prd

Generate structured Product Requirements Documents for DreamCI features and save them to markdown files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pbisogno/DreamCI --skill prd-pbisogno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/pbisogno/DreamCI/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/pbisogno/DreamCI --skill prd-pbisogno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DreamCI feature planning often stalls due to ambiguous requirements and scattered documentation. This Skill automates the creation of a comprehensive PRD that clearly defines scope, goals, user stories, and technical considerations, enabling faster alignment and execution.

Core Features & Use Cases

  • Clarifying Question Generator: Asks 3-5 critical clarifying questions with multiple-choice options to resolve ambiguity.
  • PRD Composer: Generates a structured PRD with sections Introduction/Overview, Goals, User Stories, Functional Requirements, Non-Goals, Technical Considerations, DreamCI Architecture Notes, Success Metrics, and Open Questions.
  • Output & Storage: Saves the finalized PRD to tasks/prd-[feature-name].md.
  • Triggers: Responds to prompts like create a prd, write prd for, plan this feature, requirements for, spec out to initiate PRD generation.

Quick Start

Prompt DreamCI with a feature description and the tool will ask clarifying questions and generate a 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 product requirements document for feature planning?

To generate a product requirements document, provide a feature description and the tool asks 3-5 clarifying questions to resolve ambiguity before composing a structured PRD saved to tasks/prd-[feature-name].md.

What should a PRD include for software feature requirements?

A PRD should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Technical Considerations, Architecture Notes, Success Metrics, and Open Questions to ensure comprehensive feature alignment.

How do I write user stories for a feature spec?

Writing user stories for a feature spec is automated by providing a feature description; the tool resolves ambiguity through multiple-choice questions and structures the stories directly into the PRD.

Can I automate documentation for ambiguous feature requests?

Yes, you can automate documentation for ambiguous requests by triggering the PRD composer with prompts like 'spec out'; it asks targeted clarifying questions to resolve ambiguity before generating the document.

Does automated PRD generation work for DreamCI architecture planning?

Automated PRD generation works for DreamCI architecture planning by structuring inputs into a formal document that includes specific DreamCI Architecture Notes and Technical Considerations sections.