What problem does it solve? After a PRD is finalized and the project baseline is frozen, teams still need a single, testable specification that bridges product intent and the actual repository state. This Skill generates that spec.md contract so design, engineering, and verification all work from the same source. ## Core Features & Use Cases - Repo-aware spec generation: Combines prd.md, project-context.md, and bootstrap-result.json into a structured spec.md with fixed sections covering functional requirements, business rules, data needs, API expectations, and error handling. - Acceptance Criteria Mapping: Maps every PRD AC to functional requirements in a fixed table, flagging unmappable criteria as Missing instead of silently dropping them. - Blocking and assumption handling: Distinguishes blocking uncertainties (marked decision_required) from non-blocking assumptions, and emits a structured blocked result when required inputs are missing. - Use Case: After bootstrapping a baseline project and freezing its context, run this Skill to produce a Traditional Chinese spec.md in the PRD artifact directory, ready for spec review, design, and task planning. ## Quick Start Use the prd-context-to-spec skill to generate spec.md from the finalized prd.md and frozen project-context.md in the current PRD run directory.
