plan-build-verify
Installation
SKILL.md
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, temporary body files, and coexistence with pstack and other skills in this pack. Every other reference file depends on it.
Coexistence with pstack and other skills in this pack
GitHub Issues remain the source of truth for specs, priority, and the Plan / Build / Verify lifecycle. For GitHub-issue product repos (devbox, kata-code, kata-agents, kata-symphony), plan-build-verify is the only product OS.
| Skill / layer | Role | Not its job |
|---|---|---|
| plan-build-verify | Only product OS: specs, priority, Plan / Build / Verify, labels | Implementation tactics inside a Build or Verify run |
| pstack (Cursor plugin) | Engineering execution and proof inside Build and Verify; investigation during Plan (architect / how / why) |
Planning, labels, approval, or a second issue lifecycle |
ps (/ps in this pack) |
Historical port of pstack; unwieldy; do not install for product delivery | Substitute for the pstack plugin or a second product OS |
| okf / finalize's OKF step | Retired. Remains in the library for history only | Any live roadmap or docs-as-spec workflow |
| kata-linear | Linear-first repos only | These four GitHub-issue product repos |