implementation-cycle

To automate an implementation lifecycle for backlog work items, invoke the implementation-cycle Skill. It coordinates the end-to-end execution by stitching together plan definitions, execution steps, validation gates, and delivery checkpoints into a repeatable workflow.

The PLAN-DO-CHECK-DONE workflow is a structured four-phase implementation lifecycle that enforces phase-specific tooling and guardrails. It coordinates work-item execution from initial plan definitions through final delivery checkpoints to ensure proper governance.

You can enforce governance gates and design validation by running an automated implementation cycle. It automatically invokes plan-validation, preflight checks, design-review validation, and routing decisions to ensure alignment with the defined plan.

Yes, you can coordinate cross-functional tasks and subagents within a structured workflow. The implementation cycle supports subagent routing and task coordination to ensure team compliance with the defined design throughout the lifecycle.

No, this implementation lifecycle does not require external dependencies or components. It operates independently to orchestrate the end-to-end workflow, defining phase-specific tooling and governance gates natively.

The best way to ensure alignment with plans during work-item execution is to use an automated implementation cycle. It invokes design validation and preflight checks at specific phases, making routing decisions to maintain strict alignment with the original plan.