go

Executes an approved implementation plan end-to-end on a git branch and hands off to PR creation.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/vzakharov/vovazakharov.com --skill go-vzakharov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/go
Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill go-vzakharov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved plan into finished code without ambiguity: it locates the correct plan file, records the operator's go-ahead, implements the work with disciplined commits, runs mandatory quality passes, and fills in the pull request. ## Core Features & Use Cases - Plan lifecycle management: Flips plan files from draft to in-progress to completed (or paused) via git renames that encode state, quoting the operator's literal go-ahead in the commit message. - Three entry modes: Bare invocation on the current branch, attaching to an existing branch or PR by target token, or planless execution from a prose task description. - Handoff canary: Detects mispasted cross-session handoff blocks and stops to ask rather than implementing a branch name as if it were a task. - Use Case: After a planning session produces docs/plans/add-dark-mode.draft.do-not-implement.md, invoke /go in a fresh session with the branch target to attach, implement the plan, run the polish passes, and open the PR. ## Quick Start Type /go followed by the branch name from your planning session's handoff block to attach to that branch and implement the approved plan.

Frequently Asked Questions about go

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an approved plan with the /go command?

Invoke /go with no arguments to implement the plan on the current branch, or pass a branch name, PR number, or PR URL to attach to that branch first. The skill locates the actionable plan file under docs/plans, flips it to in-progress, and implements it.

What is the difference between /go with a target and /go with a task?

A single whitespace-free token is treated as a target branch or PR to attach to, verified with git ls-remote. An argument containing whitespace is treated as a prose task and executed planlessly, skipping the plan-location step.

Can /go run without a plan file?

Yes, planless entry accepts a prose task as the plan and starts directly at implementation. Quality passes and PR creation still run unchanged; only plan location is skipped.

What happens if the target branch does not resolve?

The skill stops and asks rather than falling through to task mode. Implementing an unresolvable branch name as if it were a task description is treated as the worst possible outcome, worse than one clarifying round-trip.

Why does /go refuse to pick up an in-progress plan file?

An in-progress filename is a claim by another active session, and picking it up unasked would put two agents on the same plan and branch. It reports the conflict and asks unless the operator explicitly says to take over the abandoned session.

When should I not use /go?

Do not use it before plan approval, since invoking it is itself the go-ahead. It also does not run the vet suite, merge base branches, or mark PRs ready; those belong to the finalize step.