Guide strategic questioning to produce comprehensive product requirements documents.
npx skills add https://github.com/alysonhower/dupcheck --skill clavix-prd
Please help me install this Agent Skill. Skill: clavix-prd Source: https://github.com/alysonhower/dupcheck/tree/main/.agent/skills/clavix-prd Command: npx skills add https://github.com/alysonhower/dupcheck --skill clavix-prd
Clavix-PRD streamlines the creation of robust Product Requirements Documents by guiding teams through a focused, strategic questioning process. It ensures problems, goals, constraints, and success criteria are clearly articulated before design or development begins.
Describe the feature you want to plan, and I will start PRD development with strategic questions.
High-intent search queries and answers about installing and using this skill.
To write a PRD that prevents scope creep, use guided strategic questioning to define explicit out-of-scope boundaries, problem statements, and acceptance criteria before development begins.
The best way to structure product requirements is through a comprehensive PRD that clearly articulates problems, goals, constraints, and success criteria to ensure cross-functional alignment.
You can generate a quick reference PRD by running a dual output process that produces both a comprehensive document and a concise version for rapid stakeholder reviews.
Yes, you can use strategic questioning during feature planning to uncover critical details and generate task breakdowns, ensuring comprehensive specs are ready for engineering handoff.
You need to define out-of-scope constraints in a PRD during initial roadmap discussions to establish quality controls and prevent scope creep before design or development starts.
compozyGuide structured PRD development with brainstorming, codebase research, and ADR creation.
BellaBeDefine acceptance criteria and generate validation plans with measurable metrics.
adminsairolotech-bitGenerate PRDs, user stories, and roadmaps with templates and DACI mapping.
foomakersGenerate or update Product Requirements Documents through hypothesis-driven questioning and iterative review.
