plan-build-verify

name	plan-build-verify
description	Use this skill for multi-step, spec-driven, or acceptance-gated implementation work that should move through Plan, Build, and Verify phases.

Plan Build Verify

Use this skill to route implementation work through a sequential path:

1. Plan: align with the user on intent, constraints, approach, and acceptance criteria before writing a project-grounded spec and implementation plan.
2. Build: execute an approved spec or implementation plan.
3. Verify: validate completed work against the spec, plan, and acceptance criteria.

Most work should move through Plan → Build → Verify. Default to Plan unless the user explicitly directs you to execute an existing plan or verify completed work.

When the selected phase is Plan, do not jump straight to a written spec. Plan starts with context exploration and user alignment. The spec records the agreed direction after the user has responded to the alignment phase and approved or redirected the recommended approach.

Phase contracts

Phase	Input	Output	Status
Plan	Idea, vague request, or new build request	Context exploration → alignment dialogue → approach approval → draft docs/specs/YYYY-MM-DD-<topic>.md with mandatory ## Acceptance criteria and Build handoff → Approved after explicit user approval	Idea → Aligned → Draft → Approved
Build	Approved spec, or explicit user override	Implemented tasks, commits, review results, Build completion report	Approved →