interview-me
Overview
Structured requirements interrogation framework inspired by addyosmani/agent-skills. Prevents wasted cycles by transforming vague user intents into crisp, unambiguous architectural constraints through single-question progressive interview loops.
When to Use
Activate whenever:
- User task has underspecified requirements, open UX decisions, or multiple viable architectural trade-offs.
- A high-blast-radius change (database migrations, auth refactor, API contract change) is requested.
- Explicitly triggered via
/spec, /interview, or "ask me questions first".
Rules & Patterns
1. The One-Question-At-A-Time Rule
Never overwhelm the user with a 10-point interrogation form.
- Ask exactly ONE focused question per turn (or at most two tightly-coupled binary options).
- Provide the recommended option first with clear rationale:
"(Recommended) Option A because...".
- Always allow write-in or clarification.
2. The 4 Interrogation Dimensions
Interrogate in this strict priority order:
- Business Outcome & Invariants:
- What core problem does this solve?
- What behavior is strictly forbidden?
- Scope Boundaries (In vs Out):
- What must be delivered in this atomic slice?
- What is explicitly deferred to later?
- Technical Constraints:
- Versions, libraries, database engines, backwards compatibility requirements.
- Edge Cases & Failure Modes:
- What happens on network disconnect, empty response, or unauthorized token?
3. Progressive Synthesis
After each user answer:
- Acknowledge the decision and update the mental model.
- If more critical decisions remain, ask the next question.
- Once 2–4 key questions are resolved, synthesize the formal Feature Spec and transition to
engineering-workflow ([PHASE: Plan]).
Code Examples
Interactive Interview Turn Example
**Question 1 of 3 (Authentication Strategy)**
Before implementing the API authentication layer, we need to align on session storage:
1. **(Recommended) HTTP-only Secure Cookies with Refresh Tokens**:
- *Why*: Immune to XSS token theft, standard for web dashboards.
2. **Bearer Token in Authorization Header**:
- *Why*: Ideal if this API will also be consumed by mobile apps or third-party CLI tools.
Which model fits your architecture best?
Validation Checklist
Common Mistakes
- Asking obvious questions: Asking "Do you want error handling?" instead of making a sensible senior default.
- Interrogation bombardment: Dumping a list of 8 open-ended questions in a single wall of text.
- Ignoring user answers: Asking a question, receiving an answer, and then implementing something else.
Integration Notes
- Runs at the start of
engineering-workflow Phase 1 (/spec).
- Interacts with
gstack-roles ([ROLE: Product Manager] or [ROLE: Architect]).
- Hands off to
ponytail-mindset once scope is defined.
1---2name: interview-me-43description: interview-me4metadata:5 source: https://skillmd.com/skills/kok-o/interview-me-46---7# interview-me89## Overview1011Structured requirements interrogation framework inspired by [addyosmani/agent-skills](https://github.com/addyosmani/agent-skills). Prevents wasted cycles by transforming vague user intents into crisp, unambiguous architectural constraints through single-question progressive interview loops.1213## When to Use1415Activate whenever:1617- User task has underspecified requirements, open UX decisions, or multiple viable architectural trade-offs.18- A high-blast-radius change (database migrations, auth refactor, API contract change) is requested.19- Explicitly triggered via `/spec`, `/interview`, or "ask me questions first".2021## Rules & Patterns2223### 1. The One-Question-At-A-Time Rule2425**Never overwhelm the user with a 10-point interrogation form.**2627- Ask **exactly ONE focused question** per turn (or at most two tightly-coupled binary options).28- Provide the recommended option first with clear rationale: `"(Recommended) Option A because..."`.29- Always allow write-in or clarification.3031### 2. The 4 Interrogation Dimensions3233Interrogate in this strict priority order:34351. **Business Outcome & Invariants**:36 - What core problem does this solve?37 - What behavior is strictly forbidden?382. **Scope Boundaries (In vs Out)**:39 - What must be delivered in this atomic slice?40 - What is explicitly deferred to later?413. **Technical Constraints**:42 - Versions, libraries, database engines, backwards compatibility requirements.434. **Edge Cases & Failure Modes**:44 - What happens on network disconnect, empty response, or unauthorized token?4546### 3. Progressive Synthesis4748After each user answer:4950- Acknowledge the decision and update the mental model.51- If more critical decisions remain, ask the next question.52- Once 2–4 key questions are resolved, synthesize the formal Feature Spec and transition to `engineering-workflow` (`[PHASE: Plan]`).5354---5556## Code Examples5758### Interactive Interview Turn Example5960```markdown61**Question 1 of 3 (Authentication Strategy)**6263Before implementing the API authentication layer, we need to align on session storage:64651. **(Recommended) HTTP-only Secure Cookies with Refresh Tokens**:66 - *Why*: Immune to XSS token theft, standard for web dashboards.672. **Bearer Token in Authorization Header**:68 - *Why*: Ideal if this API will also be consumed by mobile apps or third-party CLI tools.6970Which model fits your architecture best?71```7273---7475## Validation Checklist7677- [ ] Question addresses an actual ambiguity (never ask about obvious defaults).78- [ ] Exactly one question (or two tightly coupled choices) asked.79- [ ] Recommendation provided with clear engineering justification.80- [ ] User response incorporated into the final spec before coding.8182---8384## Common Mistakes8586- **Asking obvious questions**: Asking "Do you want error handling?" instead of making a sensible senior default.87- **Interrogation bombardment**: Dumping a list of 8 open-ended questions in a single wall of text.88- **Ignoring user answers**: Asking a question, receiving an answer, and then implementing something else.8990---9192## Integration Notes9394- Runs at the start of `engineering-workflow` Phase 1 (`/spec`).95- Interacts with `gstack-roles` (`[ROLE: Product Manager]` or `[ROLE: Architect]`).96- Hands off to `ponytail-mindset` once scope is defined.