Generate a structured PRD from a feature description with clarifying questions.
npx skills add https://github.com/dennywu2966/denny-all-in-one --skill prd-dennywu2966
Please help me install this Agent Skill. Skill: prd Source: https://github.com/dennywu2966/denny-all-in-one/tree/main/home/.claude/skills/prd Command: npx skills add https://github.com/dennywu2966/denny-all-in-one --skill prd-dennywu2966
Generates a clear, structured PRD from a feature idea by guiding you through clarifying questions and delivering an implementable specification.
Provide a feature description and let the skill generate a complete PRD draft.
High-intent search queries and answers about installing and using this skill.
To generate a PRD, provide a brief feature description. The skill asks 3-5 clarifying questions to resolve ambiguity, then outputs a structured document with user stories, acceptance criteria, and functional requirements.
A generated product requirements document includes Introduction, Goals, User Stories with acceptance criteria, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.
Write user stories and acceptance criteria by providing a brief feature idea. The skill resolves ambiguity through interactive clarifying questions and structures the output into actionable specifications for implementation.
Generating a PRD does not require external product management tools. It operates independently without dependencies, directly translating feature ideas into structured specifications within your environment.
Generated PRD files are saved automatically to tasks/prd-[feature-name].md. This markdown format ensures traceability and provides an actionable guide for implementation and stakeholder review.
The best way to align stakeholders is using interactive clarifying questions. The skill asks 3-5 targeted questions to resolve ambiguity early, ensuring the final product requirements document reflects shared understanding.
sixtycat2000-ctrlGenerate structured Product Requirements Documents from feature descriptions and clarifying questions.
htlin222Generate structured implementation workflows from PRDs and feature requirements.
HigorAlvesGenerates markdown PRDs from structured interviews about problem, target users, success metrics, scope, and open questions.
qa-amanDraft measurable acceptance criteria using Robertson's Fit Criteria.
