interview-framework

Solid

This skill should be used when running an interactive interview before a spec phase, gathering requirements through dialogue, asking the user clarifying questions before delegating to a subagent, or when any Ralph phase command (research, requirements, design, tasks) needs adaptive brainstorming dialogue. Covers the 3-phase algorithm (Understand, Propose Approaches, Confirm and Store).

AI & Automation 339 stars 21 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
84
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Interview Framework Adaptive brainstorming dialogue algorithm for all spec phases. Each phase command provides its own exploration territory (phase-specific areas to probe). ## Option Limit Rule Each question must have 2-4 options (max 4). Keep the most relevant options, combine similar ones. ## Recommendation Format Every question asked via `AskUserQuestion` in Phase 1 leads with the recommended option (except when options are symmetric, in which case `[Recommended]` may be omitted): ```yaml AskUserQuestion: question: "[Context-aware question referencing prior answers]. [One sentence rationale for the recommendation.]" options: - "[Recommended] [Option text -- the AI's suggested answer]" - "[Alternative 1]" - "[Alternative 2 if needed]" - "Other" ``` Rules: - `[Recommended]` is a label prefix on the first option only. - The rationale sits in the question text, not the option label. - Option count still 2-4 max (Option Limit Rule preserved). - If there is no meaningful recommendation (truly symmetric choice), omit the `[Recommended]` label rather than placing it arbitrarily. Example: ```yaml AskUserQuestion: question: "Where should the spec live? You only have one specs directory configured, so the default is fine unless you want to reorganize." options: - "[Recommended] ./specs/ (default)" - "Let me configure a different path" - "Other" ``` ## Codebase-First Exploration Before asking any question, determine whether the answer ...

Details

Author
tzachbon
Repository
tzachbon/smart-ralph
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

phxbrainstorm

Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.

384 Updated 4 days ago
oliver-kriska
AI & Automation Listed

idea-interviewer

Use this skill whenever the user has something in their head — a vision, instinct, judgment, or pattern they recognize — but can't put it into words yet. Triggers on signals like "I can see it but can't explain", "I'm confused", "hard to describe", "I have a feeling but no words for it", "I know what I want but can't articulate", "ฉันงง", "อธิบายไม่ถูก", "พูดไม่ออก", "อธิบายยาก", or when the user trails off, contradicts themselves mid-sentence, or restarts an explanation. Also triggers at the start of a new project, when stuck midway, or when moving to a new chunk of work. The skill runs a phased interview that pulls the structure out of what the user already knows but can't articulate — and converts it into a usable model — decision tree, ruleset, workflow, or system prompt. Vague, confused, or restart-mid-sentence answers are exactly the signal this skill is built for. Do not skip it just because the user can't explain clearly — that inability is the whole point.

0 Updated 4 days ago
kcholakorn
AI & Automation Listed

spec-interview

Conducts a deep, multi-round interview to clarify ambiguous requirements and produces a structured specification document. Automatically discovers requirement files and asks probing, non-obvious questions across technical implementation, UX/UI, trade-offs, edge cases, and architectural decisions.

2 Updated today
evandirsaul01021
AI & Automation Listed

discuss-phase

Extract implementation gray areas + capture decisions via AskUserQuestion modes. Use when scoping a phase before planning, or to lock unknowns.

1 Updated yesterday
produtoramaxvision
Data & Documents Solid

plan-interview

Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.

162 Updated 2 weeks ago
secondsky