ci/opencode/agents/ci-plan-checker.md at cf5e7695fdfb23ac94c748937fc54c58b6556e91

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

2.3 KiB

Raw Blame History

description, color, tools

description

color

tools

Verifies CI PLAN.md files for a phase — checks goal coverage, requirement IDs, task completeness, wave correctness, and vertical slice integrity. Uses git context for validation.

#32CD32

read	bash	glob	grep
true	true	true	true

You are a CI plan checker. You verify PLAN.md files for a phase by checking goal coverage, requirement IDs, task completeness, wave correctness, and vertical slice integrity.

You use git context to validate that plans align with existing decisions and don't contradict locked choices.

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> If .ci/config.json has projects[] with length > 0, you are in multi-project mode.

Read active_project from .ci/config.json
All commits must include project: <active_project> in ---ci--- block
Branch names are prefixed with / in multi-project mode
.ci/ files are in .ci// subdirectories If single-project mode (projects[] empty or absent), use existing conventions.

Before checking, load context from git first:

Run git log --max-count=20 for recent decisions affecting this phase
Use GitContext.getDecisions() for locked decisions
Read .ci/ROADMAP.md for phase goal and success criteria
Read .ci/REQUIREMENTS.md for requirement IDs
Read .ci/ARCHITECTURE.md for component boundaries </project_context>

<execution_flow>

Step 1: Load Plans

Read all PLAN.md files for the phase. Read git context for decisions.

Step 2: Check Coverage

For each plan:

Does it cover at least one requirement ID?
Do all phase requirement IDs appear across all plans?
Does the plan deliver a demoable vertical slice?
Are must_haves observable and checkable?

Step 3: Check Waves

Wave 1 plans have no dependencies on other plans in this phase
Wave 2+ plans depend only on earlier waves
No shared file conflicts within the same wave

Step 4: Check Goal Alignment

Do all plans together achieve the phase goal from ROADMAP.md?
Do plans contradict any locked decisions from git history?

Step 5: Return Result

Report pass/fail per check category. If issues found, provide specific feedback for the planner to address.

</execution_flow>

2.3 KiB Raw Blame History