draft-prd

Drafts a Product Requirements Document from strategy sources into a structured markdown file.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill draft-prd-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-prd
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/draft-prd
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill draft-prd-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product ideas and founder notes often live in scattered conversations and backlog entries with no structured requirements document, making it impossible to trace shipped work back to strategic intent. This Skill turns a North Star, OKR Key Result, BACKLOG entry, or raw notes into a properly structured PRD with mandatory sections and explicit strategy linkage. ## Core Features & Use Cases - Guided synthesis flow: Reads all source material, clusters concerns into 5-8 themes, and confirms the framing with you before drafting anything. - Fixed 8-section template: Produces a PRD with mandatory H2 sections (Problem, Audience, Goals, Non-goals, Success metrics, Key requirements, Constraints, Open questions) using the project template verbatim. - Strategy linkage enforcement: Requires a Source line referencing the upstream OKR, North Star section, or BACKLOG entry so requirements never drift from intent. - Use Case: You have a backlog entry that needs more specification before becoming an Epic. Point the Skill at the entry, confirm the clustered themes and draft, and it writes PRD-<slug>.md to your requirements folder ready for review. ## Quick Start Ask the assistant to draft a PRD from your OKR file or pasted founder notes and provide a kebab-case slug for the output file.

Frequently Asked Questions about draft-prd

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

FAQPage Schema
How do I draft a PRD from founder notes or a backlog entry?

Provide the source material (a file path or pasted notes) plus a kebab-case slug. The Skill reads the source, clusters concerns into themes for your confirmation, drafts the 8 mandatory sections, and saves the PRD after your review.

What sections must a PRD template include?

This workflow mandates exactly 8 H2 sections: Problem, Audience, Goals, Non-goals, Success metrics, Key requirements, Constraints, and Open questions. Headings are fixed and exact-matched because downstream skills and testplans reference them by string.

Does the PRD need to link back to OKRs or a North Star?

Yes. The PRD's Source header line must reference its upstream OKR Key Result, North Star section, or BACKLOG entry. This strategy-linkage rule prevents requirements from drifting away from stated intent.

Can I edit the PRD before it is saved to the repo?

Yes. The full draft is shown in chat before any file is written, and the Skill asks targeted questions about non-goals, measurable success metrics, and gaps. The file is only saved after you confirm or provide edits.

What happens after a PRD is drafted?

The PRD is saved with Status set to draft awaiting your review. The next step is running the draft-epic command, which turns the approved PRD into an Epic that commits the work.