interview-framework
FeaturedThis 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).
Install
Quality Score: 94/100
Skill Content
Details
- Author
- tzachbon
- Repository
- tzachbon/smart-ralph
- Created
- 6 months ago
- Last Updated
- 5 days ago
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
interview-me
Clarify what the user actually wants before specs, plans, or code. Use when an ask is underspecified, when the user says "interview me", "grill me", "stress-test my thinking", or when you would otherwise fill in important product/architecture assumptions silently.
guided-interview
Conduct a structured, one-question-at-a-time interview to explore a specific topic or decision — each question offers 3-4 concrete, mutually exclusive options plus a free-text path, and later questions adapt to prior answers rather than following a fixed script. Ends with a recap the user confirms before finalizing, and only then produces a synthesized answer or (when the interview clearly feeds downstream work) a written brief. NOT for open-ended ambiguity-surfacing (use socratic-method) or single-fact lookups.
specify
Interview the user to produce a complete, agent-ready specification, then emit what is needed to build it: for a coded feature/agent a phase-scoped build prompt, or for a skill / declarative agent the artifact itself (SKILL.md / AGENT.md). Surfaces every assumption for review, slices the work into a phased plan, and runs a build-readiness (model/effort) check. Use when the user wants to design, specify, plan, or scope a new agent, feature, or skill; turn a vague idea, PRD, or plan into a rigorous spec; write requirements in EARS / SHALL with testable acceptance criteria; produce a build prompt for a coding agent; or amend, advance, review, audit or sweep an existing spec under specs/ for drift and staleness. Reasoning-driven, one question at a time.