Generate structured PRD documents with goals, scope, and acceptance criteria.
npx skills add https://github.com/deepnoodle-ai/creddit --skill prd-deepnoodle-ai
Please help me install this Agent Skill. Skill: prd Source: https://github.com/deepnoodle-ai/creddit/tree/main/.claude/skills/prd Command: npx skills add https://github.com/deepnoodle-ai/creddit --skill prd-deepnoodle-ai
Create concise, high-quality PRDs that align teams on what to build and why, and ensure each section adds clarity to decision-making.
Ask clarifying questions to resolve ambiguity, then generate and save a concise PRD to tasks/prd-[feature-name].md.
High-intent search queries and answers about installing and using this skill.
Create a concise PRD by generating structured sections including a header, problem framing, goals, user stories, and acceptance criteria to guide development and align teams on product scope.
Write user stories and acceptance criteria by embedding them directly into your PRD structure, using clarifying questions to resolve ambiguity and define clear product goals and success metrics for development guidance.
Document product specifications by following a structured PRD template that requires a header, problem and opportunity analysis, goals, user stories, and acceptance criteria to ensure comprehensive coverage and team alignment.
Yes, you can collaboratively review and save versioned product requirement documents to tasks/prd-[feature-name].md, ensuring teams stay aligned on the latest product specifications and scope definitions.
Yes, generating a PRD requires answering clarifying questions to resolve ambiguity and gather inputs before producing the final concise document with defined product goals, scope, and success criteria.
Product management documentation should include a header, problem and opportunity framing, goals, user stories, and acceptance criteria to ensure each section adds clarity to decision-making and guides development.
kevinlinGenerate a structured PRD with problem statements, goals, user stories, and acceptance criteria.
ArvorCoConvert user stories from tasks.md into GitHub issues via the gh CLI.
belokonmCoordinate product strategy, roadmaps, and requirements across teams.
igor1309Review architecture specifications for completeness, abstraction, and separation of concerns.
