writing-plans

To turn feature requirements into an implementation plan, you generate a comprehensive Plan Document with a header and bite-sized tasks. Each task details exact file paths, complete code samples, tests, and explicit verification commands for rapid development.

The best way to break down complex features for subagent-driven development is creating bite-sized tasks spanning two to five minutes each. This structured approach maintains consistent engineering standards and facilitates delegating work effectively.

You structure implementation plans for test-driven development by outputting explicit verification steps and complete code samples within each task. The plan document covers setup, core functionality, testing, and documentation phase by phase.

Yes, you can generate a single shareable plan document containing exact file paths and complete code samples. This output ensures reproducible development and provides clear guidance for implementation and code reviews.

Generating a task-by-task workflow plan requires no specific dependencies. It operates independently to translate vague requirements into detailed, executable plans with explicit tasks, file paths, and example code.