feat: Add installation tool, Claude.ai export, and skill standardization (#1)
## Summary - Add portable installation tool (`install.sh`) for cross-machine setup - Add Claude.ai export files with proper YAML frontmatter - Add multi-agent-guide v2.0 with consolidated framework template - Rename `00-claude-code-setting` → `00-our-settings-audit` (avoid reserved word) - Add YAML frontmatter to 25+ SKILL.md files for Claude Desktop compatibility ## Commits Included - `93f604a` feat: Add portable installation tool for cross-machine setup - `9b84104` feat: Add Claude.ai export for portable skill installation - `f7ab973` fix: Add YAML frontmatter to Claude.ai export files - `3fed49a` feat(multi-agent-guide): Add v2.0 with consolidated framework - `3be26ef` refactor: Rename settings-audit skill and add YAML frontmatter Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Andrew Yim
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "multi-agent-guide",
|
||||
"version": "1.0.0",
|
||||
"description": "Multi-agent collaboration framework for complex projects. Sets up agent hierarchies, ownership rules, guardrails, handoff protocols, and CI/CD integration for Claude, Gemini, Codex, and Human agents working together.",
|
||||
"version": "2.0.0",
|
||||
"description": "Multi-agent collaboration framework for complex projects. Sets up agent hierarchies, ownership rules, guardrails, handoff protocols, and CI/CD integration for Claude, Gemini, Codex, and Human agents working together. v2.0 includes consolidated MULTI_AGENT_FRAMEWORK.md template and quick-setup command.",
|
||||
"author": {
|
||||
"name": "OurDigital",
|
||||
"email": "ourdigital@example.com"
|
||||
@@ -12,7 +12,21 @@
|
||||
"guardrails",
|
||||
"ownership",
|
||||
"ci-cd",
|
||||
"project-management"
|
||||
"project-management",
|
||||
"framework",
|
||||
"claude",
|
||||
"gemini",
|
||||
"codex"
|
||||
],
|
||||
"license": "MIT"
|
||||
"license": "MIT",
|
||||
"commands": [
|
||||
{
|
||||
"name": "multi-agent-setup",
|
||||
"description": "Quick setup for multi-agent collaboration"
|
||||
},
|
||||
{
|
||||
"name": "setup-agents",
|
||||
"description": "Full interactive multi-agent setup"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -1,7 +1,13 @@
|
||||
# Multi-Agent Guide Plugin
|
||||
# Multi-Agent Guide Plugin v2.0
|
||||
|
||||
A Claude Code plugin for setting up multi-agent collaboration frameworks in complex software projects.
|
||||
|
||||
## What's New in v2.0
|
||||
|
||||
- **Consolidated Framework**: Single `MULTI_AGENT_FRAMEWORK.md` (~250 lines vs ~2,400)
|
||||
- **Quick Setup**: `/multi-agent-setup` command for rapid deployment
|
||||
- **Production-Tested**: Based on dintel-data-agent and our-seo-agent
|
||||
|
||||
## Overview
|
||||
|
||||
This plugin helps you establish a structured collaboration framework for projects where multiple AI agents (Claude Code, Gemini, Codex, and Human) work together. It provides:
|
||||
@@ -46,15 +52,19 @@ The skill activates automatically when you mention:
|
||||
- "multi-agent guide"
|
||||
- "agent coordination"
|
||||
|
||||
### Explicit Command
|
||||
### Explicit Commands
|
||||
|
||||
Use the slash command:
|
||||
**Quick Setup (Recommended):**
|
||||
```
|
||||
/multi-agent-setup
|
||||
```
|
||||
Rapid deployment with minimal questions. Creates consolidated framework.
|
||||
|
||||
**Full Setup:**
|
||||
```
|
||||
/setup-agents
|
||||
```
|
||||
|
||||
This will guide you through the complete setup process interactively.
|
||||
Interactive setup with full customization options.
|
||||
|
||||
## What Gets Created
|
||||
|
||||
|
||||
95
custom-skills/91-multi-agent-guide/commands/quick-setup.md
Normal file
95
custom-skills/91-multi-agent-guide/commands/quick-setup.md
Normal file
@@ -0,0 +1,95 @@
|
||||
---
|
||||
name: multi-agent-setup
|
||||
description: Quick setup for multi-agent collaboration using the consolidated framework
|
||||
---
|
||||
|
||||
# Quick Multi-Agent Setup
|
||||
|
||||
You are setting up multi-agent collaboration using the consolidated MULTI_AGENT_FRAMEWORK.md template.
|
||||
|
||||
## Your Task
|
||||
|
||||
Perform a rapid setup with minimal questions:
|
||||
|
||||
### Step 1: Quick Assessment
|
||||
|
||||
Check the project structure:
|
||||
```bash
|
||||
ls -la
|
||||
ls src/ 2>/dev/null || ls lib/ 2>/dev/null || echo "No src directory"
|
||||
```
|
||||
|
||||
### Step 2: Ask ONE Question
|
||||
|
||||
Use AskUserQuestion to ask:
|
||||
|
||||
```
|
||||
Which agents will participate in this project?
|
||||
- Claude + Gemini + Codex (Full team)
|
||||
- Claude + Codex (Dev focused)
|
||||
- Claude + Gemini (Research focused)
|
||||
- Claude only (Solo with guidelines)
|
||||
```
|
||||
|
||||
### Step 3: Create Files
|
||||
|
||||
Based on the answer, create these files:
|
||||
|
||||
**Always create:**
|
||||
```
|
||||
.agent-state/tasks.yaml
|
||||
.agent-state/locks.yaml
|
||||
MULTI_AGENT_FRAMEWORK.md ← Use template from skill
|
||||
tools/check-ownership.py
|
||||
```
|
||||
|
||||
**If Gemini included:**
|
||||
```
|
||||
GEMINI.md
|
||||
```
|
||||
|
||||
**If Codex included:**
|
||||
```
|
||||
CODEX.md
|
||||
```
|
||||
|
||||
### Step 4: Customize Framework
|
||||
|
||||
In MULTI_AGENT_FRAMEWORK.md:
|
||||
1. Replace `{{PROJECT_NAME}}` with actual project name
|
||||
2. Replace `{{DATE}}` with current date
|
||||
3. Adjust ownership matrix based on project structure
|
||||
|
||||
### Step 5: Summary
|
||||
|
||||
Output a concise summary:
|
||||
|
||||
```markdown
|
||||
## Multi-Agent Framework Installed
|
||||
|
||||
**Files Created:**
|
||||
- `.agent-state/tasks.yaml`
|
||||
- `.agent-state/locks.yaml`
|
||||
- `MULTI_AGENT_FRAMEWORK.md`
|
||||
- `tools/check-ownership.py`
|
||||
- [Additional agent files if created]
|
||||
|
||||
**Next Steps:**
|
||||
1. Set agent identity: `export AGENT_AUTHOR=claude`
|
||||
2. Review ownership matrix in `MULTI_AGENT_FRAMEWORK.md`
|
||||
3. Start using `[Agent] type(scope): message` commit format
|
||||
|
||||
**Commands:**
|
||||
- Check ownership: `python tools/check-ownership.py <file>`
|
||||
- View tasks: `cat .agent-state/tasks.yaml`
|
||||
- View locks: `cat .agent-state/locks.yaml`
|
||||
```
|
||||
|
||||
## Template Location
|
||||
|
||||
Use the consolidated framework template from:
|
||||
`${SKILL_DIR}/templates/multi-agent-framework.md`
|
||||
|
||||
## Key Principle
|
||||
|
||||
**Speed over completeness** - Get the framework running quickly. Users can customize later.
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
name: multi-agent-guide
|
||||
description: Use when user asks to "set up multi-agent collaboration", "initialize multi-agent project", "create agent guardrails", "set up team AI collaboration", "configure agent ownership rules", "create agent handoff protocols", mentions "multi-agent guide", "multi-agent setup", "agent coordination", "AI agent collaboration", or wants to configure a project for multiple AI agents (Claude, Gemini, Codex) working together with proper ownership rules, task management, and CI/CD integration.
|
||||
version: 1.0.0
|
||||
version: 2.0.0
|
||||
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion
|
||||
---
|
||||
|
||||
@@ -9,6 +9,24 @@ allowed-tools: Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion
|
||||
|
||||
This skill helps you set up a comprehensive multi-agent collaboration framework for complex software projects where multiple AI agents (Claude Code, Gemini, Codex, and Human) work together.
|
||||
|
||||
## What's New in v2.0
|
||||
|
||||
| Feature | Description |
|
||||
|---------|-------------|
|
||||
| **Consolidated Framework** | Single `MULTI_AGENT_FRAMEWORK.md` (~250 lines vs ~2,400 in separate files) |
|
||||
| **Quick Setup Command** | `/multi-agent-setup` for rapid deployment |
|
||||
| **Simplified Templates** | One unified template instead of 5 separate files |
|
||||
| **Production-Tested** | Based on dintel-data-agent and our-seo-agent implementations |
|
||||
|
||||
## Quick Start
|
||||
|
||||
For rapid setup, use:
|
||||
```
|
||||
/multi-agent-setup
|
||||
```
|
||||
|
||||
This creates the essential files in under 2 minutes.
|
||||
|
||||
## Overview
|
||||
|
||||
The multi-agent setup creates:
|
||||
@@ -371,8 +389,9 @@ Supporting files in this skill:
|
||||
|
||||
| File | Purpose |
|
||||
|------|---------|
|
||||
| `templates/agents-md.md` | AGENTS.md template |
|
||||
| `templates/guardrails-md.md` | GUARDRAILS.md template |
|
||||
| `templates/multi-agent-framework.md` | **Consolidated framework (RECOMMENDED)** |
|
||||
| `templates/agents-md.md` | AGENTS.md template (legacy) |
|
||||
| `templates/guardrails-md.md` | GUARDRAILS.md template (legacy) |
|
||||
| `templates/claude-md.md` | CLAUDE.md template |
|
||||
| `templates/gemini-md.md` | GEMINI.md template |
|
||||
| `templates/codex-md.md` | CODEX.md template |
|
||||
@@ -383,6 +402,15 @@ Supporting files in this skill:
|
||||
| `examples/minimal-setup/` | Minimal 2-agent setup example |
|
||||
| `examples/full-setup/` | Full 3-agent setup example |
|
||||
|
||||
### Template Selection Guide
|
||||
|
||||
| Use Case | Template |
|
||||
|----------|----------|
|
||||
| New projects | `multi-agent-framework.md` (consolidated) |
|
||||
| Existing projects with separate files | Keep existing AGENTS.md + GUARDRAILS.md |
|
||||
| Quick setup | `/multi-agent-setup` command |
|
||||
| Full customization | Individual templates (agents-md, guardrails-md, etc.) |
|
||||
|
||||
---
|
||||
|
||||
## Commands
|
||||
|
||||
@@ -0,0 +1,256 @@
|
||||
# Multi-Agent Development Framework
|
||||
|
||||
**Version:** 1.0
|
||||
**Applies to:** {{PROJECT_NAME}}
|
||||
**Last Updated:** {{DATE}}
|
||||
|
||||
---
|
||||
|
||||
## 1. Agent Hierarchy
|
||||
|
||||
```
|
||||
Human (Final Authority)
|
||||
│
|
||||
▼
|
||||
┌─────────────┐
|
||||
│ Claude Code │ ← Lead Agent
|
||||
│ Orchestrator│
|
||||
└──────┬──────┘
|
||||
│
|
||||
┌─────────────────┼─────────────────┐
|
||||
▼ ▼ ▼
|
||||
┌─────────┐ ┌─────────┐ ┌─────────┐
|
||||
│ Gemini │ │ Codex │ │ Human │
|
||||
│Research │ │ Speed │ │ Approve │
|
||||
└─────────┘ └─────────┘ └─────────┘
|
||||
```
|
||||
|
||||
| Agent | Role | Scope |
|
||||
|-------|------|-------|
|
||||
| **Claude** | Lead / Orchestrator | Architecture, core logic, integration, git, final review |
|
||||
| **Gemini** | Sub-agent | Google APIs, documentation, research, visualization |
|
||||
| **Codex** | Sub-agent | Tests, boilerplate, models, docstrings, utilities |
|
||||
| **Human** | Authority | Business decisions, priorities, release approval |
|
||||
|
||||
---
|
||||
|
||||
## 2. File Ownership
|
||||
|
||||
### 2.1 Standard Ownership Matrix
|
||||
|
||||
| Pattern | Owner | Examples |
|
||||
|---------|-------|----------|
|
||||
| `src/*/core/`, `src/*/services/` | Claude | Business logic, orchestration |
|
||||
| `src/*/api/`, `src/*/mcp/` | Claude | API clients, MCP servers |
|
||||
| `src/*/connectors/` | Claude | Data source integrations |
|
||||
| `src/*/visualization/`, `src/*/app/` | Gemini | Dashboards, charts |
|
||||
| `docs/*.md` | Gemini | User documentation |
|
||||
| `tests/` | Codex | All test files |
|
||||
| `src/*/utils/`, `src/*/models.py` | Codex | Utilities, Pydantic models |
|
||||
|
||||
### 2.2 Shared Files (Require Claude Approval)
|
||||
|
||||
| Files | Rule |
|
||||
|-------|------|
|
||||
| `pyproject.toml`, `requirements*.txt` | Claude approves dependency changes |
|
||||
| `.github/workflows/` | Claude approves CI/CD changes |
|
||||
| `CLAUDE.md`, `AGENTS.md`, `GUARDRAILS.md` | Claude only |
|
||||
| `PROJECT_PLAN.md` | Human approves roadmap changes |
|
||||
|
||||
### 2.3 Unrestricted Files
|
||||
|
||||
Any agent can modify: `.agent-state/*`, `.gitignore`, `README.md`
|
||||
|
||||
---
|
||||
|
||||
## 3. State Management
|
||||
|
||||
All state tracked in `.agent-state/` directory:
|
||||
|
||||
```
|
||||
.agent-state/
|
||||
├── tasks.yaml # Task registry
|
||||
└── locks.yaml # File locks
|
||||
```
|
||||
|
||||
### 3.1 Task Entry
|
||||
|
||||
```yaml
|
||||
tasks:
|
||||
- id: "TASK-001"
|
||||
agent: "codex"
|
||||
status: "in_progress" # pending | in_progress | completed | abandoned | blocked
|
||||
description: "Add unit tests for crawler"
|
||||
files: ["tests/test_crawler.py"]
|
||||
claimed_at: "{{DATE}}T10:00:00Z"
|
||||
expires_at: "{{DATE}}T22:00:00Z"
|
||||
```
|
||||
|
||||
### 3.2 Lock Entry
|
||||
|
||||
```yaml
|
||||
locks:
|
||||
- path: "src/crawler.py"
|
||||
agent: "claude"
|
||||
task_id: "TASK-001"
|
||||
lock_type: "exclusive" # exclusive | shared | override
|
||||
expires_at: "{{DATE}}T22:00:00Z"
|
||||
```
|
||||
|
||||
### 3.3 Expiration Rules
|
||||
|
||||
| Scenario | Duration |
|
||||
|----------|----------|
|
||||
| Standard task | 12 hours |
|
||||
| Complex refactoring | 24 hours |
|
||||
| Emergency fix | 4 hours |
|
||||
| Override (Claude) | 4 hours |
|
||||
|
||||
---
|
||||
|
||||
## 4. Workflow
|
||||
|
||||
### 4.1 Task Claiming
|
||||
|
||||
```bash
|
||||
# 1. Set identity
|
||||
export AGENT_AUTHOR=codex
|
||||
|
||||
# 2. Check state
|
||||
cat .agent-state/tasks.yaml
|
||||
cat .agent-state/locks.yaml
|
||||
|
||||
# 3. Claim task (add to tasks.yaml)
|
||||
git commit -m "[Codex] chore: claim TASK-001"
|
||||
|
||||
# 4. Do work, then commit
|
||||
git commit -m "[Codex] test(crawler): add unit tests"
|
||||
|
||||
# 5. Complete (update status, remove locks)
|
||||
git commit -m "[Codex] chore: complete TASK-001"
|
||||
```
|
||||
|
||||
### 4.2 Conflict Resolution
|
||||
|
||||
```
|
||||
1. Ownership Matrix → Owner has priority
|
||||
↓
|
||||
2. Active Locks → Lock holder has priority
|
||||
↓
|
||||
3. Task Assignment → Assigned agent has priority
|
||||
↓
|
||||
4. Escalate to Claude → Final decision
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 5. Handoff Protocols
|
||||
|
||||
### 5.1 Claude → Sub-agent
|
||||
|
||||
```markdown
|
||||
## Task for [Gemini/Codex]
|
||||
|
||||
**Type:** [API | Docs | Tests | Models]
|
||||
**Priority:** [High | Medium | Low]
|
||||
|
||||
### Objective
|
||||
[What needs to be done]
|
||||
|
||||
### Deliverables
|
||||
- [ ] Implementation
|
||||
- [ ] Tests (if applicable)
|
||||
- [ ] Documentation update
|
||||
```
|
||||
|
||||
### 5.2 Sub-agent → Claude (Escalation)
|
||||
|
||||
```markdown
|
||||
## Escalation to Claude
|
||||
|
||||
**Reason:** [Architecture | Integration | Security | Complexity]
|
||||
|
||||
### Completed
|
||||
[What was finished]
|
||||
|
||||
### Blocking Issue
|
||||
[What needs Claude's decision]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Commit Standards
|
||||
|
||||
### 6.1 Format
|
||||
|
||||
```
|
||||
[Agent] type(scope): description
|
||||
|
||||
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
||||
```
|
||||
|
||||
### 6.2 Types & Tags
|
||||
|
||||
| Type | Purpose | Agent Tags |
|
||||
|------|---------|------------|
|
||||
| `feat` | New feature | `[Claude]` |
|
||||
| `fix` | Bug fix | `[Gemini]` |
|
||||
| `docs` | Documentation | `[Codex]` |
|
||||
| `test` | Tests | `[Human]` |
|
||||
| `refactor` | Refactoring | `[CI]` |
|
||||
| `chore` | Maintenance | |
|
||||
|
||||
---
|
||||
|
||||
## 7. Quality Gates
|
||||
|
||||
### 7.1 Pre-merge Checklist
|
||||
|
||||
- [ ] Tests pass (`pytest`)
|
||||
- [ ] Code quality passes (`black`, `isort`, `flake8`, `mypy`)
|
||||
- [ ] Ownership check passes
|
||||
- [ ] No hardcoded secrets
|
||||
- [ ] Documentation updated
|
||||
- [ ] Agent attribution in commits
|
||||
|
||||
### 7.2 Coverage Targets
|
||||
|
||||
| Scope | Minimum | Target |
|
||||
|-------|---------|--------|
|
||||
| Overall | 70% | 80% |
|
||||
| Core modules | 80% | 90% |
|
||||
| New code | 80% | 100% |
|
||||
|
||||
---
|
||||
|
||||
## 8. Quick Reference
|
||||
|
||||
### Environment Setup
|
||||
|
||||
```bash
|
||||
export AGENT_AUTHOR=claude # claude | gemini | codex | human
|
||||
pip install -e ".[dev]"
|
||||
pre-commit install
|
||||
```
|
||||
|
||||
### Ownership Lookup
|
||||
|
||||
```
|
||||
Core logic, APIs, services → Claude
|
||||
Visualization, dashboards → Gemini
|
||||
Documentation → Gemini
|
||||
Tests, fixtures → Codex
|
||||
Utilities, models → Codex
|
||||
Dependencies, CI/CD → Shared (Claude approves)
|
||||
```
|
||||
|
||||
### Escalation Triggers
|
||||
|
||||
- Architectural decisions needed
|
||||
- Multi-file integration required
|
||||
- Security concerns
|
||||
- Performance optimization
|
||||
|
||||
---
|
||||
|
||||
*Generated by Multi-Agent Guide Skill v2.0*
|
||||
Reference in New Issue
Block a user