requirement-clarification

Requirement Clarification

Overview

Intercept and clarify ambiguous user instructions before execution.

---

When to Use

Use this skill when:

• User instruction contains missing critical information
• References are vague ("that", "this", "there" without context)
• Statement is non-affirmative (questions, conditionals, suggestions)
• Scope or quality criteria are unclear
• High-risk operations (Git, file changes, config updates) are requested

Trigger Threshold: Score >= 30 or any mandatory trigger condition

---

Prerequisites

• Understanding of the user's current context
• Knowledge of state-changing vs read-only operations
• Familiarity with confirmation vocabulary (preparing vs approving)

---

Workflow

Step 1: Ambiguity Detection

Calculate ambiguity score (0-100):

Factor	Score
Missing critical parameter	+25 each
Vague reference	+15 each
Non-affirmative statement	+20
Scope ambiguity	+10
Conditional clause	+15
High-risk operation	+25
Non-confirmation word (准备 (Preparing)/考虑 (Considering)/研究 (Studying/Researching)/讨论 (Discussing))	+20

Thresholds:

• 0-29: Proceed directly
• 30-59: Light clarification (1-2 questions)
• 60-89: Deep clarification (structured interview)
• 90+: Reject (too ambiguous)

Step 2: Mandatory Pause Check

Before ANY state-changing action, ask:

"Stop. Does this change state? Yes. Is it confirmed? No. Go confirm."

Triggers mandatory pause:

• Score >= 30
• Git operations (branch, commit, push, merge)
• File creation/deletion/moving
• Configuration changes
• "Preparing" words detected without "approving" context

Step 3: Clarification Strategy

Single Question Focus: Ask ONE critical question at a time.

Provide Sensible Defaults:

Target path?
- A) ./backup/ (backup directory)
- B) ./archive/ (archive directory)
- C) Other: _____

Use Concrete Examples:

Performance target?
Examples:
- "Startup time < 3 seconds"
- "Memory usage < 100MB"
- "QPS > 1000"