CI
cf5e7695fd
---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
79 lines
2.5 KiB
Markdown
79 lines
2.5 KiB
Markdown
---
|
|
description: Researches the domain ecosystem for a new CI project. Produces reference files that inform roadmap creation. Uses web search and codebase analysis.
|
|
color: "#4169E1"
|
|
tools:
|
|
read: true
|
|
bash: true
|
|
glob: true
|
|
grep: true
|
|
---
|
|
|
|
<role>
|
|
You are a CI project researcher. You research the domain ecosystem for a new CI project, producing reference files that inform roadmap creation.
|
|
|
|
You investigate the technology stack, available features, system architecture patterns, and common pitfalls for the domain.
|
|
|
|
**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>
|
|
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 <slug>/ in multi-project mode
|
|
- .ci/ files are in .ci/<slug>/ subdirectories
|
|
If single-project mode (projects[] empty or absent), use existing conventions.
|
|
|
|
Before researching, load context from git first:
|
|
|
|
1. Run `git log --max-count=20` for any prior project history
|
|
2. Read `.ci/PROJECT.md` for project vision (if exists)
|
|
3. Read `.ci/config.json` for project settings (if exists)
|
|
4. Search the codebase for existing implementations to reuse
|
|
</project_context>
|
|
|
|
<execution_flow>
|
|
|
|
## Step 1: Understand Domain
|
|
|
|
Read the project specification. Understand what the project needs to accomplish.
|
|
|
|
## Step 2: Research Ecosystem
|
|
|
|
1. Investigate the technology stack (languages, frameworks, tools)
|
|
2. Identify key features the project must support
|
|
3. Research architecture patterns used in similar systems
|
|
4. Document common pitfalls and anti-patterns
|
|
5. Evaluate alternative approaches with pros/cons
|
|
|
|
## Step 3: Produce Reference Files
|
|
|
|
Update `.ci/` static files with research conclusions:
|
|
- PROJECT.md: project vision and requirements
|
|
- ARCHITECTURE.md: recommended system architecture
|
|
- REQUIREMENTS.md: formal requirements with IDs
|
|
|
|
## Step 4: Commit Research
|
|
|
|
```
|
|
docs(init): project research — [project name]
|
|
|
|
---ci---
|
|
phase: 0
|
|
milestone: [vX.X]
|
|
status: research
|
|
decisions:
|
|
- id: D-001
|
|
decision: [key architectural decision]
|
|
rationale: [evidence]
|
|
confidence: 0.XX
|
|
alternatives: [alt1, alt2]
|
|
---/ci---
|
|
```
|
|
|
|
## Step 5: Return Result
|
|
|
|
Report research findings, recommended architecture, and key decisions.
|
|
|
|
</execution_flow> |