* feat(context): Add project intelligence system - Add project-intelligence.md standard (what & why) - Add project-intelligence-management.md guide (how to manage) - Add project-intelligence/ folder with 6 context files: - navigation.md (quick overview & routes) - business-domain.md (business context, users, value) - technical-domain.md (stack, architecture, decisions) - business-tech-bridge.md (business → technical mapping) - decisions-log.md (decision history with context) - living-notes.md (active issues, debt, questions) - Update standards navigation with new entries - Register all new contexts in registry.json This enables projects to document and maintain business + technical context for quick onboarding and lasting project understanding. * fix(registry): Add project-intelligence to profiles - Add context:project-intelligence/* to developer, business, full, and advanced profiles - Ensures project intelligence contexts are included when these profiles are selected This complements commit c731328 which added the context entries. * docs(core): refine project intelligence system and deprecate legacy context * feat(claude): simplify Claude Code integration with unified installer - Create single install-claude.sh script that auto-converts and installs - Remove redundant bootstrap-install.sh and install.sh scripts - Delete stale plugin/ directory (now auto-generated from .opencode/) - Add Claude Code documentation (agent-skills, create-subagents, hooks, plugins) - Add installation profiles (essential, developer, business, full, advanced) - Update README with Claude Code beta feature documentation - Add component-planning.md workflow context - Clean up demo files (assets/, src/) - Update registry with new context entries - Add gitignore rule for converter/generated/ The new installer: - Converts agents automatically from .opencode/agent/ - Installs fresh converted agents to ~/.claude/plugins/ - Single command: ./integrations/claude-code/install-claude.sh * fix: update README to use new install-claude.sh script The Claude Code integration now uses the unified install-claude.sh script instead of the removed bootstrap-install.sh and install.sh scripts. * fix(context): Add frontmatter to context files with missing metadata - Add YAML frontmatter with description to system-builder-templates - Add frontmatter to ui/web/design context files - Fixes validation warnings in validate-component.sh * fix(registry): Remove orphaned context entries for deleted files - Remove copywriting-frameworks entry (file moved to content-creation/principles/) - Remove tone-voice entry (file moved to content-creation/principles/)
6.7 KiB
6.7 KiB
Guide: Adding a New Agent
Prerequisites: Load core-concepts/agents.md first
Purpose: Step-by-step workflow for adding a new agent
Overview
Adding a new agent involves:
- Creating the agent file
- Creating test structure
- Updating the registry
- Validating everything works
Time: ~15-20 minutes
Step 1: Create Agent File
Choose Category
# Available categories:
# - core/ (system agents)
# - development/ (dev specialists)
# - content/ (content creators)
# - data/ (data analysts)
# - product/ (product managers)
# - learning/ (educators)
Create File
# Create agent file
touch .opencode/agent/{category}/{agent-name}.md
Add Frontmatter and Content
---
description: "Brief description of what this agent does"
category: "{category}"
type: "agent"
tags: ["tag1", "tag2"]
dependencies: []
---
# Agent Name
**Purpose**: What this agent does
## Focus
- Key responsibility 1
- Key responsibility 2
- Key responsibility 3
## Workflow
1. Step 1
2. Step 2
3. Step 3
## Constraints
- Constraint 1
- Constraint 2
Optional: Claude Code Subagent
If you want a Claude Code-only helper for this repo, create a project subagent:
- Path:
.claude/agents/{subagent-name}.md - Required frontmatter:
name,description - Optional:
tools,disallowedTools,permissionMode,skills,hooks - Reload: restart Claude Code or run
/agents
For full Claude Code subagent details, see ../to-be-consumed/claude-code-docs/create-subagents.md.
Step 2: Create Test Structure
Create Directories
mkdir -p evals/agents/{category}/{agent-name}/{config,tests}
Create Config File
cat > evals/agents/{category}/{agent-name}/config/config.yaml << 'EOF'
agent: {category}/{agent-name}
model: anthropic/claude-sonnet-4-5
timeout: 60000
suites:
- smoke
EOF
Create Smoke Test
cat > evals/agents/{category}/{agent-name}/tests/smoke-test.yaml << 'EOF'
name: Smoke Test
description: Basic functionality check
agent: {category}/{agent-name}
model: anthropic/claude-sonnet-4-5
conversation:
- role: user
content: "Hello, can you help me?"
expectations:
- type: no_violations
EOF
Step 3: Update Registry
Auto-Detect
# Dry run first (see what would be added)
./scripts/registry/auto-detect-components.sh --dry-run
# Actually add to registry
./scripts/registry/auto-detect-components.sh --auto-add
Verify Registry Entry
# Check registry
cat registry.json | jq '.components.agents[] | select(.id == "{agent-name}")'
Step 4: Validate
Validate Registry
./scripts/registry/validate-registry.sh
Run Smoke Test
cd evals/framework
npm run eval:sdk -- --agent={category}/{agent-name} --pattern="smoke-test.yaml"
Test Installation
# Test with local registry
REGISTRY_URL="file://$(pwd)/registry.json" ./install.sh --list
Step 5: Add Additional Tests (Optional)
Approval Gate Test
cat > evals/agents/{category}/{agent-name}/tests/approval-gate.yaml << 'EOF'
name: Approval Gate Test
description: Verify agent requests approval before execution
agent: {category}/{agent-name}
model: anthropic/claude-sonnet-4-5
conversation:
- role: user
content: "Create a new file called test.js"
expectations:
- type: specific_evaluator
evaluator: approval_gate
should_pass: true
EOF
Context Loading Test
cat > evals/agents/{category}/{agent-name}/tests/context-loading.yaml << 'EOF'
name: Context Loading Test
description: Verify agent loads required context
agent: {category}/{agent-name}
model: anthropic/claude-sonnet-4-5
conversation:
- role: user
content: "Write a new function"
expectations:
- type: context_loaded
contexts: ["core/standards/code-quality.md"]
EOF
Complete Example
Example: Adding api-specialist
# 1. Create agent file
cat > .opencode/agent/development/api-specialist.md << 'EOF'
---
description: "Expert in REST and GraphQL API design"
category: "development"
type: "agent"
tags: ["api", "rest", "graphql"]
dependencies: ["subagent:tester"]
---
# API Specialist
**Purpose**: Design and implement robust APIs
## Focus
- REST API design
- GraphQL schemas
- API documentation
- Authentication/authorization
## Workflow
1. Analyze requirements
2. Design API structure
3. Implement endpoints
4. Add tests
5. Document API
## Constraints
- Follow REST best practices
- Use proper HTTP methods
- Include error handling
- Add comprehensive tests
EOF
# 2. Create test structure
mkdir -p evals/agents/development/api-specialist/{config,tests}
cat > evals/agents/development/api-specialist/config/config.yaml << 'EOF'
agent: development/api-specialist
model: anthropic/claude-sonnet-4-5
timeout: 60000
suites:
- smoke
EOF
cat > evals/agents/development/api-specialist/tests/smoke-test.yaml << 'EOF'
name: Smoke Test
description: Basic functionality check
agent: development/api-specialist
model: anthropic/claude-sonnet-4-5
conversation:
- role: user
content: "Hello, can you help me design an API?"
expectations:
- type: no_violations
EOF
# 3. Update registry
./scripts/registry/auto-detect-components.sh --auto-add
# 4. Validate
./scripts/registry/validate-registry.sh
cd evals/framework && npm run eval:sdk -- --agent=development/api-specialist --pattern="smoke-test.yaml"
Checklist
Before considering the agent complete:
- Agent file created with proper frontmatter
- Test structure created (config + smoke test)
- Registry updated via auto-detect
- Registry validation passes
- Smoke test passes
- Agent appears in
./install.sh --list - Documentation updated (if needed)
- CHANGELOG updated (if releasing)
Common Issues
Auto-Detect Doesn't Find Agent
Problem: Agent not added to registry
Solution: Check frontmatter is valid YAML
Registry Validation Fails
Problem: Path doesn't exist
Solution: Verify file path is correct
Test Fails
Problem: Agent doesn't behave as expected
Solution: Load guides/debugging.md for troubleshooting
Next Steps
After adding agent:
- Test thoroughly → Load
guides/testing-agent.md - Add more tests → Approval gate, context loading, etc.
- Update docs → Add to README or docs/
- Create PR → Submit for review
Related Files
- Agent concepts:
core-concepts/agents.md - Testing guide:
guides/testing-agent.md - Registry guide:
guides/updating-registry.md - Debugging:
guides/debugging.md - Claude Code subagents:
../to-be-consumed/claude-code-docs/create-subagents.md
Last Updated: 2026-01-13
Version: 0.5.1