feat(skills): formalize agent coordination via beadboard-driver

We moved from ad-hoc task claims to a strictly defined 'Skill' system.

Triumphs:
- Implemented the 'beadboard-driver' skill, which encodes our project-specific coordination protocols (claim, reservation, handoff).
- This ensures that any AI operative (or human supervisor) can participate in the project lifecycle using a unified CLI-driven state machine.
- Decoupled high-level mission logic from low-level file mutations, allowing for easier agent skill composition in the future.

Raw Honest Moment:
Initially, we were just 'winging it' with manual status updates. Formalizing this into a skill was a necessary step to ensure our collaboration is repeatable and resilient to agent context swaps.
This commit is contained in:
zenchantlive 2026-02-14 00:23:41 -08:00
parent c7c3a25457
commit 1ae7efb31b
14 changed files with 848 additions and 0 deletions

View file

@ -0,0 +1,4 @@
interface:
display_name: "Beadboard Driver"
short_description: "Safe bd+bb agent workflow orchestration"
default_prompt: "Use Beadboard Driver to resolve bb path, register a unique session agent, coordinate via bb agent commands, and produce verification-backed closeout notes."