sp-prd

Routes deprecated sp-prd invocations to the canonical sp-prd-scan and sp-prd-build workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Older documentation, aliases, or operators may still invoke the deprecated sp-prd compatibility entrypoint, which no longer represents the correct reverse-PRD reconstruction workflow. This Skill detects those legacy invocations and redirects the work into the canonical two-step flow so reconstruction artifacts are produced correctly. ## Core Features & Use Cases - Deprecation Routing: Detects invocations arriving through the deprecated sp-prd path and explains that it is compatibility-only. - Canonical Handoff: Directs operators to run sp-prd-scan first, then sp-prd-build, producing .specify/prd-runs/<run-id>/prd-scan.md and exported PRD artifacts. - Blocked Exit Contract: Preserves workflow state via .specify/templates/workflow-blocker-template.md instead of returning bare errors when blocked. - Use Case: A team member follows an old runbook that says to run sp-prd on a legacy codebase; the Skill intercepts this, explains the deprecation, and starts the scan-then-build reconstruction flow instead. ## Quick Start Ask the agent to reverse-document an existing project into a PRD, and it will route the request through sp-prd-scan followed by sp-prd-build.

Frequently Asked Questions about sp-prd

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

FAQPage Schema
How do I reverse-document an existing project into a PRD?▼

Run sp-prd-scan first to perform read-only reconstruction and produce a run package, then run sp-prd-build to compile the master pack and export the PRD suite. The deprecated sp-prd command now only routes you into this two-step flow.

What replaced the deprecated sp-prd command?▼

The canonical pair sp-prd-scan and sp-prd-build replaced sp-prd. The scan step generates .specify/prd-runs/<run-id>/prd-scan.md, and the build step exports the final prd.md artifact.

Does sp-prd still work as a one-step PRD extraction?▼

No, sp-prd is compatibility-only and no longer performs one-step reconstruction. It detects the legacy invocation, explains the deprecation, and hands the work to sp-prd-scan followed by sp-prd-build.

What project structure is required for PRD reconstruction?▼

The workflow requires a spec-kit project structure with a .specify directory. Outputs are written under .specify/prd-runs/<run-id>/, and blocked states follow .specify/templates/workflow-blocker-template.md.

What happens when the PRD reconstruction workflow gets blocked?▼

The Skill follows the blocked exit contract in .specify/templates/workflow-blocker-template.md, preserving state and defining resume actions instead of returning a bare error. Human action is flagged only for authority, credentials, or review decisions.