sp-accept

Guides humans through step-by-step product acceptance of completed spec-kit features.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-accept-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-accept
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-accept
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-accept-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementation closeout, a human reviewer often lacks the context to verify a finished feature. This Skill restores that context and walks the reviewer through one acceptance scenario at a time, producing a durable, resumable acceptance record instead of relying on old chat history. ## Core Features & Use Cases - Zero-Context Orientation: Explains what changed, why it matters, and the exact starting entrypoint in plain product language before any verification begins. - Guided Step-by-Step Acceptance: Leads one scenario and one step at a time, persisting observed results, evidence, and a resume cursor into a schema-valid human-acceptance.json file. - Explicit Verdicts and Failure Routing: Records accepted, rejected, or blocked outcomes and routes defects to /sp-implement, /sp-debug, /sp-clarify, or /sp-specify without editing production code. - Use Case: A developer finishes a feature in a spec-kit project; the product owner returns days later with no memory of the work and is guided through verifying each user-visible behavior until a final acceptance verdict is recorded. ## Quick Start Ask the agent to run the sp-accept workflow for the completed feature so it can walk you through verifying each acceptance scenario step by step.

Frequently Asked Questions about sp-accept

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

FAQPage Schema
How do I run human acceptance testing for a spec-kit feature?▼

Invoke the sp-accept workflow after implementation closeout passes. It prepares a human-acceptance.json state file, gives you a zero-context summary of what changed, and guides you through one verification step at a time until a final verdict is recorded.

What is the difference between implementation closeout and human acceptance?▼

Implementation closeout confirms the technical work is complete, while human acceptance verifies the product behavior matches approved requirements. A feature can be technically complete yet still pending human acceptance, and the two statuses are never collapsed.

Does sp-accept require a spec-kit project structure?▼

Yes, it requires a project with a .specify directory and the spec-kit-plus CLI available via uvx. It resolves the feature through check-prerequisites scripts and the deterministic workflow runtime before any acceptance writes occur.

Can I resume an interrupted acceptance session?▼

Yes, the workflow persists a resume cursor in human-acceptance.json after every step. On resume it restates only the accepted context and the exact current step without replaying completed scenarios, unless implementation evidence changed.

What happens when an acceptance scenario fails?▼

The failure is recorded as a finding with expected behavior, observed behavior, and evidence, then routed to the appropriate workflow such as /sp-debug or /sp-implement. The acceptance state and resume point are preserved so verification can continue after repair.

Can automated tests substitute for human acceptance in this workflow?▼

No, automated tests, agent visual inspection, and implementation closeout never substitute for an explicit human PASS. Every required scenario must receive an explicit human pass before the accepted verdict and closeout command run.