git:20260813.25a2e80 to git:20260814.ef54249

# Claude Octopus Agents

This file describes the autonomous agents available in this repository for

AI coding tools that support agent discovery (e.g., GitHub Copilot coding agent).

## Available Agents

| Agent | Description | Tools |

|-------|-------------|-------|

| `backend-architect` | Scalable API design, microservices, distributed systems | Read-only |

| `code-reviewer` | Code quality, security vulnerabilities, production reliability | Read-only |

| `debugger` | Errors, test failures, unexpected behavior | All |

| `docs-architect` | Technical documentation from codebases | Read + execute |

| `frontend-developer` | React components, responsive layouts, client-side state | All |

| `performance-engineer` | Optimization, observability, scalable performance | Read-only |

| `security-auditor` | DevSecOps, OWASP compliance, vulnerability assessment | Read-only |

| `tdd-orchestrator` | Red-green-refactor discipline, test-driven development | All |

| `database-architect` | Data modeling, schema design, migration planning | Read-only |

| `cloud-architect` | AWS/Azure/GCP infrastructure, IaC, FinOps | Read + execute |

## Agent Definitions

Agents are defined in two formats for cross-platform compatibility:

- **Claude Code**: `.claude/agents/*.md` — YAML frontmatter with Claude Code tool names

- **GitHub Copilot**: `.github/agents/*.agent.md` — YAML frontmatter with Copilot tool aliases

Both formats describe the same 10 agents with platform-native tool mappings:

| Claude Code Tool | Copilot Alias |

|-----------------|---------------|

| Read | read |

| Write, Edit | edit |

| Bash | execute |

| Grep, Glob | search |

## MCP Integration

The MCP server (`mcp-server/`) exposes Claude Octopus workflows as MCP tools.

For MCP-aware coding agents, connect to the MCP server rather than invoking

agents directly.

## Repo Orientation for Agents

Mirror of the "Repo Orientation for Agents" section in `CLAUDE.md` (keep both in sync). Essentials:

- **Derived artifacts, never hand-edit**: `.claude-plugin/marketplace.json` (regen: `./scripts/sync-marketplace.sh`) and `openclaw/src/tools/index.ts` (regen: `./scripts/build-openclaw.sh`). `scripts/sync-readme.py` owns current facts across both READMEs and `PRODUCT.md`. Run `make sync` after component, metadata, release, model, or provider changes. During development use focused suites; before an ordinary branch push run `make ci-changed`, which fails closed to the full matrix for shared or unmapped changes. Run `make ci-local` before merge and release.

- **Exec bits**: scripts stay `100755`; `git diff origin/main...HEAD --summary | grep "mode change"` must be empty (CI-enforced; `allow-mode-change` label bypasses). Local test runs chmod test fixtures as a side effect — recheck modes after every local test run.

- **Provider wiring**: 7-point checklist across 5 files, documented in `docs/PROVIDERS.md`. Case globs are order-sensitive (`claude-sdk*` before `claude*`).

- **Releases**: follow `RELEASING.md`; tag the squash-merge commit on `main`, never the branch head.

- **Secret-scan quoting**: write `"SOME_API_KEY=${VAR}"`, not `SOME_API_KEY="${VAR}"`.

- **beads blocked?** If bd writes are blocked by pending schema migrations, do NOT migrate; record work in the session handoff and flag the blockage.

## Cross-Harness Continuity

`bd` is the task system of record. `AI_AGENT_HANDOFF.md` is the committed,

harness-neutral context packet for Claude Code, Codex, Copilot, OpenCode, and

other coding agents. It records the active branch, current decisions, evidence,

known blockers, and exact next action; it does not replace issue tracking.

At session start, read `RTK.md`, this file, `AI_AGENT_HANDOFF.md`, `git status`,

and the relevant `bd` issue before editing. For model-routing work, also read

`docs/MODEL-ROUTING-STRATEGY.md`. At session end, update the handoff with

verified test results, commit/push state, and remaining work.

Harness-local files such as `.octo-continue.md` may be generated or stale. Do

not treat them as the repository source of truth and do not overwrite an

untracked copy you did not create.

<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:7510c1e2 -->

## Beads Issue Tracker

This project uses **bd (beads)** for issue tracking. Run `bd prime` to see full workflow context and commands.

### Quick Reference

```bash

bd ready # Find available work

bd show <id> # View issue details

bd update <id> --claim # Claim work

bd close <id> # Complete work

```

### Rules

- Use `bd` for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists

- Run `bd prime` for detailed command reference and session close protocol

- Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files

**Architecture in one line:** issues live in a local Dolt DB; sync uses `refs/dolt/data` on your git remote; `.beads/issues.jsonl` is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md for details and anti-patterns.

## Session Completion

**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.

**MANDATORY WORKFLOW:**

1. **File issues for remaining work** - Create issues for anything that needs follow-up

2. **Run quality gates** (if code changed) - Tests, linters, builds

3. **Update issue status** - Close finished work, update in-progress items

4. **PUSH TO REMOTE** - This is MANDATORY:

```bash

git pull --rebase

git push

git status # MUST show "up to date with origin"

```

5. **Clean up** - Clear stashes, prune remote branches

6. **Verify** - All changes committed AND pushed

7. **Hand off** - Provide context for next session

**CRITICAL RULES:**

- Work is NOT complete until `git push` succeeds

- NEVER stop before pushing - that leaves work stranded locally

- NEVER say "ready to push when you are" - YOU must push

- If push fails, resolve and retry until it succeeds

<!-- END BEADS INTEGRATION -->