Structured Interview

Extract precise team requirements through staged, single-direction questioning.

54|16|Updated Feb 2, 2026

Search Tags:#planning #scoping #requirements #discovery #clarification #interview

Ready to run

npx skills add https://github.com/chemistrywow31/A-Team --skill structured-interview

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Structured Interview
Source: https://github.com/chemistrywow31/A-Team/tree/main/.agents/skills/structured-interview
Command: npx skills add https://github.com/chemistrywow31/A-Team --skill structured-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague user requests into a precise requirements summary, ensuring clarity on scope, workflow, roles, and constraints before team generation.

Core Features & Use Cases

Staged Questioning: Guides users through a structured, single-direction interview process.
Requirement Refinement: Clarifies ambiguous inputs and identifies missing details.
Use Case: When a user says "I need a content team," this skill will ask targeted questions to define the team's exact deliverables, required roles, and operational boundaries.

Quick Start

Use the structured interview skill to refine the requirements for a new content team.

Frequently Asked Questions about Structured Interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract precise requirements from vague project requests?▼

Requirement extraction uses a staged, single-direction questioning process to transform vague requests into confirmed summaries. It applies a funnel method with follow-up triggers and reverse validation to clarify scope, workflow, and constraints.

What is the best way to scope team roles and operational boundaries before project execution?▼

Scoping team roles requires a structured interview process that refines ambiguous inputs into confirmed requirements summaries. This method identifies missing details regarding exact deliverables, required roles, and operational boundaries.

How does a structured interview process work for project discovery?▼

Structured interviewing works by guiding users through staged questioning to clarify user wishes. It utilizes a funnel method to drill down from broad requests, applying reverse validation to ensure comprehensive requirement gathering.

When do I need to use a funnel method for requirement clarification?▼

You need a funnel method for requirement clarification when initial user requests lack explicit scope and workflow details. It is essential for identifying missing details and confirming operational constraints before team generation.

Can I use reverse validation to check my requirements summary?▼

Yes, you can use reverse validation to check your requirements summary by verifying the gathered details against the original user wishes. This ensures comprehensive requirement gathering and confirms explicit scope and role coverage.

What are the limitations of using a single-direction questioning process for requirements gathering?▼

The limitation of a single-direction questioning process is that it restricts users to staged, sequential prompts rather than open dialogue. This structured approach focuses strictly on extracting explicit scope and constraints, which may limit spontaneous requirement discovery.