brigade-work

What problem does it solve?

When Brigade is installed but never used, it remains dormant: the daily brief stays empty, the outcome ledger never fills, and outcome rankings show no data because all work, verifications, and handoffs happen outside the Brigade workflow, leaving no audit trail or captured learning for the team.

Core Features & Use Cases

• Session Start Guidance: Pulls pending work, imports, and warnings from Brigade's daily brief to help users prioritize tasks at the start of every work session.
• Verified Work Routing: Requires all test and check runs to execute through Brigade's verify command, generating signed receipts with real exit codes instead of running tests raw with no audit trail.
• Outcome Capture: Instructs users to record pass/fail results against the relevant skill or memory card that performed the work, feeding the learning ratchet to automatically rank proven skills and roll back broken ones.
• Mandatory Handoffs: Requires end-of-session knowledge handoffs to preserve durable learnings across team members.
• Use Case: A developer working in a Brigade-wired repository uses this skill to ensure every pytest run, code change verification, and session handoff is captured, so the team can automatically promote reliable coding skills and deprecate ones that cause failures.

Quick Start

Use the brigade-work skill to route your next work verification through Brigade and capture the outcome against the skill or card that performed the work.