writing-plans

Plan multi-step software development tasks by generating a structured plan document with a mandatory header, explicit per-task steps, validation criteria, and clear execution handoffs. This reduces rework and scope creep by breaking complex requirements into small, testable file changes.

Task breakdown for multiple agents is decomposing multi-step software requirements into discrete file changes, tests, and toolchain steps. This process creates traceable commits and clear handoffs, allowing different agents or environments to execute software development tasks independently.

Write an implementation plan document for test-driven development by outlining tasks, files to modify, tests, and validation steps. This skill enforces DRY, YAGNI, and TDD oriented guidance to encourage incremental, testable plans with frequent commits and rigorous validation.

Test-driven planning works for multi-module software projects requiring precise file changes and toolchain steps. It captures scope, interfaces, risks, and success criteria within a comprehensive plan document, ensuring traceable commits and clear execution handoffs across modules.

Handle execution handoffs to subagents by using a structured plan document with clear checkpoints and headers. This skill provides execution handoff guidance for transitioning plans into subagents or inline runs, ensuring traceable commits and avoiding placeholders.

You should not use a structured plan document for simple software tasks that do not require multi-step decomposition, precise file changes across modules, or multiple agent handoffs. It is designed for complex projects needing rigorous validation steps and traceable commits.