write-planlisted

Use when you have a finalized `beagle-analysis:brainstorm-beagle` spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "/write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md`. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document only.
existential-birds/beagle · ★ 60 · AI & Automation · score 84

Install: claude install-skill existential-birds/beagle

# Write Plan: Spec Into Implementation Plan Turn a `beagle-analysis:brainstorm-beagle` spec into a comprehensive implementation plan that an engineer (or a downstream agent) can execute task-by-task without re-deriving intent. The output is a single markdown plan document at `.beagle/concepts/<slug>/plan.md`, sitting beside the spec in the same concept folder. The plan captures HOW — file structure, task decomposition, exact code, exact commands — while the spec already owns WHAT and WHY. <hard_gate> Do NOT start writing the plan until a brainstorm-beagle spec exists at `.beagle/concepts/<slug>/spec.md`. If one is missing, stop and route the user to `beagle-analysis:brainstorm-beagle` first. Skipping the spec produces plans that bake in unexamined assumptions — the spec is the contract this skill plans against. </hard_gate> ## Workflow Complete these steps in order: 1. **Locate the spec** — find `.beagle/concepts/<slug>/spec.md`; if absent, stop and route to `beagle-analysis:brainstorm-beagle` 2. **Read the spec** — ingest every section; do not paraphrase, do not summarize away requirements 3. **Read project conventions** — scan `CLAUDE.md` (root and nested) for testing, commenting, and architecture rules the plan must respect 4. **Explore relevant code** — read existing files the plan will touch or pattern-match against; do not guess at structure 5. **Design file structure** — map which files will be created or modified before any task is written 6. **Decompose into ta