Files

T

CI cf5e7695fd feat(P03): multi-project support, NFR milestone versioning, phase context reset, install scripts

---ci---
phase: 3
milestone: v0.3.0
status: complete
decisions:
  - id: D-006
    decision: Multi-project via .ci/<slug>/ subdirectories and config.json registry
    rationale: Backward compatible migration from flat files; slug-based namespacing for branches and commits
    confidence: 0.92
    alternatives: [Git worktrees, Separate repos with subtrees]
  - id: D-007
    decision: NFR milestones use progressive patch versioning (no minor tag)
    rationale: NFR phases (fix/chore/docs/perf/refactor/test) don't represent feature delivery; patch increments reflect incremental improvement only
    confidence: 0.90
    alternatives: [Treat all milestones uniformly, Skip versioning for NFR]
  - id: D-008
    decision: Phase context reset via git checkpoint + fresh agent spawn
    rationale: Git-native architecture makes full state serialization safe; fresh context prevents accumulated conversation drift
    confidence: 0.88
    alternatives: [Context compaction, Sliding window summarization]
  - id: D-009
    decision: Install via both npm postinstall and standalone bash script
    rationale: Postinstall only fires on npm install -g; standalone script covers manual/cloned installs
    confidence: 0.95
    alternatives: [Postinstall only, Makefile target]
---/ci---

Source code:
- Added ProjectEntry, projects[], active_project to CIConfig
- Added project?: string to CiMetadata, CommitScope, all commit input types
- CiFiles: multi-project support (projectSlug, listProjects, addProject, migrateFlatToProject, isNfrMilestone)
- GitContext: projectSlug support, detectProjectFromCommit(), isNfrMilestone()
- GitBranch: project-prefixed branch naming via prefix()
- commit-builder/parser: project field in ---ci--- blocks
- config.ts: initCI() accepts projectSlug/projectName
- Implemented parseRoadmapMd phase parsing
- 284 tests passing (66 new tests)

Install scripts:
- scripts/install.sh: Standalone bash installer
- scripts/postinstall.js: npm postinstall (global installs only)

OpenCode integration:
- All 18 agents updated with multi-project project_context
- All 11 workflows updated with Step 0: Confirm Active Project
- All 5 references updated (branch-strategy, ci-files-discipline, commit-schema, decision-engine, git-context-loading)
- All 3 contexts updated (dev, research, review)
- VERSION bumped to 0.3.0

Package:
- Added files field, postinstall script, install script alias
- Version bumped to 0.3.0

2026-05-29 14:11:49 +00:00

3.2 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 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_project is correct for this initialization
If not, set it with ci setActiveProject(<slug>)
All subsequent operations use .ci/<slug>/ subdirectories
All commit messages must include project: <slug> in ---ci--- block

If single-project mode: proceed with existing conventions.

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 — registry with projects[] and active_project
.ci/<slug>/PROJECT.md — vision, requirements, constraints, key decisions (or .ci/PROJECT.md in single-project mode)
.ci/<slug>/ARCHITECTURE.md — system architecture (initial, may be incomplete)
.ci/<slug>/ROADMAP.md — phase breakdown (to be refined by roadmapper)
.ci/<slug>/REQUIREMENTS.md — formal requirements with REQ-IDs

initCI() accepts projectSlug and projectName parameters for multi-project initialization.

Step 5: Create Initial Branches

git checkout -b milestone/v1.0-initial

Step 6: Initial Commit

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

---ci---
project: <slug>
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, ...]

Include project: <slug> in the ---ci--- block when in multi-project mode.

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.

3.2 KiB Raw Blame History