sp-prd-scan

Scans existing repositories to produce reconstruction-grade evidence packages for PRD compilation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When you need to write a PRD suite for an existing (brownfield) repository, manually reading the entire codebase is slow and error-prone. This Skill performs a read-only reconstruction scan that harvests grounded evidence about capabilities, artifacts, and boundaries so a downstream build step can compile PRDs without rereading the repository. ## Core Features & Use Cases - Reconstruction-Grade Scanning: Produces a complete scan package under .specify/prd-runs/<run-id>/ including coverage ledgers, capability ledgers, artifact contracts, state machines, and error semantics. - Evidence Labeling: Preserves Evidence, Inference, and Unknown labels on every consequential claim, with depth levels from L1 (exists) to L4 (reconstruction-ready). - Subagent-Orchestrated Lanes: Dispatches validated PrdScanPacket contracts to read-only subagent lanes and enforces structured worker result handoffs. - Freshness-Aware Routing: Consults .specify/prd/status.json to route fresh, targeted-stale, or full-stale scans, and resumes interrupted runs from workflow-state.md. - Use Case: Point it at a legacy service repository before writing requirements; it triages capabilities into critical/high/standard/auxiliary tiers and refuses handoff to the build step when critical capabilities lack reconstruction-ready evidence. ## Quick Start Ask the agent to run /sp-prd-scan on this repository to reconstruct its capabilities and produce a scan package ready for PRD compilation.

Frequently Asked Questions about sp-prd-scan

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

FAQPage Schema
How do I generate a PRD from an existing codebase?▼

Run the sp-prd-scan workflow first to produce a reconstruction-grade scan package under .specify/prd-runs/<run-id>/, then hand off to sp-prd-build which compiles the PRD suite from that package without rereading the repository.

What does the sp-prd-scan skill output?▼

It writes a scan bundle including workflow-state.md, prd-scan.md, coverage and capability ledgers, artifact-contracts.json, reconstruction-checklist.json, state-machines.json, error-semantics.json, and per-lane scan packets with evidence notes.

Does sp-prd-scan modify my repository source code?▼

No. The scan phase is strictly read-only with respect to the repository; it only writes its reconstruction package under .specify/prd-runs/ and never writes master packs, exports, or source files.

What project structure is required to run sp-prd-scan?▼

It requires a spec-kit project structure with a .specify/ directory, and it queries the project-cognition runtime (compass) before broad repository reads. A missing cognition launcher triggers a documented repair or degraded-navigation path.

When does sp-prd-scan refuse to hand off to the build step?▼

Handoff is refused when any critical capability lacks reconstruction-ready evidence or when high capabilities have only path-level evidence. The run is marked blocked-by-gap with the smallest safe repair reported instead of a softened narrative.

Can an interrupted sp-prd-scan run be resumed?▼

Yes. The workflow-state.md file under .specify/prd-runs/<run-id>/ is the resumable state surface; if it shows active_command sp-prd-scan in a non-terminal state, the run resumes from it rather than rebuilding intent from chat history.