skills.rest
CopeeeTang
CopeeeTangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

interview-mode

Clarify user intent through structured interactive questioning before planning.

Updated Mar 6, 2026
Search Tags:#planning#decision making#requirements#tooling#clarification#execution strategy#interactive q&a
One-click install
npx skills add https://github.com/CopeeeTang/copeee-skills --skill interview-mode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-mode
Source: https://github.com/CopeeeTang/copeee-skills/tree/main/skills/interview-mode
Command: npx skills add https://github.com/CopeeeTang/copeee-skills --skill interview-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps resolve ambiguity in a user’s request by turning vague goals into clear, actionable requirements before planning or execution.

Core Features & Use Cases

  • Structured requirement clarification: Guides the user through focused, trade-off-aware choices to surface scope, constraints, and success criteria.
  • Think-Harder analysis: Applies systematic decomposition and evaluation to identify assumptions and execution topology needs.
  • Interactive questioning via AskUserQuestion: Ensures every clarifying question is asked through the Claude Code selection UI (not plain text), enabling precise multi-step intake.
  • Planning-ready output: Produces a structured requirements summary and recommends an execution strategy for the next phase.

Quick Start

Use the interview-mode skill by asking the AI to run /interview for your task so it will ask the necessary selection questions and then summarize requirements for planning.

Frequently Asked Questions about interview-mode

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

FAQPage Schema
How do I clarify project requirements before planning and execution?▼

Structured interactive questioning resolves ambiguity by guiding you through trade-off-aware choices to surface scope, constraints, and success criteria before planning begins.

What is the best way to scope a partially specified software request?▼

Systematic decomposition and evaluation identifies assumptions and execution topology needs, producing a planning-ready requirements summary for the next phase.

How do I use interactive Q&A for task scoping and constraint discovery?▼

Interactive Q&A for task scoping asks every clarifying question through a selection UI, enabling precise multi-step intake to align on trade-offs and success criteria.

Does structured requirement clarification work for complex software engineering tasks?▼

Structured requirement clarification applies directly to task scoping, constraint discovery, and success-criteria alignment across complex or partially specified software engineering requests.

When should I not use interactive questioning for requirements gathering?▼

You should avoid interactive questioning for requirements gathering when a task is already fully specified with no ambiguity, as the process exists to resolve vague goals and surface missing constraints.

Related Skills

Explore More Software Engineering Skills→
sbonocsbonoc

blueprint-sdd-step01-intake

Automate initial scoping and documentation for SDD software projects.

Community
Intermediate
droxeydroxey
1

writing-plans

Translate software specs into file-aware implementation plans with test strategy.

Community
Basic
martialarconmartialarcon
1

architecture

Analyze requirements and document architectural decisions with Architecture Decision Records.

Community
Intermediate
wilsonkichoiwilsonkichoi
3

auto

Run the execute-review-fix-verify pipeline for a wave or milestone.

Community
Advanced