writing-prd

Generate versioned Full and Lite PRDs with DoR checks and upstream evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wuji-technology/pm-workflow-plugin --skill writing-prd-wuji-technology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-prd
Source: https://github.com/wuji-technology/pm-workflow-plugin/tree/main/skills/writing-prd
Command: npx skills add https://github.com/wuji-technology/pm-workflow-plugin --skill writing-prd-wuji-technology

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about writing-prd

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

FAQPage Schema
How do I convert scattered design specs and informal requirements into a traceable PRD?

Converting scattered design specs into a traceable PRD involves reading and summarizing upstream artifacts into an indexed evidence table. Structured Q&A guides the discovery and definition phases, ensuring the final PRD is testable and ready for developer handoff.

What is the difference between a Full PRD and a Lite PRD for engineering handoff?

A Full PRD provides comprehensive versioned documentation across discovery and delivery workflows, while a Lite PRD is a developer-oriented output focusing on acceptance-criteria-driven stories and tracking plans for direct engineering handoff.

How do I generate developer-ready stories and tracking plans from upstream artifacts?

Generating developer-ready stories involves feeding upstream define, validate, and design artifacts into a layered extraction model. This produces Epic and Story breakdowns with acceptance criteria and tracking plans, ensuring all output is traceable to original evidence.

Can I use existing prototype files to write a PRD and automatically break down Epics and Stories?

Yes, existing prototype and design files can be read and summarized into a PRD. The system applies Definition of Ready checks and automatically breaks down validated requirements into developer-ready Epic and Story structures.

Does writing a PRD require Definition of Ready and quality checks before generating stories?

Yes, applying Definition of Ready and quality self-checks is required before generating stories. This validation ensures versioned Full and Lite PRD outputs meet readiness standards, producing testable contracts for the engineering team.