This skill should be used when the user asks to 'clarify requirements', 'resolve uncertainties', 'answer spec questions', or when auto-triggered by /opencode-specify with >3 NEEDS CLARIFICATION markers. Systematically surfaces and resolves ambiguities in specifications.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
This skill should be used when the user asks to 'clarify requirements', 'resolve uncertainties', 'answer spec questions', or when auto-triggered by /opencode-specify with >3 NEEDS CLARIFICATION markers. Systematically surfaces and resolves ambiguities in specifications.
Clarify - Systematic Uncertainty Resolution
Scan specifications for ambiguities and resolve them through structured questioning. Produces cleaner specs that feed into architecture and planning.
Triggers:
Auto-triggered by /opencode-specify when >3 [NEEDS CLARIFICATION] markers
Manual: /opencode-clarify to review current spec
Manual: /opencode-clarify path/to/spec.md for specific spec
Process
1. Load Specification
Find active spec:
# Most recent specls -t .claude/specs/*/spec.md | head -1
Impact: How much does this affect architecture, data model, task breakdown, or testing?
Uncertainty: How unclear is this currently?
Take top 5 questions maximum per clarify session.
6. Generate Questions
Format rules:
Multiple choice (2-5 options) preferred
If open-ended: constrain to ≤5 word answer
One question at a time
Include context from spec
Question template:
## Question 1 of 5**Context:** FR-003 states "System MUST validate user input"
**Question:** What validation rules apply to email addresses?
**Options:**
A) RFC 5322 strict validation
B) Simple format check (contains @ and .)
C) Format check + DNS MX record verification
D) Custom business rules (please specify)
**Impact:** Affects error messages, test cases, and integration complexity.
7. Apply Answers Immediately
After each answer:
Update spec.md - replace marker with resolved requirement
Log to .claude/specs/{slug}/clarifications/log.md
Before:
- FR-003: System MUST validate email [NEEDS CLARIFICATION: validation rules]
After:
- FR-003: System MUST validate email format (RFC 5322) and verify domain has MX record
Clarification log entry:
## 2025-01-29: Email Validation Rules**Question:** What validation rules apply to email addresses?
**Answer:** RFC 5322 + MX verification (Option C)
**Updated:** FR-003
**Rationale:** Balance strictness with user experience, catch typos in domain
**Question:** How should the system handle failed payment attempts?
A) Retry automatically up to 3 times
B) Notify user immediately, no retry
C) Queue for manual review
D) Combination (specify)
Constrained Open-Ended
**Question:** Maximum file upload size? (≤5 words)
Example answers: "10MB", "50MB per file", "No limit"
Binary with Justification
**Question:** Should inactive users be auto-deleted?
A) Yes - after [specify duration]
B) No - keep indefinitely
If yes, what defines "inactive"?
Handling Technical Uncertainties
Some markers are technical (HOW, not WHAT). Don't resolve these in clarify.
Technical markers → arch-lead:
[NEEDS CLARIFICATION: which database?]
[NEEDS CLARIFICATION: sync or async processing?]
[NEEDS CLARIFICATION: API design]
Flag for arch-lead:
## Technical Uncertainties (for Architecture)
These require technical research, not stakeholder input:
1. FR-015: Processing approach (sync/async) - arch-lead to evaluate
2. NFR-003: Database selection based on scale requirements
Deferral
Some questions can't be answered yet. Mark as deferred:
- FR-020: System MUST integrate with payment provider [DEFERRED: vendor selection pending]
Deferred items:
Don't block spec completion
Must have clear unblock condition
Tracked in clarification log
Completion Criteria
Clarify session complete when:
All explicit markers addressed (resolved or deferred)
No implicit ambiguities in P1 scenarios
Coverage summary shows no Outstanding in critical categories
Remaining markers ≤ 3 (threshold for arch-lead handoff)
Output
Updates to:
.claude/specs/{slug}/spec.md - markers replaced with answers
.claude/specs/{slug}/clarifications/log.md - decision history
