sp-explain

Explains spec-kit stage artifacts and project cognition state in plain language.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working through a spec-kit planning workflow, artifacts like spec.md, plan.md, and tasks.md accumulate quickly and become hard to interpret. This Skill reads the current stage artifact or project cognition state and translates it into a plain-language explanation so you can decide whether to continue, revise, or proceed. ## Core Features & Use Cases - Stage-Aware Explanation: Deterministically resolves the most advanced artifact (tasks, plan, or specify) and explains what is decided, what is open, and what comes next. - Cognition and Atlas Views: Explains project cognition status and compatibility/export handbook artifacts covering ownership, dependencies, lifecycle, and change impact. - Read-Only Safety: Never rewrites stage artifacts; it reports missing state explicitly instead of inventing it. - Use Case: After running a planning workflow, ask for an explanation of the current plan to understand the implementation approach and risks before generating tasks. ## Quick Start Ask the assistant to explain the current planning stage artifact in plain language using the sp-explain skill.

Frequently Asked Questions about sp-explain

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

FAQPage Schema
How do I understand a spec-kit plan or tasks artifact?▼

Invoke the sp-explain skill, optionally naming the stage you want explained. It resolves the most advanced artifact (tasks, plan, or specify), reads supporting files, and renders a structured explanation with status, risks, and next steps.

What does the sp-explain skill do in a spec-kit workflow?▼

It translates the current stage artifact or project cognition state into plain language. It is explanation-only and never rewrites spec, plan, or tasks files, handing off to /sp-plan or /sp-tasks when you are ready to advance.

Does sp-explain modify my spec or plan files?▼

No. The skill is strictly read-only and grounded in what exists on disk. If an expected artifact such as implementation status is absent, it says so explicitly instead of inventing state.

What project structure is required to use sp-explain?▼

It requires a spec-kit project structure with a .specify/ directory containing feature artifacts and optionally project-cognition status. Compatibility and export handbook artifacts are explained only when explicitly requested.

Why does sp-explain say implementation status is unavailable?▼

There is no canonical implementation status artifact in the file set. In that case the skill falls back to explaining the most recent planning artifact rather than guessing progress.