Generate a Product Requirements Document with clarifying questions and numbered requirements.
npx skills add https://github.com/ivanrvpereira/.agents --skill prd-ivanrvpereira
Please help me install this Agent Skill. Skill: prd Source: https://github.com/ivanrvpereira/.agents/tree/main/skills/prd Command: npx skills add https://github.com/ivanrvpereira/.agents --skill prd-ivanrvpereira
A PRD (Product Requirements Document) turns a vague idea into a clear, testable plan that developers can execute without guessing.
Tell the agent: "Create a PRD for a new feature that [briefly describe the feature], including clarifying questions and a complete PRD saved to tasks/prd-[feature-name].md."
High-intent search queries and answers about installing and using this skill.
To write a PRD for a new feature, provide a brief feature idea to the agent. It asks 3 to 5 clarifying questions to resolve ambiguity, then generates a complete PRD with user stories, acceptance criteria, and functional requirements.
Product requirements documentation should include goals, user stories with verifiable acceptance criteria, numbered functional requirements, non-goals, and success metrics to turn a vague idea into a testable plan for developers.
You generate acceptance criteria and user stories by submitting your feature idea to the agent. It drives structured discovery by asking lettered clarifying questions to resolve ambiguity before writing the testable requirements into a PRD.
Yes, you can plan a feature and produce requirement specs without starting implementation. The process focuses entirely on planning and documentation, saving the result to a markdown file without building the feature.
The best way to resolve ambiguity when spec writing for product planning is to answer 3 to 5 essential clarifying questions with lettered options before drafting the document, ensuring the resulting functional requirements are verifiable.
sixtycat2000-ctrlGenerate structured Product Requirements Documents from feature descriptions and clarifying questions.
richardwuGenerate structured markdown PRDs with user stories and acceptance criteria.
mmartinsolivCreate structured product requirements documents with user stories and success metrics.
zhixuan312Audit prose artifacts for ambiguity and gaps across four subtypes.
