skills.rest
bnadlerjr
bnadlerjrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-prds

Translate product briefs into structured PRDs with scope, use cases, and milestones.

5|1|Updated Sep 6, 2009
Search Tags:#workflow#requirements#milestones#prd#product-management#use-cases
One-click install
npx skills add https://github.com/bnadlerjr/dotfiles --skill writing-prds-bnadlerjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-prds
Source: https://github.com/bnadlerjr/dotfiles/tree/main/claude/skills/writing-prds
Command: npx skills add https://github.com/bnadlerjr/dotfiles --skill writing-prds-bnadlerjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform scattered product briefs into a structured Product Requirements Document (PRD) that guides engineers, designers, and product teams from vision to actionable specifications.

Core Features & Use Cases

  • Build Product Requirements Documents from Product Briefs, producing high-level design principles, use case compendiums, and milestone definitions.
  • Follow a guided workflow (Extraction, High-Level Requirements, Use Case Compendium, Milestone Definition, Review) to ensure traceability and completeness.
  • Use workflow references (workflow-phases.md) and examples (kabletown example) to anchor PRD quality.

Quick Start

Provide a product brief (or a path to it) and the assistant will extract the core thesis, define scenarios, and draft a complete PRD with a Milestone 1 scope.

Frequently Asked Questions about writing-prds

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

FAQPage Schema
How do I turn a product brief into a structured PRD?▼

To turn a product brief into a structured PRD, the skill extracts the core thesis, defines high-level design principles, and generates a use-case compendium with milestone definitions. It translates briefs into actionable specifications ensuring scope and stakeholder alignment.

What is the best way to define MVP scope and milestones from product requirements?▼

Defining MVP scope and milestones from product requirements is best handled by enforcing guardrails for future extensions while establishing traceability from scenarios. The workflow extracts high-level requirements to isolate initial milestone deliverables.

How does traceability from scenarios to requirements work in a product requirements document?▼

Traceability from scenarios to requirements works by converting product discovery scenarios into a unified use-case compendium. This guided workflow extracts high-level requirements and ensures each use case maps directly to defined milestones.

Can I use product discovery outputs to generate use cases for my PRD?▼

Yes, you can use product discovery outputs to generate use cases for your PRD. The workflow explicitly applies these outputs alongside design principles to convert scenarios into a unified use-case compendium for stakeholder alignment.

What phases are involved when converting a product brief into actionable specifications?▼

Converting a product brief into actionable specifications involves five guided phases: Extraction, High-Level Requirements, Use Case Compendium, Milestone Definition, and Review. This workflow ensures completeness from vision to final scope.

Related Skills

Explore More Product & Management Skills→
saranskumarsaranskumar

product-philosophy-extractor

Extract a product thesis, guiding principles, wedge, and non-goals from founder briefs.

Community
Intermediate
SolaneHubSolaneHub

gh-issue-creator

Create and edit GitHub issues with naming conventions, project assignment, and milestone tracking.

Community
Intermediate
roberttmadsen13-delroberttmadsen13-del

user-story-mapping

Visualize user journeys into a story map with activities, steps, and tasks.

Community
Intermediate
zazzcodezazzcode
3

feature-doc-builder

Create and evolve feature documents with purpose, current state, and milestones.

Community
Advanced