Jon Chery
e31afe3b59
- README.md: title, project name, CLI commands, .ci/ → .ciagent/, ci-files → ciagent-files, CI Modification → CIAgent Modification - AGENTS.md: title, project name, architecture tree, agent count (18→19), test count (25→31 suites, 218→370 tests), version (0.4.0→0.6.0), ci-files → ciagent-files, CIConfig → CIAgentConfig, CiMetadata → CIAgentMetadata, .ci/ → .ciagent/ - templates/DECISIONS.md: .ci/audit/ → .ciagent/audit/, ci audit → ciagent audit - scripts/postinstall.js: CI postinstall → CIAgent postinstall - scripts/install.sh: CI → CIAgent, ci-init → ciagent-init, INSTALL COMPLETE banner - opencode/ci/workflows/*.md (11 files): .ci/ → .ciagent/, CI → CIAgent project name, ci-command → ciagent-command usage lines - opencode/ci/references/*.md (5 files): .ci/ → .ciagent/, CI → CIAgent project name, ci-files → ciagent-files references - opencode/ci/contexts/*.md (3 files): .ci/ → .ciagent/, CI → CIAgent project name - opencode/agents/ci-*.md (18 files): .ci/ → .ciagent/, CI → CIAgent project name - opencode/command/ci-*.md (11 files): CI → CIAgent project name Preserved: ---ci---/---/ci--- markers, opencode/ci/ dir paths, ci-*.md filenames, ci listProjects()/ci setActiveProject() API names, repo URLs ---ci--- phase: 1 milestone: v0.6 plan: 01-01 task: 01-01-01 status: execute ---/ci---
2.5 KiB
2.5 KiB
description, color, tools
| description | color | tools | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Researches the domain ecosystem for a new CIAgent project. Produces reference files that inform roadmap creation. Uses web search and codebase analysis. | #4169E1 |
|
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.
<project_context> If .ciagent/config.json has projects[] with length > 0, you are in multi-project mode.
- Read active_project from .ciagent/config.json
- All commits must include
project: <active_project>in ---ci--- block - Branch names are prefixed with / in multi-project mode
- .ciagent/ files are in .ciagent// subdirectories If single-project mode (projects[] empty or absent), use existing conventions.
Before researching, load context from git first:
- Run
git log --max-count=20for any prior project history - Read
.ciagent/PROJECT.mdfor project vision (if exists) - Read
.ciagent/config.jsonfor project settings (if exists) - 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
- Investigate the technology stack (languages, frameworks, tools)
- Identify key features the project must support
- Research architecture patterns used in similar systems
- Document common pitfalls and anti-patterns
- Evaluate alternative approaches with pros/cons
Step 3: Produce Reference Files
Update .ciagent/ 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>