crew-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:dispatch` can build a DAG and parallelize independent phases. ## plans/<milestone-slug>/<file>.md One file, two layers (no separate spec file unless `clarify.specArtifact: "separate"`): ```markdown # <Feature/Phase/Ticket> ## Spec ← the what/why (from /crew:brief or an external ticket) - Goal / problem - Requirements - Acceptance criteria - Out of scope - externalRef: <ticket-id> ← only when pulled via /crew:pull ## Plan ← the how - affected files - Tasks: action / pattern to mirror / validation command - Risks - Verify configuration for this phase ``` ### Plan file naming & folders Plans live in **milestone folders** — `plans/<milestone-slug>/` — keeping a brief together with the phases it spawned. The folder name is a slug (not a number), so inserting/reordering via `/crew:adjust` never renumbers a folder. `<milestone-slug