writing-plans

An implementation plan translates vague feature specs into concrete, executable task lists. It details exact file paths, code examples, testing steps, and documentation to guide both humans and subagents through implementation and verification.

You break down complex software tasks by generating a repeatable planning template that specifies concrete files, commands, checkpoints, and verification steps. This structure guides both humans and subagents through design, implementation, and verification.

You need a detailed implementation plan when applying multi-step features or complex workflows. It provides a ready-to-use start-point for new projects, including example code scaffolds and testing steps following TDD, DRY, and YAGNI principles.

Yes, subagent-driven execution is explicitly supported by the generated implementation plans. The plan enables subagent execution by detailing exact file paths, code examples, tests, and documentation following TDD, DRY, and YAGNI principles.

The best way to generate a planning template is to provide a complete, end-to-end planning prompt from a feature spec. You receive a ready-to-execute task list with exact file paths, tasks, and verification steps for immediate use.