next

What problem does it solve? Non-trivial code changes often ship without a grounded plan, skip human approval, or bypass verification because process checklists are advisory and easy to ignore. This Skill enforces a hard state machine — plan → Phase-1 gate → analyze → human approval → execute → verify/review — where every transition is blocked by a gate script if the required artifact or approval is missing. ## Core Features & Use Cases - Enforced phase gating: Each transition calls next-phase-gate.mjs advance <phase>, which exits 1 and blocks out-of-order jumps or missing precondition artifacts (plan file, analyze report, recorded approval). - Fresh-context executor subagents: Implementation runs in isolated git worktrees via executor subagents that return BRANCH READY and never self-merge; the orchestrator integrates serially with --no-ff and re-verification between merges. - Mandatory adversarial review: Verifier, slopchecker, and adversarial-reviewer subagents must all pass per branch, and a review that finds zero issues is treated as incomplete and halts the flow. - Use Case: You need to land a risky feature in a repository with strict quality standards. Run /next to force a grounded plan with standards evidence, a cross-artifact consistency analysis, explicit human sign-off, and gated execution with adversarial review before any merge. ## Quick Start Run the /next command to start a new gated unit of work, beginning with a reset and a plan containing a Standards & Guardrails Evidence section.