write-plan

To generate an implementation plan, you analyze software requirements and break down features into small, testable tasks with clear acceptance criteria, effort estimates, and defined success metrics.

Task breakdown is achieved by applying structured templates to software requirements, dividing complex features into actionable phases and testing strategies while identifying potential project risks.

Automated project planning optimizes token usage by gathering context efficiently through Git diffs and grep, leveraging caching and progressive disclosure to minimize resource consumption.

Yes, structured templates support agile project management by estimating development effort, identifying implementation risks, and defining clear success metrics for software features.

While not strictly required, using Git diffs to gather context allows the planning process to efficiently analyze existing codebases and generate highly accurate, actionable implementation plans.

Limitations arise if software requirements are vague or if the codebase lacks accessible context for grep and Git diffs, which constrains the accuracy of task breakdown and risk identification.