writing-plans

Generate implementation plans by providing a project specification to produce task breakdowns, file structure maps, and testing strategies. The Skill enforces a Plan Document Header and saves ready-to-commit outputs to a structured markdown file before coding begins.

Task decomposition for multi-subsystem engineering involves breaking vague specifications into executable, step-by-step task granularity with explicit file and testing guidance. This approach translates requirements into actionable, fork-ready plans that guide design, coding, and deployment.

Structure implementation plan documentation using an enforced Plan Document Header and a standardized template. This documentation discipline ensures outputs include detailed task breakdowns, file maps, and test plans, yielding traceable, versioned markdown files.

Yes, you can use plan templates for software engineering task breakdowns. The Skill enforces a specific plan structure that generates step-by-step task granularity, explicit file guidance, and testing strategies suitable for multi-subsystem projects.

Yes, the implementation plan workflow integrates plan-review steps and plan-handover options. After generating the structured task breakdown and file maps, it suggests commits and saves traceable, versioned outputs to facilitate team handover.

The best way to translate vague specs into actionable coding tasks is to enforce a plan template that generates detailed task breakdowns and file structure maps. This ensures execution-ready outputs with explicit testing guidance and ready-to-commit changes.