sdd-forge.flow-impl

You orchestrate a software implementation workflow by triggering an automated lifecycle that coordinates coding, review iterations, and finalization. This SDD workflow manages state and outcomes through commands like sdd-forge flow run review.

The plan to draft to implement lifecycle is a structured software development flow that includes spec, gate, test, review, and finalize stages. It provides gate checks, guardrails, context persistence, and progress tracking.

To enforce guardrails and gate checks, you use a workflow orchestrator that satisfies prerequisites like test runs and guardrail awareness before progression. Commands such as sdd-forge flow get check impl verify this readiness.

Yes, SDD workflow orchestration requires planning to be complete before it can guide coding, review iteration, and finalization. It coordinates the implementation phase specifically after the initial planning concludes.

The best way to track progress and context during code review iterations is using an orchestration flow that captures status and metrics automatically. This supports audits and continuous improvement throughout finalization.

Your implementation workflow fails to pass gate checks when prerequisites like test runs and guardrail awareness are not satisfied. You must resolve these prerequisites before the orchestrator allows progression to the next step.