writing-plans

To create an implementation plan for autonomous agent execution, you define a plan template that encodes tasks as complete, self-contained units of work, including goals, success criteria, and explicit verification steps. This ensures tasks are actionable and auditable.

Subsystem task grouping is a planning technique that organizes implementation tasks by subsystem to enable parallel execution by agents while preserving dependencies and traceability across the broader software project.

You structure implementation tasks to ensure reproducibility by including explicit goals, success criteria, and save locations—such as a dated markdown file—so that each unit of work remains traceable and reviewable.

No, writing-plans requires no specific dependencies or components to function. It requires only a defined plan template, explicit context loading guidance, and verification steps to validate plan effectiveness.

The best way to group tasks for parallel agent execution is to organize them by subsystem, which clarifies ambiguities upfront and preserves dependencies, allowing multiple agents to work concurrently without conflict.

You should not use a structured implementation plan template when tasks are purely exploratory or lack defined success criteria, as the approach requires explicit context loading guidance and verification steps to validate plan effectiveness.