prd-author

Generate structured PRD drafts from templates, research, and domain context.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill prd-author-cmbays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-author
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/prd-author
Command: npx skills add https://github.com/cmbays/mokumo --skill prd-author-cmbays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of structured Product Requirements Documents (PRDs) by synthesizing various sources of information, reducing manual drafting time and ensuring comprehensive coverage.

Core Features & Use Cases

  • Structured PRD Generation: Creates PRDs following a defined template, incorporating competitive analysis, domain context, and technical constraints.
  • Contextual Synthesis: Pulls information from existing PRD templates, past PRDs, competitive research, domain context, and architecture documentation.
  • Use Case: When starting a new feature, use this Skill to generate a first draft of the PRD by providing the feature name and problem statement, allowing you to quickly move to the review and refinement stage.

Quick Start

Use the prd-author skill to generate a PRD for a new feature called 'user authentication'.

Frequently Asked Questions about prd-author

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

FAQPage Schema
How do I generate a product requirements document from competitive research and domain context?

Generating a product requirements document from competitive research requires synthesizing existing architecture constraints and past PRDs into a structured draft. This Skill automates that synthesis, pulling from specified file paths to produce a comprehensive PRD template for review.

What is the best way to draft a PRD using past templates and architecture documentation?

Drafting a PRD using past templates involves contextual synthesis of prior documents and architecture constraints. Provide the feature name and problem statement, and the Skill automatically generates a structured first draft by integrating these sources.

Can I review and approve a PRD draft before it is saved to disk?

Reviewing and approving a PRD draft before saving to disk is required. The Skill follows an audit, suggest, and approve pattern, presenting the synthesized draft for human review and refinement before any file writes occur.

Do I need specific file paths to synthesize competitive analysis into a PRD?

Specific file paths for PRD templates, competitive research, and domain context are required. Access to these defined locations is necessary for the Skill to pull and synthesize the information needed to generate the structured document.

How does research synthesis work when generating product requirements for a new feature?

Research synthesis for product requirements works by aggregating domain context, competitive analysis, and technical architecture constraints. The Skill processes these inputs to create a structured draft, ensuring comprehensive coverage and reducing manual drafting time.

What are the limitations of automating PRD generation from existing documentation?

Limitations of automating PRD generation include the reliance on pre-existing file paths for competitive research and domain context. The Skill cannot draft documents without these inputs and requires human approval during the audit phase before writing the final PRD to disk.