writing-plans

Implementation plans provide step-by-step tasks with real file paths, runnable code samples, and quantitative metrics like complexity scores and duration estimates. This Skill generates self-contained plans when you have design finalized but need precise execution steps, validation gates, and MCP requirements for handoff to engineers with zero context.

Comprehensive plans include header templates, exact file paths for all changes, code examples for each component, validation gates between milestones, complexity and risk scores, backend/data/frontend/DevOps breakdowns, and explicit MCP requirements. This ensures engineers can execute without clarification.

Yes. Plans integrate Shannon quantitative analysis across architecture layers, assign complexity and duration metrics to each task, define validation gates between steps, and specify MCP dependencies. This transforms design into measurable, gated execution phases.

Plans break tasks across all four layers with layer-specific file paths, code examples, and metrics. Each layer includes its own validation gates and dependencies, allowing parallel execution while maintaining coordination points and cross-layer requirements.

Use implementation plans when design is complete, multiple engineers need context-free execution, quantified risk and complexity matter for scheduling, or you need documented handoff with validation checkpoints. Plans eliminate ambiguity when distributing work across teams.

Yes. Plans explicitly list MCP requirements and integrate them into task sequences and validation gates. This ensures MCP dependencies are clear before execution begins and validation gates confirm MCP interactions succeed.