writing-plans

To create an implementation plan for a multi-file software feature, you define the feature spec and the system generates bite-sized, executable tasks with explicit file paths, code examples, and a validation checklist. This provides a step-by-step execution path guiding developers from planning to verification.

The best way to break down complex feature specs into executable tasks is to use automated task breakdown, which transforms high-level requirements into complete task-level instructions. This includes exact file touchpoints, test commands, and code examples for hands-on development.

You generate a testing strategy and documentation scaffolding by applying automated planning to your feature requirements, which outputs explicit test commands and structural guidance. This ensures your testing and documentation work follows a precise, verifiable execution path.

Yes, generated implementation plans integrate directly with subagent-driven development workflows. The plans provide bite-sized, executable tasks with explicit file references and validation checklists that subagents can follow to execute code generation and verification steps autonomously.

No, you do not need to specify exact file paths and test commands before generating a plan. The system automatically infers and outputs precise file touchpoints, complete task-level instructions, and test commands directly from your feature spec.

You should use automated task breakdown instead of manual planning when starting large, complex multi-file features that require architectural planning. It solves the problem of lacking a clear execution path by providing a comprehensive, step-by-step plan with verification steps.