skills.rest
chenziyang110
chenziyang110COMMUNITY
Explore all skills by this author →
GitHub

sp-discussion

Matures rough ideas into validated requirement contracts before formal specification.

Updated Jul 6, 2026
Search Tags:#specification#requirements#decision tracking#spec-kit#handoff contract#product discussion#truth pass
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-discussion-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-discussion
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-discussion
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-discussion-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Rough product ideas often jump straight into specification or implementation without boundary locking, evidence verification, or decision tracking, causing rework and drift. This Skill runs a resumable senior product and technical discussion that matures an idea into a reviewed, handoff-ready requirement contract. ## Core Features & Use Cases - Resumable Discussion Sessions: Creates or resumes typed discussion state under .specify/discussions/<slug>/ with checkpoint-based persistence and a compact JSONL event log. - Boundary and Truth Gates: Enforces a Context Boundary Gate and Truth Pass so project-specific technical claims are backed by live repository evidence, not assumptions. - Validated Handoff Contract: Produces exactly one agent-only handoff-to-specify.json contract with self-review, protected review digest, and explicit user confirmation before it becomes handoff-ready for sp-specify or sp-quick. - Use Case: You have a vague feature idea for an existing codebase. Start a discussion, lock the target boundary, compare 2-3 evidence-backed technical options, confirm the direction, and hand off a validated contract to formal specification. ## Quick Start Ask the assistant to start an sp-discussion session for your rough feature idea so it can be discussed, grounded in evidence, and prepared for specification.

Frequently Asked Questions about sp-discussion

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

FAQPage Schema
How do I turn a rough feature idea into a specification-ready requirement?▼

Start an sp-discussion session with your idea. The workflow clarifies goals, scope, and non-goals, locks the context boundary, verifies project facts through a truth pass, and produces a validated handoff-to-specify.json contract only after self-review and your confirmation.

What is the difference between sp-discussion and sp-specify?▼

sp-discussion matures rough ideas into requirements and technical options before formal specification, while sp-specify consumes the validated handoff contract to create formal feature artifacts. sp-discussion never creates feature branches, edits source code, or writes specification files.

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

Yes, it requires a spec-kit project with a .specify directory. Discussion state, logs, and handoff contracts are stored under .specify/discussions/<slug>/, and templates are read from .specify/templates/.

Can I resume a discussion after closing the session?▼

Yes, discussions are resumable. Canonical state lives in discussion-state.json with a compact discussion-log.jsonl event log, so the workflow can recover decisions, open questions, and handoff readiness after compaction or a new session.

When does sp-discussion write files to disk?▼

Only at semantic checkpoints or explicit save triggers such as 'checkpoint, continue', handoff events, or high compaction risk. Ordinary replies stay frontstage-only and keep state in active memory without writing files.

Why won't sp-discussion give technical recommendations immediately?▼

It enforces a Context Boundary Gate and Truth Pass first. Project-specific claims about files, modules, or implementation paths require live repository evidence, so it verifies facts before recommending technical options.

Related Skills

Explore More Product & Management Skills→
supermalangsupermalang

discovery

Clarify product requirements and generate a structured PRD.

Community
Advanced
chenziyang110chenziyang110
7

Test-Driven Development (Spec Kit Plus)

Enforce a failing test before production code changes in sp-* workflows.

Community
Basic
nguyenpv1980-wqnguyenpv1980-wq
2

architecture-designer

Design software architecture from inspected codebase components and dependencies.

Community
Advanced
GenproMMGenproMM

gsd-quick

Execute small ad-hoc tasks with atomic commits and state tracking.

Official
Basic