interview
/interview
Structured requirements gathering through a series of questions. Use when the task is described verbally/informally (not from an issue tracker ticket) and scope, AC, and edge cases need clarifying before work starts.
- Author
- akovalion ↗
- Repository
- paranoid-qa ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Structured requirements gathering through a series of questions. Use when the task is described verbally/informally (not from an issue tracker ticket) and scope, AC, and edge cases need clarifying before work starts.
Original author description
Structured requirements gathering through a series of questions. Use when the task is described verbally/informally (not from an issue tracker ticket) and scope, AC, and edge cases need clarifying before work starts.
How it works
- When to apply
- Process
- Output format
- What to prefer
SKILL.md preview
--- name: interview description: Structured requirements gathering through a series of questions. Use when the task is described verbally/informally (not from an issue tracker ticket) and scope, AC, and edge cases need clarifying before work starts. allowed-tools: — AskUserQuestion — Write --- # Interview: requirements gathering through questions Help the user turn an informal task description into complete requirements ready to hand off to the `test-cases` or `testing` skills. ## When to apply - The task is described verbally or in general terms, without a ticket - No AC, no mockups, no clear scope - The user is unsure what exactly to test/automate If the task already comes from an issue tracker (Jira etc.) with a full description — this skill is not needed: gather context straight from the ticket (via the tracker's MCP: description, comments, attachments, linked issues) and hand off to `test-cases`. ## Process **Round 1: scope and context.** Ask 3-4 questions via `AskUserQuestion`: - What exactly is being checked (feature, page, element) - Where it lives (URL, screen, navigation path) - Task type (new functionality / regression / bug) - Platforms (desktop / mobile / both) **Round 2: behavior and AC.** Based on the round 1 answers: - Happy path — what behavior counts as correct - Edge cases — which negative scenarios matter - UI states (loading, error, empty, disabled) — if applicable - Integrations — any APIs / external services **Round 3: clarifications on remaining gaps.** Only if critical gaps remain after rounds 1-2. Group related questions. Maximum 3 rounds. If the requirements are still incomplete — log the gaps as "Questions for the analyst/PM" and work with what you have. ## Output format Once the interview is done, assemble a structured summary: ```markdown # Requirements: <short task name> ## Context - Type: <new feature / regression / bug> - Platforms: <desktop / mobile / both> - URL / location: <…> ## Scope <what exactly is being checked, briefly> ## Acceptance Criteria - <AC 1> - <AC 2> ## Scenarios **Happy path:** <description> **Edge cases:** - <case 1> - <case 2> ## Integrations <APIs, external services — if any> ## Open questions for the analyst/PM - <question 1> ``` Save the summary to an md file (e.g. `requirements_<task_name>.md` in the current working directory) and offer to hand it off to `test-cases` or `testing`. ## What to prefer - 4 precise questions beat 10 boilerplate ones - Tie questions to the previous round's answers instead of running down a checklist - If the user answers "don't know" — log it as a question for the analyst, do not push - Use concrete answer options in questions (AskUserQuestion options), not open-ended wording
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · akovalion/paranoid-qa | 100 | MIT |
| q00/ouroboros | 100 | MIT |
| vanducng/skills | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| mthines/agent-skills | 100 | MIT |
| r3dlex/oh-my-auggie | 100 | Apache-2.0 |
| YuDefine/nuxt-supabase-starter | 100 | MIT |
| biliboss/skills | 100 | MIT |
| Soe-Reh/soes-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version fcef774ba635 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100product-requirements
Turn a vague idea into a testable PRD: problem, users, journeys, scope, edge cases, acceptance criteria. Use when starting a product or feature, clarifying requirements, or writing user stories. - 100gathering-requirements
Use when eliciting or clarifying feature requirements, defining scope, identifying constraints, or capturing user needs. Triggers: 'what are the requirements', 'define the requirements', 'scope this feature', 'user stories', 'acceptance criteria', 'what should this do', 'what… - 86team-shinchan:requirements
Use when you need to discover hidden requirements, risks, or edge cases. - 100requirement-enhancer
Iteratively enhance user requirements into clear, complete, actionable specifications through analysis and clarification. Use when: (1) Users provide initial requirements that need refinement, (2) Requirements are vague, incomplete, or ambiguous, (3) Creating formal… - 100analyze-and-plan
Use this when you need to define acceptance criteria, write requirements, scope work, or create a definition of done for AEM Edge Delivery Services (EDS) tasks such as new blocks, variants, behavior modifications, CSS-only changes, or bug fixes. Covers analyzing development… - 100system-design-interview-clarifying-requirements
Use this skill when scoping ambiguous system design prompts by defining boundaries, features, and operational SLAs in the first 5 minutes.