Multi-Agent Pipeline — OpenCode Configuration

Enterprise-grade, multi-agent AI pipeline for automated code discovery, implementation, testing, and verification across multiple repositories.

---

What This Is

This repo contains the .opencode/ pipeline infrastructure — skills, tools, agents, modes, and knowledge that power a multi-agent AI coding pipeline. Drop this into any workspace to get intelligent code automation.

User Input (vague or structured)
       │
       ▼
┌──────────────────────────────┐
│  1. Requirement Intake       │  Transforms vague → structured
└──────────┬───────────────────┘
           ▼
┌──────────────────────────────┐
│  2. Pattern Detection        │  Classifies → selects pipeline mode
└──────────┬───────────────────┘
           ▼
┌──────────────────────────────┐
│  3. Orchestrator Routing     │  Backend / Frontend / Both
└──────────┬───────────────────┘
           ▼
┌──────────────────────────────────────────────────────────────────┐
│                    PIPELINE EXECUTION                              │
│                                                                    │
│  full-feature: Discovery → Implementation → Testing → Verification│
│  quick-fix:    Implementation → Verification                      │
│  hotfix:       Discovery(lite) → Implementation → Verification    │
│  refactor:     Discovery → Implementation → Verification          │
└──────────────────────────────────────────────────────────────────┘
           │
           ▼
┌──────────────────────────────┐
│  Final Report + Lessons      │  Confidence scores + timing + PR
└──────────────────────────────┘

---

Structure

.opencode/
├── agents/                         # Agent definitions (6)
│   ├── main-orchestrator.md        #   Routes, gates, assembles
│   ├── discovery-agent.md          #   Read-only code analysis
│   ├── implementation-agent.md     #   Code modifications
│   ├── test-agent.md              #   Test creation
│   ├── verification-agent.md      #   Final review & PR prep
│   └── reviewer.md               #   Code review
├── skills/                         # Reusable skill modules (10)
│   ├── requirement-intake/        #   Vague → structured requirements
│   ├── pattern-detector/          #   Requirement classification
│   ├── pipeline-summary/          #   Progress visualization
│   ├── contract-validator/        #   Implementation compliance
│   ├── pr-description/            #   PR text generation
│   ├── test-scaffold/             #   Test boilerplate (~40% speedup)
│   ├── rollback/                  #   Safe change reversion
│   ├── lessons-learned/           #   Outcome recording
│   ├── ado-query/                 #   Azure DevOps queries
│   └── jenkins-build-status-report/ # CI/CD status
├── tools/                          # Shell tools (3)
│   ├── compile-check.sh           #   Verify compilation
│   ├── test-runner.sh             #   Run specific tests
│   └── diff-summarizer.sh         #   Structured diff output
├── modes/                          # Pipeline mode definitions (5)
│   ├── full-feature.md            #   Complete 4-stage pipeline
│   ├── quick-fix.md               #   Skip discovery + testing
│   ├── hotfix.md                  #   Lite discovery, skip new tests
│   ├── refactor.md                #   Skip testing, enhanced ref-check
│   └── analyze.md                 #   Read-only analysis mode
├── scripts/
│   └── notify-teams.sh            #   Teams webhook notifications
├── knowledge/                      # Institutional memory
│   ├── pipeline-history.json      #   All pipeline runs
│   ├── patterns/                  #   Discovered code patterns
│   ├── pitfalls/                  #   Common mistakes
│   └── metrics/                   #   Performance data
├── mcp-servers/
│   └── code-rag/                  #   Semantic code search (ChromaDB)
├── repos.yaml                      #   Target repository config
├── agent-report-templates.md       #   Report format standards
└── requirement-template.md         #   Requirement document template

---

Pipeline Modes

Mode	Stages	When to Use
full-feature	Discovery → Implementation → Testing → Verification	New features, complex changes
quick-fix	Implementation → Verification	Typos, labels, config values
hotfix	Discovery(lite) → Implementation → Verification	Critical production bugs
refactor	Discovery → Implementation → Verification	Structural changes, no behavior change

Modes automatically escalate when complexity exceeds expectations.

---

Agents

Agent	Role	Can Write?
Orchestrator	Routes, gates, assembles reports	Reports only
Discovery	Analyzes code, produces implementation contracts	❌
Implementation	Makes code changes per contract	✅
Test	Creates/updates tests	✅
Verification	Reviews changes, runs checks	❌
Reviewer	Code review feedback	❌

---

Skills

Skill	Purpose
requirement-intake	Transform vague input → structured requirement
pattern-detector	Classify requirement → select pipeline mode
pipeline-summary	Generate progress visualization at gates
contract-validator	Validate implementation matches discovery contract
pr-description	Generate polished PR descriptions
test-scaffold	Pre-generate test boilerplate
rollback	Safely revert pipeline changes
lessons-learned	Record outcomes for future improvement
ado-query	Natural language Azure DevOps queries
jenkins-build-status	CI/CD build status and failure analysis

---

Tools

Tool	Usage
compile-check.sh	.opencode/tools/compile-check.sh <path> <stack>
test-runner.sh	.opencode/tools/test-runner.sh <path> <stack> <target>
diff-summarizer.sh	.opencode/tools/diff-summarizer.sh <path> [base_ref]

---

MCP Server: code-rag

Locally-running semantic code search using ChromaDB vector embeddings.

Tool	Description
search_code	Natural language code search
find_related	Find semantically related files
get_context	Expand context around results
index_stats	View indexing statistics

100% local — code never leaves your machine. See .opencode/mcp-servers/code-rag/README.md for setup.

---

Setup

1. Copy .opencode/ into your workspace

git clone https://github.com/kkuppula/my-opencode-projects.git
cp -r my-opencode-projects/.opencode /path/to/your/workspace/

2. Configure target repositories

Edit .opencode/repos.yaml:

repos:
  backend:
    name: MyBackend
    path: /path/to/your/backend
    stack: Java/Gradle
    patterns:
      - "API", "service", "controller", "repository"
  frontend:
    name: MyFrontend
    path: /path/to/your/frontend
    stack: TypeScript/Angular
    patterns:
      - "UI", "component", "page", "view"

3. Set up code-rag (optional)

cd .opencode/mcp-servers/code-rag
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
# Edit config.yaml with your repo paths
./run-indexer.sh

4. Configure Teams notifications (optional)

export TEAMS_WEBHOOK_URL="https://your-org.webhook.office.com/..."

---

Key Features

• Intelligent mode selection — auto-picks the right pipeline depth
• Multi-repo orchestration — coordinates backend + frontend changes
• Confidence scoring — every agent reports 0-100% with rationale
• Human-in-the-loop gates — approval checkpoints between stages
• Institutional learning — records patterns and pitfalls for future runs
• Contract validation — ensures implementation matches discovery
• Safe rollback — reverts changes cleanly on failure
• Teams notifications — posts progress to Microsoft Teams

---

License

Private — Internal use only.