Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From Captain's Cabinet
After an officer finishes a mission task, record the completion (or failure or verification) to the event ledger so the work graph advances and the next ready task surfaces to the next session.
npx claudepluginhub nate-step/captains-cabinet --plugin captains-cabinetHow this skill is triggered — by the user, by Claude, or both
Slash command
/captains-cabinet:cabinet-work-graph-completeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Invoke this skill whenever an officer has just finished work that corresponds to a mission work-graph node. Trigger phrases:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Invoke this skill whenever an officer has just finished work that corresponds to a mission work-graph node. Trigger phrases:
--status verified).Use the existing convergence script:
bash cabinet/scripts/work-graph-complete.sh <node_id> --status done --evidence <file_or_inline_text>
Where:
<node_id> matches the format <outcome_id>-task-NNN from the mission compiler. Find it in the session-task-inject context or via python3 -m framework.missions.supervisor --json --dry-run.--status is one of done (default), failed, or verified.--evidence is either a path to an evidence file (e.g., test output, deploy log) or inline text describing what was accomplished.The script emits the appropriate event (work_item_completed, work_item_failed, or work_item_verified) into the org ledger, which the compiler will overlay onto the work graph at the next session start so completed tasks don't re-inject.
After shipping the auth endpoint:
bash cabinet/scripts/work-graph-complete.sh \
outcome-launch-mvp-task-002 \
--status done \
--evidence /tmp/deploy-output.log
Returns the emitted event UUID on stdout. Status message on stderr.
mission_steps or work_graph_nodes rows — the event ledger is the source of truth.--status verified on your own work — validators verify, executors complete.