Create Product Requirements Documents through collaborative questions and codebase examination.
npx skills add https://github.com/Thomas-Fitz/auto-scrum --skill as-prd
Please help me install this Agent Skill. Skill: as-prd Source: https://github.com/Thomas-Fitz/auto-scrum/tree/main/skills/as-prd Command: npx skills add https://github.com/Thomas-Fitz/auto-scrum --skill as-prd
This Skill automates the creation of comprehensive Product Requirements Documents, reducing the time and effort required for thorough documentation and ensuring no critical details are overlooked.
To create a Product Requirements Document for a new feature, use the command: as-prd new-feature.
High-intent search queries and answers about installing and using this skill.
You can automate Product Requirements Document creation by using a collaborative AI to ask targeted questions and examine your codebase, validating assumptions to ensure comprehensive and measurable software documentation.
The best way to ensure a PRD covers technical requirements is using automated validation that checks your codebase for gaps and verifies completeness, measurability, and testability before final user approval.
Yes, you can generate a PRD by analyzing an existing codebase, which allows the collaborative AI to validate assumptions, identify potential gaps, and automatically draft detailed product requirements.
Collaborative AI improves software documentation by engaging users with targeted questions and validating codebase context, ensuring development teams produce comprehensive, validated PRDs that guide development effectively.
The user approval process for AI-generated product requirements allows stakeholders to review the validated documentation and approve it before proceeding to the next phase of software development.
No specific framework is needed to create product requirements collaboratively, as the process relies on guiding user questions and examining your existing codebase without requiring external dependencies.
gabbelloAnalyze business requirements against a codebase to generate strategic context.
yukikmDocument technical architecture decisions, diagrams, and data models.
bobmatnycDispatch a code-reviewer subagent to review changes against plans and requirements.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
