Generate a structured PRD markdown file from a feature brief.
npx skills add https://github.com/grenos/gh-viewer --skill prd-grenos
Please help me install this Agent Skill. Skill: prd Source: https://github.com/grenos/gh-viewer/tree/main/.claude/skills/prd Command: npx skills add https://github.com/grenos/gh-viewer --skill prd-grenos
PRD creation is often manual, error-prone, and time-consuming, leading to misaligned expectations and scope drift.
Provide a concise feature brief and I will generate a complete PRD document ready for engineering.
High-intent search queries and answers about installing and using this skill.
To generate a PRD, provide a concise feature brief and the skill drafts a complete document. It asks clarifying questions to resolve ambiguity, then outputs a markdown file with goals, user stories, and requirements.
A product requirements document includes Introduction, Goals, User Stories with Acceptance Criteria, Functional and Non-Functional Requirements, and Open Questions. This structure ensures engineering alignment and prevents scope drift.
You document user stories and acceptance criteria by providing a feature brief to be drafted into a structured PRD. The generated markdown file pairs each story with clear criteria to guide engineering implementation.
Yes, you can automate PRD creation by inputting a feature description. The skill handles the formatting and auto-saves the structured markdown file to tasks/prd-[feature-name].md for traceability and versioning.
Yes, the PRD generator asks clarifying questions to resolve ambiguity before writing the document. This ensures the final product requirements accurately capture stakeholder expectations and technical needs.
The best way to align stakeholders is generating a structured PRD that explicitly separates functional and non-functional requirements. This prevents misaligned expectations and reduces scope drift during engineering.
qa-amanDraft a structured PRD from a brief or problem statement.
u1pnsTranslate business concepts into structured PRDs with user flows and scope.
bearbinaryConverts Markdown PRDs into structured JSON task files with progress tracking.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
