Skip to content

docs: introduce docs/adr and docs/architecture for ADR & spec-driven development #65

@mikanmarusan

Description

@mikanmarusan

Goal

Make ADR-driven and spec-driven development operational in this repo. The plugin skills x-recording-adr (ADRs under docs/adr/) and x-syncing-specs (specs under docs/architecture.md + docs/architecture/*.md) ship with the toolchain but do not engage today because the opt-in markers and target directories do not exist. This tracking issue coordinates the bootstrap.

Your Task

Suggested order: #62 and #63 are independent (separate doc trees, enforced ownership wall) and can land in either order; #64 should land last because its verification checks both trees and adds the markers that activate the skills.

Context

  • Source plan: .plans/planning-adr-spec-docs-20260620.md (full research, risk matrix, and Codex review).
  • Scope decided with the user: full bootstrap (scaffold + markers + real seed ADR + split architecture.md), consolidated from 7 plan tasks into 3 larger PRs.
  • Two Codex findings were applied to the plan: (1) ops/rationale docs (deploy-and-iam.md, observability.md) stay marker-free so spec-sync never overwrites them; (2) verification is tool-independent so it is reproducible from a plain checkout.

Warning

Acceptance Criteria

  • All child issues are closed

Metadata

Metadata

Assignees

No one assigned

    Labels

    loop:trackingParent tracking issue for a loop batch

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions