// Multi-phase planning process: understand, decompose, design, validate, then implement. No code until the plan is approved.
Multi-model code review for gastown. Reviews GitHub PRs (by URL or number) or local branches (by branch name). Spawns parallel Claude, Codex, and (optionally) Gemini reviewers with specialized prompts optimized for regression prevention, then synthesizes findings into a single maintainer-grade decision report. Use --skip-gemini for dual-model mode when Gemini quota is exhausted. Invoke with /review-pr <pr-url|number|branch>.
Multi-pass code review: correctness, security, performance, and maintainability. Each finding gets severity, location, and suggestion.
Remove telltale AI writing patterns from documentation and text. Direct, concise prose without AI artifacts.
Structured brainstorming: generate 30 ideas, critically evaluate each, distill to the best 5 with actionable implementation plans.
Evaluate and polish README and documentation. Ensure accuracy, structure, runnable examples, then de-slopify.
Design and implement an agent-optimized CLI interface for any project. JSON output, structured errors, exit codes, token-efficient.
| name | planning-workflow |
| description | Multi-phase planning process: understand, decompose, design, validate, then implement. No code until the plan is approved. |
Spend 85% or more of your effort on planning before writing any code.
Follow these phases in order. Do not skip ahead.
Read all relevant documentation, code, and context. Identify the problem space, constraints, and requirements. List what you know and what you need to clarify. Ask questions if anything is ambiguous.
Break the task into ordered steps. Each step should be small enough to verify independently. Identify dependencies between steps. Flag any steps that carry risk or uncertainty.
For each step, define the interface, data structures, and contracts. Specify inputs, outputs, and error conditions. Consider edge cases. Write pseudo-code or signatures, not implementations.
Review the plan against the original requirements. Check for gaps, contradictions, and missed edge cases. Verify the step ordering makes sense. Confirm the design handles error paths.
Only after the plan is reviewed and approved, write code. Follow the plan step by step. Test each step before moving to the next.
Based on Jeffrey Emanuel's planning workflow (@doodlestein)
