spec-kit-discussion-handoff-review

Review agent-only discussion handoff contracts before downstream specification consumption.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Discussion-to-specification handoffs in spec-kit projects can carry stale evidence, missing fields, or integrity failures that silently corrupt downstream planning. This Skill provides a structured review process for the handoff-to-specify.json contract so problems are caught before the contract becomes ready or is consumed. ## Core Features & Use Cases - Structured Contract Review: Walks a defined review order covering goal and scope, context boundary, evidence authority, selected direction, success criteria, dependencies, and consumer eligibility gates. - Three-Way Verdicts: Returns approve, request-changes with exact JSON refs, or blocked with cause, owner, and safe retry conditions. - Digest Integrity Enforcement: Requires recomputing the protected digest after changes and rejects confirmation of stale revisions. - Use Case: When sp-discussion asks for final review or sp-specify reports a contract integrity failure, run this review to validate .specify/discussions/<slug>/handoff-to-specify.json and produce a clear verdict with required corrections. ## Quick Start Review the discussion handoff contract for the current feature slug and tell me whether it is approved, needs changes, or is blocked.

Frequently Asked Questions about spec-kit-discussion-handoff-review

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

FAQPage Schema
How do I review a spec-kit discussion handoff contract?▼

Review the handoff-to-specify.json file in .specify/discussions/<slug>/ following the defined order: goal and scope, context boundary, evidence authority, selected direction, success criteria, dependencies, and consumer eligibility. Return an approve, request-changes, or blocked verdict.

What is the handoff-to-specify.json file in spec-kit?▼

It is the sole handoff authority between the discussion phase and specification in spec-kit projects. The contract is schema-first and agent-only; no Markdown companion is required, generated, or compared during review.

When should I read discussion-state.md or requirements.md during review?▼

Read supporting files only when a named source-evidence ref is stale, missing, contradictory, or needed to repair a specific field. Do not sweep them by default; the JSON contract remains the authority.

How are schema or digest failures in the handoff contract fixed?▼

Deterministic field, schema, or digest failures are repaired through the specify discussion validate-handoff command and sp-discussion. Review judgment must not silently patch upstream truth.

Why was my handoff approval rejected after making changes?▼

After any changes, the protected digest must be recomputed and the current revision confirmed. Confirmation of an older digest is not treated as approval, so re-confirm the updated contract.