writing-plans

To create an implementation plan for a complex software feature, provide a feature spec to generate a step-by-step breakdown with exact file paths, bite-sized tasks, and verification steps. This approach splits multi-step features into trackable actions for execution-ready development.

Planning multi-step refactors for delegated subagent workflows requires structured handoff with exact file paths and frequent commit checkpoints. Generating a comprehensive implementation plan ensures another engineer can execute the refactor with minimal context and precise verification steps.

TDD guidance integrates into an implementation plan by requiring detailed test commands and verification steps for each task. The plan structures feature development by adding copy-pasteable code examples and frequent commit checkpoints to support disciplined test-driven delivery.

Yes, you can use this planning workflow for subagent-driven feature development by generating structured handoff plans. It supports delegated workflows by providing exact file paths, implementation details, and frequent commit checkpoints that another engineer or subagent can follow without guessing.

An execution-ready implementation plan should include exact file paths, bite-sized tasks, test commands, and copy-pasteable code examples. It breaks down multi-step software tasks into small actions with detailed TDD guidance and frequent commit checkpoints for disciplined delivery.

You need a structured implementation plan for software development when turning a vague or complex request into clear execution steps. It is essential for multi-step features, complex refactors, and delegated subagent workflows that require exact file paths and structured handoff.