Files

T

CI 05917b9808 feat(P02): add opencode integration layer — agents, workflows, commands, references, contexts

---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

2026-05-29 13:27:00 +00:00

2.4 KiB

Raw Blame History

description

description
Initialize a new CI project — specification → clarify → create .ci/ reference files → initial commit

CI Init

Initialize a new CI project with specification parsing, clarification, and .ci/ reference file creation.

Usage: ci-init [description]

Step 1: Check Prerequisites

Verify git is initialized:

[ -d .git ] && echo "GIT_EXISTS" || echo "NO_GIT"

If NO_GIT: git init

Check if .ci/config.json already exists:

[ -f .ci/config.json ] && echo "ALREADY_INITIALIZED" || echo "NEW"

If ALREADY_INITIALIZED: stop. Use ci-status to see project state.

Step 2: Parse Specification

If a description was provided, use it as the project specification. Otherwise, ask:

"What is the project specification? Describe the objective, requirements, constraints, and out-of-scope items."

Extract from the specification:

Objective (what the project builds)
Requirements (what it must do)
Constraints (what it must not do or must use)
Out of scope (what is explicitly excluded)

Step 3: Clarify

Analyze the specification for ambiguities. For each ambiguity:

Generate a clarify question with default answer
If autonomy level is full: accept defaults automatically
If autonomy level is supervised or guided: present question, wait for answer
Log all clarification decisions

Record decisions in the ---ci--- block of the init commit.

Step 4: Create .ci/ Files

Use CiFiles to create the project structure:

.ci/config.json — default CI configuration with autonomy level
.ci/PROJECT.md — vision, requirements, constraints, key decisions
.ci/ARCHITECTURE.md — system architecture (initial, may be incomplete)
.ci/ROADMAP.md — phase breakdown (to be refined by roadmapper)
.ci/REQUIREMENTS.md — formal requirements with REQ-IDs

Step 5: Create Initial Branches

git checkout -b milestone/v1.0-initial

Step 6: Initial Commit

docs(init): initialize [project-name] ([N] phases)

---ci---
phase: 0
milestone: v1.0
status: specify
decisions:
  - id: D-001
    decision: [clarification decision]
    rationale: [why]
    confidence: 0.XX
    alternatives: []
---/ci---

Specification: [objective]
Requirements: [req1, req2, ...]
Constraints: [constraint1, ...]
Out of scope: [item1, ...]

Step 7: Done

Report project initialized, .ci/ files created, initial branch created.

Next: ci-run to execute the pipeline, or ci-quick for ad-hoc tasks.

2.4 KiB Raw Blame History