first-officer

Solid

Use when running or resuming a Spacedock workflow, especially to discover a workflow, dispatch packaged workers, manage approval gates, and advance entity state.

AI & Automation 77 stars 8 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 81/100

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

Skill Content

If this skill is invoked directly in a non-interactive run and the prompt names a specific entity to process, enter single-entity mode immediately: - scope work to that entity only - follow the shared single-entity rules from the operating contract and any runtime-specific bounded-stop rules - keep running until the shared/runtime-specific stop condition for the requested bounded outcome is satisfied - do not treat an initial rejection as terminal when the workflow's feedback flow expects a routed follow-up - if the prompt only names the entity and does not explicitly request terminal completion, treat the runtime's bounded routed-reuse stop rule as sufficient - before the final response, explicitly shut down any worker that is no longer needed for later routing or gate handling - once the bounded stop condition is satisfied, send one concise final response and exit immediately ## How the first officer operates You are dispatcher, responsible for making sure the work is done by the crew. What awesome looks like: - Begin with the end; be clear about the value. - Do the hardest things first; de-risk while it is cheap. - Communicate and act concisely, choose the simplest approach, JFDI. ## Operating contract The skill loader supplies the absolute base directory for this `first-officer` skill when it opens this file. Retain that exact directory as `{first_officer_base}` for the session. A deferred first-officer core may only append the one literal `/references/...` suffix nam...

Details

Author
spacedock-dev
Repository
spacedock-dev/spacedock
Created
5 months ago
Last Updated
today
Language
Go
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

crew

Run a crew of agents on parallel tasks, each in its own git worktree, and hand back finished branches. Use when the user wants several independent tasks done at once, says "crew", "fleet", "dispatch", "run these in parallel", or asks for one agent to supervise others. Not for a single task, for work that has to happen in order, or outside a git repo.

0 Updated 1 months ago
muppio
AI & Automation Listed

dispatching-work

Internal machinery that starts, tracks, lists, and closes out the agents this plugin runs — one per dispatched task, each rooted in its resolved app's own directory. Use after `boss-say`'s execution-tier call has landed on dispatch, for any of its specialist skills (`shipping-task`, `inspecting-app`, `investigating-app`, `troubleshooting-app`), once `work-on` has resolved the target app(s) (or a plan). Not this skill's to front directly — a user's status question ("what's running", "wrap this up") goes through `boss-say`, which calls the List/Wrap-up branches below. Not for one dispatch's live content (`peeking-work`).

4 Updated today
wayne930242
AI & Automation Listed

boss-say

The single entry point for handing any work to straw-boss — implementation, audit, research, diagnosis, or anything else this session already has an available skill for. Use whenever the user hands work over or asks for something to be looked into — one item, a handful, or a whole backlog — e.g. "boss say <...>", "work on this", "implement X in <app>", "audit this module", "how does X work here", "X is failing", "work through this backlog". This skill judges the scale and, per item, the execution tier (a plain subagent, or a dispatched agent rooted in the app) and picks the dispatch shape (one item via a specialist skill or a better-fitting available skill, a capped batch in this turn, or a self-paced `/loop` batch).

4 Updated today
wayne930242