skills.rest
Samaara-Das
Samaara-DasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prd

Draft focused mini PRDs for Stock Buddy features with requirements and acceptance criteria.

Updated Aug 23, 2026
Search Tags:#workflow#documentation#prd#product-requirements#feature-design#stock-buddy
One-click install
npx skills add https://github.com/Samaara-Das/money-hungry-games --skill prd-samaara-das
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/Samaara-Das/money-hungry-games/tree/main/.claude/skills/PRD-generator
Command: npx skills add https://github.com/Samaara-Das/money-hungry-games --skill prd-samaara-das

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to convert scattered notes and vague requests into a precise, shareable Product Requirements Document (PRD) that guides development and validation. This skill provides a structured, repeatable process to capture problems, scope, success criteria, and implementation details for Stock Buddy feature additions, reducing ambiguity and misalignment.

Core Features & Use Cases

  • Discovery interview-driven: clarifies problem, scope, and acceptance criteria before drafting.
  • PRD lifecycle: saves to .claude/prd-[kebab-case-feature-name].md with a fixed structure that serves as the single source of truth.
  • Comprehensive content: includes user stories, functional requirements, UI specs, display logic, behavior rules, data changes, and UAT scenarios.

Quick Start

Describe a feature for Stock Buddy and I will generate a focused mini PRD saved as .claude/prd-[feature-name].md.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document for a new feature?▼

To write a product requirements document, this skill conducts a discovery interview to clarify problem scope and rules, then drafts a PRD with user stories, functional requirements, UI specs, and UAT scenarios.

What should be included in a PRD for feature design?▼

A PRD for feature design should include user stories, functional requirements, UI specs, display logic, behavior rules, data changes, and UAT scenarios to ensure actionable development and validation.

How do I turn scattered feature notes into a structured PRD workflow?▼

Turning scattered notes into a structured PRD workflow requires a discovery interview to clarify vague requests, followed by drafting a concise document capturing scope, requirements, and acceptance criteria.

Can I generate acceptance criteria and user stories before writing the full PRD?▼

Yes, you can generate acceptance criteria and user stories before the full PRD. The workflow starts with a discovery interview to define problem scope and rules before drafting the complete requirements document.

How are PRDs saved and formatted for team alignment?▼

PRDs are saved as markdown files at .claude/prd-[kebab-case-feature-name].md, providing a fixed structure that serves as the single source of truth for team development and validation.

Does this PRD workflow work for Stock Buddy feature additions specifically?▼

Yes, this PRD workflow is designed for Stock Buddy feature additions, capturing problem scope, implementation details, and acceptance criteria tailored to the Stock Buddy application context.

Related Skills

Explore More Product & Management Skills→
LucasMatuszewskiLucasMatuszewski
2

write-a-prd

Create Markdown product requirements documents from idea and interview inputs.

Community
Advanced
mahg-esmahg-es
3

uat-generate

Generate complete UAT packages with traceability matrices and acceptance sections.

Official
Advanced
bearbinarybearbinary

prd-to-json

Converts Markdown PRDs into structured JSON task files with progress tracking.

Official
Intermediate
AgLyx3AgLyx3

product-manager-toolkit

Organize product workflows with RICE prioritization, PRD templates, and GTM checklists.

Community
Advanced