Generate structured Product Requirements Documents from feature prompts.
npx skills add https://github.com/YougLin-dev/Aha-Loop --skill prd-youglin-dev
Please help me install this Agent Skill. Skill: prd Source: https://github.com/YougLin-dev/Aha-Loop/tree/main/.agents/skills/prd Command: npx skills add https://github.com/YougLin-dev/Aha-Loop --skill prd-youglin-dev
Teams often generate PRDs that are vague or incomplete, leading to scope creep and misaligned expectations between product, design, and engineering. This Skill automates creation of comprehensive PRDs from a simple feature prompt, ensuring consistent structure and clear acceptance criteria.
Provide a feature description prompt (e.g., "Add user analytics dashboard") and run the PRD generator to produce a new PRD file under tasks/ (e.g., tasks/prd-<feature-name>.md).
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document, provide a feature prompt like "Add user analytics dashboard" and the tool outputs a complete PRD file with Introduction, Goals, and User Stories. It automatically structures your feature idea into clear functional requirements and success metrics.
A standard PRD includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions. This structure ensures product, design, and engineering teams share clear expectations and prevents scope creep.
To define project scope, the PRD uses dedicated sections for Functional Requirements to list included features and Non-Goals to explicitly mark out-of-scope items. This separation prevents scope creep by aligning product, design, and engineering teams on exact boundaries.
Yes, you can resolve feature ambiguities before writing a PRD using the built-in clarifying question workflow. The tool generates 3-5 essential questions from your feature prompt to identify and resolve missing details before creating the final document.
Yes, the PRD generator outputs actionable markdown files for project kickoffs under a tasks directory, such as tasks/prd-feature-name.md. It includes a Quick Start template with example commands to help teams immediately execute the defined scope.
To track success metrics and open questions for feature planning, the generated PRD enforces specific sections for both. This ensures measurable criteria are documented alongside unresolved technical or design queries for team review.
sbonocAutomate initial scoping and documentation for SDD software projects.
OmexITConvert PRD or design docs into epics, tickets, and acceptance criteria.
diegosanchespereira1Breaks down planning documents into epics and user stories for delivery planning.
jmaglyLocate templates, parse placeholders, and generate validated artifacts.
