Interview users one question at a time to clarify plan-file requirements.
npx skills add https://github.com/BenjaminG/ai-skills --skill interview-benjaming
Please help me install this Agent Skill. Skill: interview Source: https://github.com/BenjaminG/ai-skills/tree/main/interview Command: npx skills add https://github.com/BenjaminG/ai-skills --skill interview-benjaming
This Skill helps teams clarify plan-file requirements before drafting a specification, reducing ambiguity and rework.
Start the interview by referencing a plan file (e.g., plan.yaml). Ask one focused question at a time about technical details, UI/UX decisions, concerns, tradeoffs, edge cases, and dependencies. After each answer, decide whether to continue or summarize and ask where to write the spec. Continue until the user says "done" or all meaningful questions are exhausted.
High-intent search queries and answers about installing and using this skill.
To clarify plan requirements before drafting a specification, you can run a guided one-question-at-a-time interview. This process surfaces technical details, UI/UX decisions, edge cases, and dependencies, then summarizes findings to reduce ambiguity and rework.
A one-question interview for plan refinement is a process that prompts you sequentially to elicit project details. By asking focused questions individually about tradeoffs and concerns, it ensures all meaningful requirements are gathered before writing the spec.
You resolve ambiguity in UI/UX decisions and technical dependencies by applying an interview process during plan refinement. It guides you through targeted prompts to uncover hidden concerns and edge cases, producing a concise summary for your specification.
Yes, you can use a guided interview to identify edge cases in project planning. The interview asks one focused question at a time about your plan file, specifically targeting edge cases, tradeoffs, and dependencies to ensure comprehensive requirement coverage.
The best way to gather requirements for a plan-based project is conducting sequential interviews that reference your plan file. This method extracts technical details and UI/UX decisions one question at a time, then indicates exactly where to write the spec.
You should stop the requirement interview and start writing the spec when all meaningful questions are exhausted or you explicitly indicate you are done. The process then provides a concise summary of findings and recommends next steps for drafting the specification.
zabuuqInterview project stakeholders to define scope and generate docs/scope.md.
rodrigobranasTranslate PRD requirements into technical specifications with ADRs.
hashi-demo-labOrchestrate Terraform module planning with human approval gates.
pxlcrtivGuide collaborative design brainstorming through user intent exploration and design validation.
