writing-plans

To turn an approved design into an implementation plan, provide the feature name and spec to generate a structured plan detailing tasks, touched files, testing steps, and commit history on a feature branch.

Task decomposition works by mapping high-level requirements into specific files to modify, tests to write, and documentation to update, while outlining the sequence of actions for developers and subagents.

The best way to automate feature branch workflow planning is generating an end-to-end plan that decomposes work by subsystem and defines explicit tasks, acceptance criteria, and commit history.

Yes, subagents can orchestrate plan development by coordinating research, drafting, and execution on complex features to ensure all touched files and testing steps are accurately mapped.

An implementation plan for a software project should include explicit tasks, files to modify, tests to add, clear acceptance criteria, testing steps, and a structured commit history.

You need a structured plan for software engineering tasks when you have approved designs or clear requirements and must provide developers, reviewers, and subagents with a precise execution path on a feature branch.