authoring-prd

Guides authoring and amending product requirements documents to a plannable quality bar.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill authoring-prd-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authoring-prd
Source: https://github.com/bm629/agent-skills/tree/main/skills/authoring-prd
Command: npx skills add https://github.com/bm629/agent-skills --skill authoring-prd-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a raw product idea into a PRD that engineers can actually plan milestones from is hard: problems get asserted without evidence, metrics are unmeasurable, NFRs stay vague, and scope creeps without an MVP boundary. This Skill supplies the authoring method that fills a PRD template with grounded, decision-complete content. ## Core Features & Use Cases - Evidence-grounded method: Frames the problem as a job-to-be-done backed by research, defines 2-4 measurable success metrics with guardrails, and draws a defensible MVP boundary with explicit non-goals. - NFR taxonomy with numeric targets: Covers performance, availability, security, accessibility (WCAG 2.2 AA), and more, each with checkable targets proportional to the product archetype. - Versioned amendments: Edits an existing PRD in place as a versioned delta with changelog, superseded-content marking, and ripple analysis instead of silent rewrites. - Use Case: Hand the agent a product idea for a freelancer invoicing tool; it researches the domain, fills the PRD template with an evidenced problem, measurable metrics, traceable features with acceptance criteria, and a 12-condition self-check before handoff. ## Quick Start Use authoring-prd to turn my product idea for a freelancer invoicing tool into a comprehensive PRD an engineer can plan milestones from.

Frequently Asked Questions about authoring-prd

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

FAQPage Schema
How do I write a PRD from a product idea?

Start from a PRD template's section structure, then ground each section in evidence: frame the problem as a job-to-be-done, define 2-4 measurable success metrics with targets, draw an explicit MVP boundary with non-goals, and write testable acceptance criteria for every user story.

What makes a PRD good enough for engineers to plan from?

A plannable PRD has an evidenced problem, defined personas, measurable metrics with guardrails, a defensible MVP boundary, concrete features with acceptance criteria, numeric NFR targets, named dependencies, and full traceability from problem to goal to metric to feature.

How do I amend an existing PRD without rewriting it?

Edit only the affected requirements in place, bump the document version, add a changelog entry recording who, when, what changed and why, mark superseded content explicitly, and trace the ripple impact on acceptance criteria, metrics, and downstream docs.

What non-functional requirements should a PRD include?

Include the load-bearing NFR categories for your product archetype, each with a numeric target: performance (p95 latency), availability (an SLO), security, privacy, accessibility (WCAG 2.2 AA floor), scalability, and compliance where applicable.

When should I not use a PRD authoring skill?

Do not use it to review or grade a finished PRD (use a reviewing skill instead), to author other document types like feature specs or technical designs, or for trivial changes that need no requirements document.