prd-writer

Generate a structured PRD from a discovery brief and ADRs.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill prd-writer-shakhovskiya-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/solo-sdlc/skills/prd-writer
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill prd-writer-shakhovskiya-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing PRDs from feature discovery briefs is repetitive and error-prone. This skill automates turning validated briefs into a structured PRD that clearly defines goals, scope, functional and non-functional requirements, acceptance criteria, data models, and hand-off notes to architecture.

Core Features & Use Cases

  • Reads inputs such as docs/specs/<feature>/brief.md and docs/specs/<feature>/glossary.md (if present) to inform requirements.
  • Outputs a complete PRD at docs/specs/<feature>/prd.md with sections: Background, Goals, Non-goals, FRs, NFRs, Data Model, External Dependencies, User Stories, and Open Questions.
  • Generates a ready-to-review PRD suitable for architecture planning, sign-off, and hand-off to implementation.

Quick Start

Provide a confirmed feature brief and request the PRD when you want the document generated.

Frequently Asked Questions about prd-writer

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

FAQPage Schema
How do I generate a PRD from a feature discovery brief?

To generate a PRD from a feature discovery brief, provide the confirmed brief at docs/specs/<feature>/brief.md. The skill reads this input along with any present glossary.md files and ADRs to output a structured PRD at docs/specs/<feature>/prd.md.

What sections are included in a production-ready PRD?

A production-ready PRD includes Background, Goals, Non-goals, Functional Requirements, Non-functional Requirements, Data Model, External Dependencies, User Stories, and Open Questions sections. It also enforces measurable targets and explicit acceptance criteria for v1 sign-off.

Do I need architecture decision records to write functional and non-functional requirements?

You do not need architecture decision records to write functional and non-functional requirements, but the skill reads ADRs from docs/architecture when available. It combines these with your brief and glossary to inform the final PRD structure.

What is the best way to structure hand-off notes for architecture planning?

The best way to structure hand-off notes for architecture planning is to generate a PRD with dedicated sections for External Dependencies, Data Model, and Open Questions. This ensures architecture teams receive measurable targets and explicit acceptance criteria.

Can I use a glossary file to define terms for my product requirements document?

You can use a glossary file to define terms for your product requirements document by placing glossary.md inside docs/specs/<feature>/. The skill reads this file alongside your brief.md to accurately inform the generated PRD.