Driving a Goal to Done

One run from a goal to reviewed, committed code. This skill orchestrates; it does not implement. Planning happens through /vibe-plan (or /vibe-deep-plan first, when the work is too big), each ticket is implemented by a fresh sub-agent running /vibe-implement, and the whole goal closes on a standards review plus a formal requirement quality gate.

The issue tracker and triage label vocabulary should have been provided to you — run /vibe-init if docs/agents/issue-tracker.md is missing.

Landing and tracker state

/vibe-review is read-only: it reports findings and never changes tracker state. A review pass, a sub-agent completion claim, or the user's general goal request does not authorize a tracker write. The parent spec issue is read-only: never include it in a tracker-change preview or modify it.

The goal owns integration and final landing. For a hosted tracker it must not preview or change ticket state while work exists only on ticket branches or in the integration workspace; only after Stage 4 has authoritative evidence that the exact reviewed integration commit SHA is present on the original target branch may it show an exact preview of every checkbox, the complete comment, and each status or close change, then wait for separate, explicit approval immediately before writing — rejection or no response leaves the tracker unchanged. For a version-controlled local Markdown tracker there is nothing to preview: each ticket's checkboxes ride that ticket's own implementation commit, so integration and landing carry code and checklist together. Either way the orchestrator never edits a ticket file itself and never puts a tracker-only commit on the target branch.

The orchestrator never writes production code

Your context is the only thing holding the goal together: the ticket graph, what landed, what's left. Spending it on implementation is how a run dies halfway.

• Never edit source files yourself. Every code change goes through a ticket sub-agent.
• Never read a diff in full. Read the sub-agent's report and the review verdict; open code only to adjudicate a specific disputed claim.
• Stay in one context window from planning through the last ticket. If it degrades anyway, hand off with /vibe-handoff — pass the ledger, not the history.