implementation-plan

To create an execution plan for feature implementation, this Skill decomposes requirements into mid-to-low-level phased steps, defining objectives, scope, non-goals, and dependencies while grounding tasks in your real codebase patterns.

Mid-to-low-level task decomposition in software development breaks features into specific steps that avoid ambiguity while maintaining enough abstraction to allow flexible implementation execution by developers or AI coding agents.

Generating a codebase-integrated execution plan without redoing discovery requires analyzing existing documentation and real codebase patterns to produce concrete phased steps, avoiding hypothetical scenarios and ensuring accurate feature implementation.

Yes, this implementation planning approach works for AI coding agents by producing concrete execution plans with defined objectives, assumptions, and dependencies that provide sufficient detail for autonomous feature implementation.

The best way to structure an execution plan for complex software features is to include objective, scope, non-goals, deferred items, assumptions, dependencies, and phased steps grounded in real codebase analysis.

You should not use mid-to-low-level task decomposition when project direction is unknown, as this approach assumes direction is established and focuses on analyzing existing codebase and documentation to generate concrete execution steps.