plan-writer

To generate an implementation plan, you input design session outputs and briefs to bind design decisions to ordered steps, agent assignments, and quality gates, producing a structured template ready for execution agents to follow deterministically.

Replacement pattern detection identifies component-level replacements in your plan and enforces interleaved create/delete ordering alongside dependency-safe deletions, preventing unsafe batching and ensuring system stability during execution.

Implementation steps are mapped to execution stages by integrating phases.execute.stages from workflow.yaml, resolving quality gates, and matching step requirements to available agents in the agents_generated roster for precise task delegation.

Yes, implementation plans integrate phases.execute.stages and quality_gates directly from workflow.yaml, enforcing safety checks and mapping deliverable artifacts to ensure execution proceeds with clear responsibilities and verified gate compliance.

The best way is using a standardized plan template featuring Prior Design Decisions, an ordered Steps table, Quality Gates, Risks & Mitigations, and Acceptance Criteria, ensuring the migration is reviewed and gate-enforced for execution agents.

Dependency safety matters because unsafe batching of component deletions can break system integrity, so the plan enforces interleaved create/delete ordering to ensure replacements execute without disrupting dependent services or causing execution failures.