writing-plans

To break down software requirements, you create an implementation plan that decomposes complex changes into bite-sized tasks with exact file paths, testing steps, and verification details. This ensures developers can execute tasks without needing extra context.

An implementation plan is a structured document that transforms complex software requirements into actionable development tasks. It includes task decomposition, exact file paths, testing guidance, and verification steps aligned with DRY, YAGNI, and TDD practices.

You create an engineering workflow plan by structuring tasks with exact file paths, implementation details, and testing guidance. This allows another developer or subagent to implement the software changes step by step without requiring additional context.

Yes, this implementation planning approach supports TDD practices by requiring testing guidance and verification steps within the task decomposition. It applies TDD alongside DRY and YAGNI principles to organize reliable coding work.

Yes, you can use this for complex feature development and code delegation. It applies to scenarios requiring structured task decomposition, allowing you to delegate complete engineering plans that another developer can implement step by step.

The best way to document engineering workflows for subagents is creating implementation plans with structured task decomposition, exact file paths, and verification steps. This ensures subagents can execute development tasks without needing extra context.