sp-prd-build

Compiles a validated scan reconstruction package into a delivery-grade PRD suite.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a repository reconstruction scan completes, teams still need to turn raw scan packets, ledgers, and machine-readable contracts into a coherent, traceable PRD suite without re-scanning the codebase or losing evidence labels. ## Core Features & Use Cases - Bundle-Grounded Compilation: Builds the master pack and exports strictly from the .specify/prd-runs/<run-id>/ scan package, never from new repository rereads. - Reverse Coverage Validation: Verifies traceability of every reconstruction claim back to scan evidence and preserves Evidence, Inference, and Unknown labels. - Classification-Aware Exports: Keeps ui, service, and mixed project semantics explicit across the exported PRD documents. - Use Case: After sp-prd-scan produces a validated reconstruction package for a legacy service, run this Skill to generate master-pack.md, prd.md, and supporting contract exports with full traceability, or get a structured refusal routing back to the scan step when critical gaps remain. ## Quick Start Invoke /sp-prd-build with the validated PRD run ID to compile the scan package into the final PRD suite.

Frequently Asked Questions about sp-prd-build

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

FAQPage Schema
How do I build a PRD from a spec-kit reconstruction scan?▼

Run /sp-prd-build with the validated PRD run ID after sp-prd-scan completes. It reads the run bundle under .specify/prd-runs/<run-id>/, compiles master/master-pack.md, and renders the exports directory including prd.md and contract documents.

What inputs does sp-prd-build require before running?▼

It requires the scan workspace containing workflow-state.md, prd-scan.md, coverage and capability ledgers, artifact contracts, reconstruction checklist, machine-readable contracts like config-contracts.json and state-machines.json, scan packets, and worker results.

Can sp-prd-build fill gaps by re-reading the repository?▼

No. The scan package is the only authoritative fact source, and the No New Facts Gate forbids repository rereads. When critical evidence is missing, the build refuses completion and routes back to sp-prd-scan with the smallest safe repair.

Why does sp-prd-build refuse to complete a build?▼

Refusal happens when required scan artifacts are missing or malformed, worker results are shallow, claims lack traceability, critical unknowns remain unresolved, or export landing for critical artifacts is missing. The blocked state records the failed check and repair path.

Does sp-prd-build handle UI and service projects differently?▼

Yes. Classification-aware export rules keep UI-facing behaviors explicit for ui runs, service, API, CLI, and runtime contracts explicit for service runs, and preserve both surfaces for mixed runs rather than collapsing to one side.