2.3 KiB
description
| description |
|---|
| Clarify CI project ambiguities — generate questions, accept defaults at full autonomy, present at supervised/guided |
CI Clarify
Run the clarification phase for the current CI project. Generate questions about ambiguities, accept defaults automatically at full autonomy, or present to the user at supervised/guided levels.
Usage: ci-clarify [phase_number]
Step 0: Confirm Active Project
Check ci listProjects() or read .ci/config.json to determine if multi-project mode is active.
If .ci/config.json has projects[] with length > 0:
- Confirm
active_projectis correct for this clarification - If not, set it with
ci setActiveProject(<slug>) - All commit messages must include
project: <slug>in---ci---block
If single-project mode: proceed with existing conventions.
Step 1: Load Git Context
git log --max-count=20
git branch -a
Read .ci/PROJECT.md and .ci/REQUIREMENTS.md for the specification.
Step 2: Identify Ambiguities
Analyze the specification and requirements for:
- Undefined terms — words with multiple interpretations
- Missing boundaries — requirements without clear success criteria
- Conflicting constraints — requirements that contradict each other
- Implicit assumptions — things taken for granted but not stated
- Scope ambiguity — unclear what is in/out of scope
Step 3: Generate Questions
For each ambiguity, generate a clarify question with:
- The question text
- A default answer (CI's best guess)
- The reasoning for the default
Step 4: Resolve Questions
Based on autonomy level:
| Level | Behavior |
|---|---|
full |
Accept all defaults automatically, log decisions |
supervised |
Present questions, accept defaults after timeout |
guided |
Present questions, wait for every answer |
Step 5: Commit Clarifications
decision(P##): clarification — [topic]
---ci---
phase: [N]
milestone: [vX.X]
status: clarify
decisions:
- id: D-XXX
decision: [clarified choice]
rationale: [why this answer]
confidence: 0.XX
alternatives: [alt1, alt2]
---/ci---
Step 6: Update .ci/ Files
Update .ci/PROJECT.md with clarified requirements.
Update .ci/REQUIREMENTS.md with refined requirements.
Step 7: Report
Report clarifications made, decisions logged, confidence levels.