plan-build-verify-github

# Plan Build Verify (GitHub) Use this skill to route implementation work through a sequential path where **GitHub Issues are the source of truth for specs**: 1. **Plan**: align with the user on intent, constraints, approach, and acceptance criteria, then publish the spec as a GitHub Issue. 2. **Build**: execute an approved spec issue. 3. **Verify**: validate completed work against the issue's acceptance criteria and post evidence to the issue. Two supporting modes manage the roadmap: 4. **Triage**: groom the issue backlog for label hygiene, missing acceptance criteria, staleness, orphaned sub-issues, and readiness. 5. **Migrate**: convert an existing file-based `docs/specs/` bundle into GitHub Issues. Most work should move through Plan → Build → Verify. Default to **Plan** unless the user explicitly directs you to execute an existing issue, verify completed work, groom the backlog, or migrate specs. When the selected phase is **Plan**, do not jump straight to a written spec. Plan starts with context exploration and user alignment. The issue records the agreed direction after the user has responded to the alignment phase and approved or redirected the recommended approach. ## Read the conventions first Before any mode, read `references/github-conventions.md` completely. It defines the repo preflight, label taxonomy, issue body template, status transitions, sub-issue mechanics, temporary body files, and the OKF integration contract. Every other reference file depends on...