Bearings
Generate a "pick up where I left off" fleet digest.
Install
npx skills add kunchenguid/firstmate --skill bearings -g -a claude-code -y- Repository
- kunchenguid/firstmate8.5k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Generate a "pick up where I left off" fleet digest. Use when the captain invokes /bearings (plain, file, or lavish) or asks for a bearings report, morning brief, status report, catch-up, "where did I leave off", or "what's in the works". Also use on a contributions check wake, when filing work linked to an upstream issue, and on a procevent lavish wake whose source id is the bearings board's.
bearings
Generate a complete current snapshot from the fleet's current state, so the captain can resume in one read after a break, a night, or a context reset.
Plain /bearings returns only the concise four-section chat digest.
Only /bearings file writes the dated markdown report artifact and then returns the concise four-section chat digest linked to that report.
Only /bearings lavish builds the interactive fleet board beside that digest, through bin/fm-bearings-board.sh (its header owns every board mechanic and the fm-bearings-board.v1 payload contract).
A digest/build invocation is operationally read-only apart from observational remote-ledger cache refreshes, durable per-target reconcile-notify requests when the captured state needs them, plus the explicit per-mode artifacts: the dated report in file mode, and in lavish mode the board file plus the answer binding and source registration that bin/fm-bearings-board.sh build records through their own owners.
During that invocation it never tears down a task, merges a PR, dispatches new work, steers a worker, answers a decision, cleans up work, or mutates backlog or task state.
Board answers are acted on later under the normal authority rules; this skill's board-wake section explicitly owns the guarded routing at that time.
