prd

Convert feature prompts into structured PRDs with goals and acceptance criteria.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/craftwerk-studio/claude-boilerplate --skill prd-craftwerk-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/craftwerk-studio/claude-boilerplate/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/craftwerk-studio/claude-boilerplate --skill prd-craftwerk-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork and fragmentation that often accompany planning a new feature by converting vague prompts into a complete PRD.

Core Features & Use Cases

  • Structured PRD with goals, user stories, acceptance criteria, and technical sections.
  • Clarifying Questions to resolve ambiguity before PRD creation.
  • Automatic persistence by saving to tasks/prd-[feature-name].md for traceability and handoff.

Quick Start

Provide a feature prompt and receive a complete PRD saved to tasks/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 generate a PRD from a feature idea for product backlog grooming?

Provide a feature prompt and the tool generates a complete PRD with goals, user stories, and acceptance criteria, saving it to tasks/prd-[feature-name].md for backlog grooming.

What is included in a structured PRD for new feature planning?

A structured PRD includes goals, user stories, acceptance criteria, functional sections, and non-goal sections to guide product development and documentation during early-stage planning.

How are ambiguous feature prompts handled during PRD creation?

The tool asks clarifying questions to resolve ambiguity before PRD creation, ensuring the final product requirements document accurately captures the intended feature scope.

Can I use this for early-stage feature ideation across product teams?

Yes, it applies to early-stage planning, feature ideation, and backlog grooming across product teams, converting vague prompts into structured documentation for development handoff.

Where are generated product requirements documents saved for traceability?

Generated PRDs are automatically saved to tasks/prd-[feature-name].md, providing automatic persistence for traceability and seamless handoff to development teams.