handoff-inbox-drain

Solid

Use when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.

AI & Automation 72 stars 7 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# handoff-inbox-drain Drain a handoff review inbox with judgment, without owning a scheduler. Brigade stays invoke-only; this skill is the allowlist-bound agent recipe for triage. ## When this applies - A handoff draft inbox has pending or reviewed items to triage. - An operator schedules a headless harness (`claude -p`, `codex exec`, or equivalent) against this skill. - You are reinforcing existing memory, not inventing a parallel corpus. ## Allowlist Work only through this allowlist of Brigade surfaces and local reads: - `brigade handoff list` - `brigade handoff show <id>` - `brigade handoff archive <id>` - `brigade handoff closeout` (when the workspace supports it) - `brigade handoff lint` / `brigade handoff doctor` for health checks - Read/Grep of on-disk handoff files, `memory/cards/`, and related indexes already present in the target Bash is scoped to those `brigade handoff …` commands only. Do not expand into arbitrary filesystem writes, remote APIs, unscoped shell, or tools outside this allowlist. Stay inside the handoff inbox / `memory/cards/` roots; do not follow `..` or symlinks out of those trees. ## Grounded-edit rules Every edit must be grounded. You must cite existing on-disk content (handoff body, card text, or index entry) before changing anything. Prefer reinforce-in-place: edit or refresh only what you can verify against a local source of truth. Date-bumps alone are not grounded edits. ## Retention (never delete) - Never delete handoff drafts or ...

Details

Author
escoffier-labs
Repository
escoffier-labs/brigade
Created
4 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

brigade-handoffs

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.

4 Updated yesterday
escoffier-labs
AI & Automation Featured

handoff

Produces and refreshes `.docs/handoff.md`, a 200-line session-continuity runbook for coding agents. Captures git state, working-tree changes, last validation commands, session decisions, blockers, resume checklist, references, and greenfield scaffolds. Triggers on: "update handoff", "session handoff", "refresh handoff", "/handoff", "/handoff init", "resume checklist", "cold-start primer". Use this skill when ending, pausing, resuming, or transferring in-flight project work across agent sessions.

325 Updated 5 days ago
Mathews-Tom
AI & Automation Listed

handoff

Coordinate progressive repository work across agents with a shared HANDOFF.md ledger. Use in repositories with a ledger, or on explicit handoff requests: /handoff:init, 'initialise the handoff', /handoff:continue, /handoff:status, /handoff:view, /handoff:purge, or 'use handoff'. After activation: handoff_guard.py name --root <repo> claims the session name; handoff_guard.py read --root <repo> returns ledger text and version in one snapshot. Audit later entries and code before treating unchecked boxes as unfinished. For ledger writes: handoff_guard.py apply --root <repo> --expect-version V with --entry FILE or --content FILE. On exit 3, re-read and re-audit; never retry the stale write. A user viewer assignment is required queued work: finish your current task, then audit and complete it without another prompt. Track investigations before research, even without code edits; a name claim is not a task.

1 Updated 1 weeks ago
divijshrivastava