- README.md: title, project name, CLI commands, .ci/ → .ciagent/, ci-files → ciagent-files, CI Modification → CIAgent Modification - AGENTS.md: title, project name, architecture tree, agent count (18→19), test count (25→31 suites, 218→370 tests), version (0.4.0→0.6.0), ci-files → ciagent-files, CIConfig → CIAgentConfig, CiMetadata → CIAgentMetadata, .ci/ → .ciagent/ - templates/DECISIONS.md: .ci/audit/ → .ciagent/audit/, ci audit → ciagent audit - scripts/postinstall.js: CI postinstall → CIAgent postinstall - scripts/install.sh: CI → CIAgent, ci-init → ciagent-init, INSTALL COMPLETE banner - opencode/ci/workflows/*.md (11 files): .ci/ → .ciagent/, CI → CIAgent project name, ci-command → ciagent-command usage lines - opencode/ci/references/*.md (5 files): .ci/ → .ciagent/, CI → CIAgent project name, ci-files → ciagent-files references - opencode/ci/contexts/*.md (3 files): .ci/ → .ciagent/, CI → CIAgent project name - opencode/agents/ci-*.md (18 files): .ci/ → .ciagent/, CI → CIAgent project name - opencode/command/ci-*.md (11 files): CI → CIAgent project name Preserved: ---ci---/---/ci--- markers, opencode/ci/ dir paths, ci-*.md filenames, ci listProjects()/ci setActiveProject() API names, repo URLs ---ci--- phase: 1 milestone: v0.6 plan: 01-01 task: 01-01-01 status: execute ---/ci---
2.4 KiB
description
| description |
|---|
| Clarify CIAgent project ambiguities — generate questions, accept defaults at full autonomy, present at supervised/guided |
CIAgent Clarify
Run the clarification phase for the current CIAgent project. Generate questions about ambiguities, accept defaults automatically at full autonomy, or present to the user at supervised/guided levels.
Usage: ciagent-clarify [phase_number]
Step 0: Confirm Active Project
Check ci listProjects() or read .ciagent/config.json to determine if multi-project mode is active.
If .ciagent/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 .ciagent/PROJECT.md and .ciagent/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 .ciagent/PROJECT.md with clarified requirements.
Update .ciagent/REQUIREMENTS.md with refined requirements.
Step 7: Report
Report clarifications made, decisions logged, confidence levels.