Gather requirements and clarify unknowns through adaptive multi-round interviews.
npx skills add https://github.com/robertdp/claude-code-skills --skill interview-robertdp
Please help me install this Agent Skill. Skill: interview Source: https://github.com/robertdp/claude-code-skills/tree/main/skills/interview Command: npx skills add https://github.com/robertdp/claude-code-skills --skill interview-robertdp
This Skill helps you gather requirements, surface unknowns, and clarify tradeoffs before making decisions or starting implementation. It reduces rework by turning vague requests into structured, verified understanding.
Use the interview skill to gather requirements for my project and identify the key constraints, unknowns, and tradeoffs before we plan the work.
High-intent search queries and answers about installing and using this skill.
Requirements gathering before implementation involves adaptive multi-round questioning to clarify unknowns, identify constraints, and surface tradeoffs. This approach turns vague requests into structured, verified understanding of goals, assumptions, and risks, reducing rework.
Structured questioning for debugging is needed when a problem lacks clear reproduction steps or root cause context. Adaptive interviews help verify assumptions, gather relevant context from codebase or web sources, and frame the tradeoffs before applying a fix.
Planning a feature with unclear constraints requires adaptive multi-round interviews that ask focused questions, verify answers against codebase structure, and summarize goals, assumptions, and risks into actionable next steps before implementation begins.
Yes, adaptive questioning frames implementation tradeoff analysis by organizing technical and product conversations into structured constraints, assumptions, and risks. It asks targeted questions per round and adjusts based on your answers to clarify the best path forward.
Requirements gathering applies to technical, product, and debugging conversations alike. It uses adaptive multi-round interviews to clarify unknowns, verify context from code or external sources, and structure decisions across different domains.
Feature planning fails without clarifying unknowns because vague requests hide critical constraints, assumptions, and risks. Structured requirements gathering surfaces these factors through adaptive questioning and context verification before implementation begins.
wachawoGather user context and codebase insights to create GitHub issues.
SethyPagnaCreates workspace-safe markdown implementation plans in .jarvis/plans/.
patrobCoordinate three parallel research agents and validate findings against the codebase.
OpenWaggleAnalyzes code repositories to generate structured project requirement documents.
