From productionos
Create step-by-step implementation plans with risk assessment, dependency mapping, and effort estimation. Used after brainstorming, before execution.
npx claudepluginhub shaheerkhawaja/productionos --plugin productionoscommands/# /writing-plans — Implementation Planning Turn approved designs into step-by-step executable plans. ## Step 0: Preamble Run `templates/PREAMBLE.md`. Read the spec or latest brainstorming output. ## Step 1: Capture the Approved Scope Restate the approved design, goal, and constraints before decomposing the work into tasks. ## Plan Structure ### 1. Requirements Summary - What are we building? (1-2 sentences) - What are the success criteria? - What are the constraints? ### 2. Task Breakdown For each task: ### 3. Dependency Graph ### 4. Execution Strategy - Which tasks can run in par...
/writing-plansGenerates a detailed implementation plan, breaking down the project into bite-sized, actionable tasks for step-by-step execution.
Turn approved designs into step-by-step executable plans.
Run templates/PREAMBLE.md. Read the spec or latest brainstorming output.
Restate the approved design, goal, and constraints before decomposing the work into tasks.
For each task:
### Task N: {title}
**Files:** {files to create/modify}
**Dependencies:** {tasks that must complete first}
**Effort:** S | M | L
**Risk:** Low | Medium | High — {why}
**Acceptance criteria:** {how to verify it's done}
Task 1 (foundation)
├── Task 2 (depends on 1)
├── Task 3 (depends on 1)
│ └── Task 5 (depends on 3)
└── Task 4 (independent)
/auto-swarm-nth for parallel tasks| Risk | Likelihood | Impact | Mitigation |
|---|
How do we know it's done? Tests to write, checks to run, criteria to meet.
Run templates/SELF-EVAL-PROTOCOL.md on plan quality:
After plan approval: dispatch /auto-swarm-nth for parallel execution or work through tasks sequentially.