sp-clarify

Strengthens existing specification packages by closing planning-critical gaps before planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Existing specification packages often contain planning-critical gaps, weak analysis, or unresolved ambiguity that make downstream planning unreliable. This Skill repairs and deepens the current spec package in place instead of rerunning the entire specification flow from scratch. ## Core Features & Use Cases - Targeted Spec Enhancement: Identifies shallow analysis, missing scenarios, contradictions, and unproven feasibility, then updates spec.md, alignment.md, context.md, and references.md in place. - Structured Clarification Loop: Asks one high-impact question at a time, delegates bounded research to subagent lanes, and persists evidence in clarification handoffs, checkpoints, and an evidence index. - Consequence Analysis Gate: Preserves CA-### consequence obligations, coverage gaps, and stop-and-reopen conditions so lifecycle, compatibility, and shared-state risks survive downstream handoffs. - Use Case: After drafting a feature spec, you realize the feasibility of a key API integration is unproven. Run this Skill to deepen the analysis, route feasibility proof to deep research if needed, and return a planning-ready package. ## Quick Start Ask the assistant to run /sp-clarify describing which parts of the current spec package need deeper analysis or correction.

Frequently Asked Questions about sp-clarify

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

FAQPage Schema
How do I fix gaps in a spec package before planning?▼

Run the sp-clarify workflow with a description of what needs deeper analysis. It identifies planning-critical gaps, asks one high-impact question at a time, and updates spec.md, alignment.md, context.md, and references.md in place.

When should I use clarification instead of rerunning specification?▼

Use clarification when the existing spec package is mostly sound but has weak analysis, unresolved ambiguity, or new constraints. Rerunning the full specify flow is only justified when the current package is unusably wrong.

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

Yes, it requires a spec-kit project with a .specify directory and an active feature directory containing the spec package. It resolves FEATURE_DIR via prerequisite scripts or lane resolution before proceeding.

What happens when feasibility cannot be proven during clarification?▼

If the remaining issue is whether a capability can work with available APIs or platform behavior, the workflow updates alignment.md and workflow-state.md to recommend the deep-research command, which must return a planning handoff with demo evidence.

Why does clarification stop with a subagent-blocked status?▼

The workflow blocks when a delegated lane returns only prose without a written handoff file, or when the artifact update cannot be safely packetized. The blocker is recorded in workflow-state.md so the lane can be re-dispatched with a valid handoff path.