write-prd

Convert user intent into a structured Markdown PRD with user stories.

9|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Dawn-Technology/aicelerate --skill write-prd-dawn-technology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/Dawn-Technology/aicelerate/tree/main/plugins/aimate/skills/write-prd
Command: npx skills add https://github.com/Dawn-Technology/aicelerate --skill write-prd-dawn-technology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an ambiguous idea into a clear, shared product plan by guiding you through problem understanding, design alignment, and documentation into a complete PRD.

Core Features & Use Cases

  • User interview + requirement discovery: Collects a long, detailed problem description and then interviews you deeply to resolve uncertainties and dependencies in the design.
  • Repo-aware exploration: Explores the existing codebase to verify assertions and understand the current state before drafting the PRD.
  • Component-focused planning: Identifies major components to build or modify, emphasizes extracting deep, testable components, and confirms expected testing scope.
  • PRD authoring with user stories: Produces an extensive PRD including problem statement, solution, highly detailed sequentially numbered user stories with acceptance criteria, implementation decisions, testing decisions, and out-of-scope items.
  • Docs output automation: Saves the PRD as a Markdown file under docs/spec using the date and feature name, creating the folder if needed and versioning when a file already exists.

Quick Start

Ask: “Explore the current repository, interview me to clarify requirements and design decisions, then write a complete PRD with user stories and acceptance criteria for a new feature called <feature-name>.”

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I write a PRD with user stories and acceptance criteria for a new feature?

To write a PRD with user stories, you collect detailed requirements, validate them against the existing codebase, and generate sequentially numbered user stories with explicit acceptance criteria.

What is the best way to turn ambiguous requirements into a structured product plan?

Turning ambiguous requirements into a structured product plan involves conducting an interactive interview to resolve uncertainties, identifying major components to modify, and documenting testing decisions and out-of-scope items.

How do I generate a PRD that validates existing codebase components?

Generating a PRD that validates existing components requires exploring the repository to understand the current state before drafting, ensuring deep component identification aligns with the actual codebase architecture.

Can I automatically save a PRD as a Markdown file under docs/spec with versioning?

Yes, you can automatically save a PRD as a Markdown file under docs/spec, which creates the folder if needed and applies date and feature name versioning when a file with the same name already exists.

Does writing a PRD with acceptance criteria require manual testing scope definition?

Writing a PRD with acceptance criteria automates testing scope definition by extracting deep, testable components during the planning phase and confirming the expected testing decisions directly with you.