planning-features

To sequence tasks for multi-agent execution, structure your implementation plan into distinct execution phases. This defines checkpoints for testing and verification, enabling parallel agents to work on isolated file-level changes without conflicting during phased delivery.

An architecture decision plan should include a problem statement, proposed approaches with trade-offs, a file-level changelist, explicit acceptance criteria, and identified risks. It maps execution sequencing for multi-agent work and provides durable storage steps for handoff.

To define acceptance criteria for feature design, specify testable conditions that the implementation must satisfy. Include these alongside alternative approaches and identified risks in the plan to establish clear verification checkpoints before coding begins.

Planning features works for API design and architecture decisions by applying research-driven analysis to pre-implementation scenarios. It locates where codebase changes should live, identifies patterns to follow, and produces reviewable plans with explicit acceptance criteria and execution phases.

To define acceptance criteria and risks, document explicit testable conditions and potential failure points within the implementation plan. This ensures teams and agents have clear verification checkpoints and understand trade-offs before executing the file-level changelist.