Generate a structured Product Requirements Document from a feature description.
npx skills add https://github.com/bamecho/my-claude-skills --skill prd-bamecho
Please help me install this Agent Skill. Skill: prd Source: https://github.com/bamecho/my-claude-skills/tree/main/skill-en/prd Command: npx skills add https://github.com/bamecho/my-claude-skills --skill prd-bamecho
This skill automates the creation of a comprehensive Product Requirements Document (PRD) from a concise feature description, reducing ambiguity and ensuring a consistent planning artifact.
Provide a feature description and I will return a complete PRD ready for review.
High-intent search queries and answers about installing and using this skill.
To generate a Product Requirements Document, provide a concise feature description and the skill asks 3-5 clarifying questions to resolve ambiguity. It then outputs a structured PRD with sections like User Stories and Acceptance Criteria, saving it to a markdown file.
An automated PRD includes Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, Non-Goals, Design and Technical Considerations, Success Metrics, and Open Questions. This ensures verifiable acceptance criteria and rigorous planning.
Writing user stories and acceptance criteria is handled by providing a feature description to the skill. It asks clarifying questions to refine the scope, then automatically structures these elements into a production-ready PRD format.
You do not need to provide full technical specifications to create a structured PRD. A concise feature description is sufficient, as the skill asks 3-5 essential clarifying questions to resolve ambiguity and build out the technical considerations.
The best way to define non-goals and functional requirements is to input a brief feature description for automated PRD generation. The skill structures these elements into a standardized document, ensuring clear boundaries and implementation readiness.
Yes, you can save a generated PRD for task tracking. The skill automatically persists the final structured document to a designated path as a markdown file, enabling sharing and iteration.
aspelldennyDistill raw research notes into concise bullets for vision docs.
shishiVerify Definition of Done and acceptance criteria for sprint increments.
product-on-purposeGenerate user stories and Given/When/Then acceptance criteria from product requirements.
CoWork-OSGenerates structured Product Requirements Documents with goals, user stories, and acceptance criteria.
