prd

Generate Draft PRDs from domain templates with pre-filled author and date.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mrcsXndr/unnamed-bot --skill prd-mrcsxndr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/mrcsXndr/unnamed-bot/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/mrcsXndr/unnamed-bot --skill prd-mrcsxndr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start-to-finish creation of Product Requirements Documents (PRDs) from domain-specific templates, reducing setup time and ensuring consistency across projects.

Core Features & Use Cases

  • Locate and apply domain templates from templates/ and pre-fill author/date from context/me.md.
  • Auto-generate a Draft PRD under projects/<Domain>/PRDs/<title-slug>.md and enforce domain-specific constraints surfaced from context.

Quick Start

Create a PRD by selecting a domain, pulling a template, and pre-filling author and date.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I automatically generate a Product Requirements Document from a domain template?

To generate a Product Requirements Document, the system reads domain templates from a templates directory, pre-fills author and date context, and scaffolds the file automatically.

What is the best way to standardize PRD creation across multiple product domains?

Standardizing PRD creation across multiple product domains is achieved by enforcing domain-specific constraints and guards during document generation, ensuring consistent structure and status enforcement for new product initiatives.

How do I set up my environment to automatically pre-fill author and date in PRD templates?

To pre-fill author and date in PRD templates, you must first configure a context file named me.md, which the automation reads to inject user identity and timestamps into the generated document scaffolding.

Can I use this automation for feature proposals and multi-domain programs?

Yes, you can use this automation for feature proposals and multi-domain programs because the scaffolding process dynamically locates and applies domain-specific templates based on the selected product initiative context.

Where are the generated Draft PRDs saved when using domain template automation?

Generated Draft PRDs are saved as markdown files using a title-slug naming convention under the projects/<Domain>/PRDs/ directory structure, enforcing a Draft status upon file creation.