go-finishlisted

# Go Finish Guide completion of a feature after the full pipeline has run. Verify everything, clean up, and integrate. ## The Process ### Step 1: Final Verification **Before presenting options, run the full verification suite:** Read the [Verification Commands](patterns.md#verification-commands) pattern in patterns.md when running this. **If anything fails:** Stop. Do not proceed. Report the failure and suggest whether go-fixer or go-debugger is appropriate. **If skipped tests remain:** These are unimplemented test stubs from scaffolding. Either they were intentionally deferred (user decision) or they were missed. Ask the user. ### Step 2: Acceptance Criteria Check Read `.plan/<feature-slug>/FEATURE.md` and check every item in "Definition of Done": Read the [Acceptance Criteria Check](patterns.md#acceptance-criteria-check) pattern in patterns.md when writing this. For each item: either point to evidence (test name, command output) or flag it as unverified. ### Step 2b: Update Project Map **Sequential safety:** This step modifies `.claude/skills/doc-project/SKILL.md`, which is a singleton file. If another feature's go-finish is running concurrently, you WILL create merge conflicts. This is safe because go-product-manager drives features sequentially — but if you were invoked manually outside that flow, verify no other feature is in progress before updating. Read `.claude/skills/doc-project/SKILL.md`. Update: 1. The context table if a new context was created 2. Th