Clarify project requirements through a structured one-question-at-a-time interview.
npx skills add https://github.com/Arcanada-one/datarim --skill discovery-arcanada-one
Please help me install this Agent Skill. Skill: discovery Source: https://github.com/Arcanada-one/datarim/tree/main/skills/discovery Command: npx skills add https://github.com/Arcanada-one/datarim --skill discovery-arcanada-one
Discovery prevents wasted effort by converting unclear project goals into verified requirements through a structured interview that proposes answers and lets the user confirm or correct them.
Run the discovery interview in /dr-prd to produce a requirements summary with a clear scope, constraints, done criteria, and any open questions.
High-intent search queries and answers about installing and using this skill.
Requirements discovery clarifies vague project needs by running a one-question-at-a-time interview that proposes answers for you to confirm or correct. This structured approach systematically validates scope, constraints, and done criteria before PRD preparation.
Preparing acceptance criteria before a PRD requires running a mode-based requirements discovery interview. By selecting Quick, Standard, or Deep depth, the process outputs a structured requirements summary containing verified scope, explicit done criteria, and tracked open questions.
You can define scope for multi-file features without over-engineering by selecting the Quick or Standard discovery mode. This prevents small fixes from triggering full-scale research while still applying live filesystem scope checks to keep constraints accurate.
Use deep requirements discovery instead of quick mode for major business-impact initiatives that require extensive source-material re-reading and comparative research insights. Quick mode remains sufficient for small fixes and straightforward multi-file features.
Yes, you can ingest optional research insights during the interview workflow. The discovery process applies context safeguards by re-reading source materials and checking existing research to keep the requirements scope accurate and grounded.
azat-ioClarify vague project ideas into goals, scope, and a discovery brief.
kentojeGenerate structured Product Requirements Documents from user prompts.
HahyeonJeonEvaluate Gobbi agent definitions for purpose, scope, and routing alignment.
profmikegreeneFrame pilot analytics scope by defining KPIs, data sources, and analysis approaches.
