plan-build-verify

name	plan-build-verify
description	Use this skill for multi-step, spec-driven, or acceptance-gated implementation work in a GitHub repository where specs live as GitHub Issues. Routes work through Plan, Build, and Verify phases, manages the roadmap through issue labels and sub-issues, and triages and grooms the backlog. Also handles migration from file-based specs to GitHub Issues.

Plan Build Verify

Route implementation work through a sequential path where GitHub Issues are the source of truth for specs. Two supporting modes, Triage and Migrate, manage the roadmap.

Read the conventions first

Before any mode, read references/conventions.md completely. It defines the repo preflight, label taxonomy, issue body template, status transitions, sub-issue mechanics, issue dependencies, and temporary body files. Every other reference file depends on it.

Phase contracts

Phase	Input	Output	Status label transition
Plan	Idea, vague request, or new build request	Context exploration → alignment dialogue → approach approval → spec issue with mandatory ## Acceptance criteria	none → status:draft → status:approved
Build	Approved spec issue number, or explicit user override	Implemented tasks, commits, review results, pushed branch, Build completion report comment	status:approved → status:implemented
Verify	Implemented spec issue plus completed work or Build report	Acceptance evidence, durable acceptance tests, pull request, green CI, resolved review threads, signoff recommendation	status:implemented →