planninglisted

# crew Planning Conventions ## ROADMAP.md Plain Markdown, milestones → phases. Status markers: - `[ ]` open · `[>]` active (claimed) · `[x]` done (append ` — erledigt YYYY-MM-DD`) · `[~]` deferred ```markdown ## Meilenstein 1: Fundament - [x] 1.1 Backend-Struktur — erledigt 2026-06-12 - [>] 1.2 DB-Schema (Drizzle) @worktree-a - [ ] 1.3 Auth (depends: 1.2) ``` Phases are identified by their heading text, **not** by rigid numbers — so inserting/reordering (via `/crew:adjust`) is a text edit, never a renumber. Each phase should be independently mergeable. Record dependencies inline (`depends: …`) so `/crew:execute dispatch` can build a DAG and parallelize independent phases. ## plans/<n>_<milestone-slug>/<file>.md The spec/plan concern is **split across two kinds of file** in the milestone folder, not stacked in one — a single source of intent that phase plans reference rather than copy: - **`_spec.md` — the milestone Spec (permanent).** Written by `/crew:brief`, it owns the **intent**: Goal/problem, Requirements, Acceptance criteria, Out of scope. It is the single source of truth and stays for the life of the milestone — co-located with `_roadmap.md` once archived, never removed and never duplicated. - **`<id>_<title>.md` — a phase plan.** Written by `/crew:plan`, it is the **how** for one phase: a short **Scope of this phase** note (1–3 lines: the deliverable + this phase's own acceptance) that **references `_spec.md`** for the full intent, followe