plan

To turn a software architecture design into an implementation plan, you provide the design artifact path to generate a structured, phased skeleton. This decomposes the architecture into independent, parallelizable phases with clear file changes and success criteria.

Phased planning for worktree tasks is the process of decomposing a design artifact into independent, testable implementation stages. It generates a structured plan with phase names, file changes, and verification steps to guide parallelizable worktree execution.

You create parallelizable implementation phases by applying a phased planning process to design artifacts containing Architecture and Ordering Constraints. This generates a plan skeleton populated with independent phases, specific changes, and verification steps.

Yes, generating a phased plan requires access to design artifact frontmatter, specifically the name and description. It also needs the design's Architectural details to populate the plan skeleton with phases, changes, and verification steps.

Verification works by automatically generating success criteria and verification steps within each phase of the plan skeleton. This ensures that every independent, parallelizable implementation stage derived from the architecture design is testable.