What problem does it solve?
Product teams struggle to convert scattered research, design specs, and informal requirements into a single, traceable, and testable PRD; this Skill streamlines that process by extracting upstream evidence, guiding structured Q&A, and enforcing readiness and quality checks so teams can hand off clear developer contracts.
Core Features & Use Cases
- Upstream extraction: Read and summarize define/validate/design/handoff artifacts into an indexed §0 evidence table and layered extraction model.
- Guided interview flow: Multi-step, phase-aware prompts that produce structured inputs for discovery, definition, and delivery paths (A/B/C/D).
- Full → Lite generation: Produce versioned Full PRD and developer-oriented Lite PRD files with naming conventions, DoR/quality self-checks, Story/Epic breakdowns, tracking plans, and optional upload to Lark MCP.
- Use case: Convert a set of define/design/prototype files into a PRD, generate AC-driven Stories, and output Lite PRD for engineering handoff.
Quick Start
Use the writing-prd skill to generate a Full PRD and a Lite PRD for product "studio" feature "data-recording" from available upstream artifacts and guided answers.