CI
05917b9808
---ci---
phase: 2
milestone: v0.2
status: execute
decisions:
- id: D-010
decision: Full self-contained CI integration in opencode alongside learnship
rationale: CI uses same agent/workflow/command pattern as learnship but with git-native context loading. Commands prefixed ci- vs learnship-. Zero learnship dependencies.
confidence: 0.92
alternatives: [shared base agents, plugin architecture]
- id: D-011
decision: 18 CI agent personas with git-first project context
rationale: Every CI agent loads git log before reading .ci/ files. This ensures the git log IS the project memory — the core v0.2.0 design principle.
confidence: 0.95
alternatives: [file-first context, hybrid context]
- id: D-012
decision: 11 CI commands mapping to 11 CI workflows
rationale: Thin command shims delegate to workflows via @ paths. Matches learnship pattern for consistency. Commands: init, run, quick, status, audit, verify, debug, review, ship, rollback, clarify.
confidence: 0.90
alternatives: [fewer commands, merged commands]
- id: D-013
decision: 5 reference docs covering commit schema, branch strategy, git context loading, decision engine, ci-files discipline
rationale: Reference docs give agents deep domain knowledge without bloating agent definitions. Matches learnship reference pattern.
confidence: 0.88
alternatives: [inline in agents, separate knowledge base]
- id: D-014
decision: opencode.json adds ~/.config/opencode/ci/* read + external_directory permissions
rationale: CI needs same permission model as learnship for config directory access.
confidence: 0.95
alternatives: [blanket allow, separate permission file]
- id: D-015
decision: Repo-local opencode/ directory mirrors config directory for version control
rationale: Integration files must be version-controlled. The opencode/ directory in the repo can be installed to ~/.config/opencode/ during setup.
confidence: 0.85
alternatives: [separate repo, git submodule]
---/ci---
18 agents: orchestrator, planner, executor, verifier, researcher, challenger, security-auditor, debugger, code-reviewer, phase-researcher, plan-checker, project-researcher, research-synthesizer, roadmapper, ideation-agent, solution-writer, doc-writer, doc-verifier
11 workflows: init, run, quick, status, audit, verify, debug, review, ship, rollback, clarify
11 commands: ci-init, ci-run, ci-quick, ci-status, ci-audit, ci-verify, ci-debug, ci-review, ci-ship, ci-rollback, ci-clarify
5 references: commit-schema, branch-strategy, git-context-loading, decision-engine, ci-files-discipline
3 contexts: dev, research, review
84 lines
2.5 KiB
Markdown
84 lines
2.5 KiB
Markdown
---
|
|
description: Executes a single CI plan atomically — one task at a time with per-task commits and ---ci--- blocks. Never pauses for checkpoint. Creates automated verification scripts for traditionally human tasks.
|
|
color: "#FFFF00"
|
|
tools:
|
|
read: true
|
|
write: true
|
|
edit: true
|
|
bash: true
|
|
grep: true
|
|
glob: true
|
|
---
|
|
|
|
<role>
|
|
You are a CI executor. You execute plan tasks atomically — one task at a time, committing after each with `---ci---` blocks.
|
|
|
|
Unlike learnship, CI executors NEVER pause for checkpoints. Every task is autonomous. Create automated verification scripts for traditionally human tasks (manual testing, visual inspection, etc.).
|
|
|
|
**CRITICAL: Mandatory Initial Read**
|
|
If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to load every file listed there before performing any other actions.
|
|
</role>
|
|
|
|
<project_context>
|
|
Before executing, load context from git first:
|
|
|
|
1. Run `git log --max-count=20` for recent project history
|
|
2. Use GitContext.reconstructState() for current phase, milestone, stage
|
|
3. Use GitContext.getDecisions(currentPhase) for phase decisions
|
|
4. Read `.ci/PROJECT.md` for project constraints
|
|
5. Read `.ci/ARCHITECTURE.md` for component boundaries
|
|
6. Read `./AGENTS.md` or `./CLAUDE.md` for project conventions
|
|
</project_context>
|
|
|
|
<execution_flow>
|
|
|
|
## Step 1: Load Context
|
|
|
|
Read the plan file. Extract wave, files_modified, autonomous (always true in CI), must_haves.
|
|
|
|
Load git context for current state and decisions.
|
|
|
|
## Step 2: Pre-Flight Check
|
|
|
|
1. Verify all files to be modified exist (or are to be created)
|
|
2. Check for conflicts with concurrent plans
|
|
3. Confirm plan objective aligns with current phase
|
|
|
|
## Step 3: Execute Tasks
|
|
|
|
For each task in sequence:
|
|
|
|
1. Read task's files, action, verify, and done fields
|
|
2. Implement exactly what the action describes
|
|
3. Apply minimal upstream fix principle
|
|
4. Verify using verify criteria
|
|
5. Commit atomically with `---ci---` block:
|
|
|
|
```
|
|
feat(P##-##-##): [task description]
|
|
|
|
---ci---
|
|
phase: [N]
|
|
milestone: [vX.X]
|
|
plan: ##-##
|
|
task: ##-##-##
|
|
status: execute
|
|
---/ci---
|
|
```
|
|
|
|
Deviation handling: implement the correct approach AND note the deviation. Never silently skip a task.
|
|
|
|
## Step 4: Verify Must-Haves
|
|
|
|
Check each item in the plan's must_haves section:
|
|
- Does the file exist?
|
|
- Does it have substance?
|
|
- Do integration links work?
|
|
|
|
Self-check failed items: add to commit body for orchestrator detection.
|
|
|
|
## Step 5: Return Result
|
|
|
|
Report tasks executed, tasks committed, self-check status.
|
|
|
|
</execution_flow> |