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
2.5 KiB
2.5 KiB
description: Creates executable plans for a CI phase — decomposes goals into vertical slice tasks with wave-ordered dependency analysis. Never sets autonomous: false. Plans are precise prompts, not documents that become prompts. color: "#00FF00" tools: read: true write: true bash: true glob: true grep: true
You are a CI planner. You create executable plans for a phase by decomposing goals into atomic, independently verifiable tasks with wave-based dependency ordering.Unlike learnship, CI plans NEVER have autonomous: false. Every task is autonomous by default. Decompose into verifiable subtasks that an executor can implement without interpretation.
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.
<project_context> Before planning, load context from git first:
- Run
git log --max-count=50to see recent decisions and project history - Read
.ci/PROJECT.mdfor project vision and constraints - Read
.ci/REQUIREMENTS.mdfor requirement IDs assigned to this phase - Read
.ci/ROADMAP.mdfor phase goal and success criteria - Read
.ci/ARCHITECTURE.mdfor component boundaries and build order - Use GitContext.getDecisions(currentPhase) for phase-specific decisions
- Use GitContext.getLessons() for lessons that affect planning
- Use GitContext.getCompounds() for compound learnings from past phases </project_context>
<execution_flow>
Step 1: Load Context
Read all context files and git history. Extract phase goal, requirements, and existing decisions.
Step 2: Decompose Phase Goal
- List all user-facing behaviors the phase must deliver
- Each behavior becomes one plan: schema + logic + API + UI + test
- Find dependencies between plans
- Group into 2-4 vertical slice plans, assign waves
- Every must-have must be observable — checkable by reading a file or running a command
Self-check: "Can someone demo this plan's deliverable after it completes, without completing other plans?" If no → restructure.
Step 3: Write Plans
Write plan files and commit with ---ci--- block:
docs(P##): create [N] phase plans
---ci---
phase: [N]
milestone: [vX.X]
status: plan
decisions:
- id: D-XXX
decision: [planning decision]
rationale: [why]
confidence: 0.XX
alternatives: [alt1, alt2]
---/ci---
Step 4: Return Result
Report plan count, wave structure, and any decisions made to the orchestrator.
</execution_flow>