菜单
Use when setting up, checking, writing, linting, or troubleshooting Brigade memory handoffs for a repo or agent workspace, especially when a user wants durable agent memory, handoff inboxes, cross-harness memory routing, or a safe first Brigade setup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the current session needs an answer or a work product from a model on ANOTHER vendor's stack - a second opinion from a different model family, a cheap fast model for bulk work, or a cross-model review - by dispatching that vendor's own CLI as a one-shot worker. Triggers include "ask grok/composer/gemini/claude/codex what it thinks", "get a second opinion from a different model", "cross-model review", "run this by another model", "poll several models". No orchestration framework required; if a Brigade roster exists, prefer `brigade run --worker` instead.
Use when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
Use when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
Use before implementing, scaffolding, prototyping, or adding a feature when the work should start with the smallest useful code path, avoid speculative architecture, or prevent overbuilding before reduce would be needed.
Use when the user wants to act on an audit, fix the findings in a line-check/bug-hunt/security-sweep report, work a prioritized backlog, or asks to "fix the findings", "work the backlog", "clear the audit", or "do the high-leverage items". The step after the audit trio.
Use when a written implementation plan is ready to execute, when the user says "fire", "execute the plan", "build it", or hands over a plan file to implement. The step after recipe.
| name | brigade-handoffs |
| license | MIT |
| description | Use when setting up, checking, writing, linting, or troubleshooting Brigade memory handoffs for a repo or agent workspace, especially when a user wants durable agent memory, handoff inboxes, cross-harness memory routing, or a safe first Brigade setup. |
Use Brigade to make agent handoffs boring: local drafts, linted routes, and a clear review queue before anything becomes durable memory.
MEMORY.md.For a code repo:
pipx install brigade-cli
brigade --version
brigade operator quickstart --target . --harnesses codex --dry-run
brigade operator quickstart --target . --harnesses codex
brigade operator doctor --target . --profile local-operator
brigade handoff doctor --target .
For an OpenClaw or Hermes workspace:
pipx install brigade-cli
brigade --version
brigade operator quickstart --target . --depth workspace --harnesses openclaw,hermes --owner openclaw --dry-run
brigade operator quickstart --target . --depth workspace --harnesses openclaw,hermes --owner openclaw
brigade operator doctor --target . --profile local-operator
brigade handoff doctor --target .
If the user uses multiple coding harnesses, choose the ones that exist in the target:
brigade operator quickstart --target . --harnesses codex,claude,opencode,antigravity,pi,cursor,aider,goose,continue,copilot,qwen,kimi,adal,openhands,grok,amp,crush --dry-run
Run without --dry-run only after checking the planned files.
Before setup, inspect the target for existing conventions:
find . -maxdepth 2 \( -name AGENTS.md -o -name CLAUDE.md -o -name MEMORY.md -o -name TOOLS.md -o -name SAFETY_RULES.md -o -name .brigade -o -name .codex -o -name .claude -o -name .openclaw -o -name .hermes \) -print
If existing memory or harness files are present, adapt Brigade around them. Do not replace working conventions with the example layout.
Use a short no-card handoff for most lessons:
brigade handoff draft --target . --inbox codex \
--type workflow \
--title "Short durable title" \
--summary "One sentence summary." \
--content "### Short durable title
What changed, what command worked, and what the next agent should do differently."
Use a card handoff only when the topic deserves a standalone memory card:
brigade handoff draft --target . --inbox codex \
--type gotcha \
--action create-card \
--target-card "memory/cards/example-gotcha.md" \
--title "Example gotcha" \
--summary "One sentence summary." \
--content-file /tmp/reviewed-card-content.md
Then lint before the memory owner ingests anything:
brigade handoff lint --target .
brigade handoff lint --target . --content-guard --guard-policy personal
brigade handoff doctor --target .
Use these commands to review pending drafts:
brigade handoff list
brigade handoff show <handoff-id-or-path>
brigade handoff archive <handoff-id-or-path>
brigade handoff archive --all-reviewed
Do not archive invalid handoffs just to make a queue look clean. Repair the draft or leave it pending for the memory owner.
If setup or lint fails, collect machine-readable output and summarize it after redaction:
brigade --version
brigade operator quickstart --target . --harnesses codex --json
brigade operator doctor --target . --profile local-operator --json
brigade operator verify-harness --target . --harness codex --json
brigade handoff doctor --target . --json
brigade handoff lint --target . --json
brigade tools doctor --target . --json
brigade skills doctor --target . --json
For OpenClaw/Hermes workspaces, use the workspace-depth quickstart command in the setup section.
When finished, report:
Healthy setup looks like:
quickstart: ok
operator doctor: ready yes
blocking issues: 0
handoff doctor: ok or warnings explained