workflow-implement

To execute a PLAN.md file step-by-step, this Skill loads the approved plan and iterates through milestones with validation, progress tracking, and activity logging at each phase. It enforces plan-driven execution by verifying deliverables before advancing to the next milestone.

Milestone-driven implementation works by automatically committing changes and recording milestones using conventional commit messages and activity logs. This ensures that progress tracking is tied directly to git history and log entries during plan execution.

Yes, you need an existing PLAN.md to start milestone-based workflow execution. This Skill is applicable only when a PLAN.md exists and the user wants to implement the approved plans step-by-step with milestone verification and logging.

The best way to track implementation progress is through a milestone-based workflow that invokes review and qa-runner checks. These verification guardrails ensure deliverables meet plan intent while logging progress via activity logs and git commits.

Yes, you can use conventional commit messages for logging progress during plan execution. The workflow enforces logging via activity logs and conventional git commits to automatically record milestones as changes are implemented.

If deliverables fail validation during milestone execution, the built-in verification guardrails halt the workflow. The Skill invokes review and qa-runner checks to ensure deliverables meet plan intent before allowing commits and progression to the next milestone.