Write Plan

name: write-plan
description: Create an implementation plan for /impl-task. Brainstorms first, produces a decisions spec, then writes a structured plan with execution strategy.
scope: global
allowedTools:

- Read
- Write
- AskUserQuestion
- Search

---

# /write-plan — Plan Writing Pipeline

Use this command when you need to produce a structured implementation plan before coding. The output is a plan that `/impl-task` consumes.

## Inputs to collect

- Problem statement or feature request.
- Any hard constraints (performance, security, UX, timelines).
- Reference artifacts: research docs, GH issues, prior conversation context.

## Behaviour

1. **Load the pipeline**
   - Treat `.claude/pipelines/plan-writing.md` as the authoritative checklist.
   - Follow `.claude/rules/plan-writing.md` for discipline throughout.
   - Follow its phases in order; do not skip phases silently.

2. **Enter plan mode**
   - Enter plan mode immediately. All work happens in plan mode.
   - Do not write or modify any application code.

3. **Brainstorm**
   - Follow `superpowers:brainstorming` discipline with pipeline overrides.
   - Explore scope, constraints, approaches with the user.
   - Produce a decisions spec to `docs/plans/specs/YYYY-MM-DD-<topic>.md`.
   - Get user approval on the spec before proceeding.

4. **Write the plan**
   - Read `.claude/pipelines/implementation.md` for the format the plan must match.
   - Write as a Claude Code plan file with execution strategy + inline reminders per step.
   - Follow `.claude/rules/agent-teams.md` for parallel dispatch decisions.
   - Follow `.claude/rules/workspace-setup.md` for worktree and Ralph setup.
   - Follow `.claude/rules/beads.md` — plans do NOT create beads.
   - Present to user in plan mode for inline review.

5. **Save (no execution)**
   - Exit plan mode after user approves the plan.
   - Copy plan to `docs/plans/YYYY-MM-DD-<topic>.md`.
   - Save execution state to Serena via `plan-lifecycle save`.
   - State: "Plan saved. Execute with `/impl-task`."
   - **Never execute the plan, create worktrees, or create beads.** Those happen during `/impl-task`.