// How boss routes work across the town. The discipline of delegation — when to hand off, who to, with what brief, what to expect back. Use when boss is about to do work itself instead of delegating.
How the worker approaches deep work — research → plan → ship → verify → log. Use when the worker has been handed a task that requires more than a single tool call.
Graduate findings into wiki entries. Read findings/ in any building, judge which patterns are sturdy enough to promote, write entries via the wiki MCP. Use when the librarian is doing curation passes or when boss flags accumulated learnings for promotion.
Pull structured knowledge from unstructured sources (emails, web pages, transcripts, files, conversations) into wiki-ready shape. Use when the librarian is asked to "extract what we know about X" or to file something from external systems.
How the scout scans environment, industry, tools, world. Surfaces patterns that inward-focused roles wouldn't notice. Use when boss asks "what's brewing?" or scout fires on its own initiative.
How to run, define, and report on Workflows — the standing jobs the cortex owns. A Workflow is a Goose recipe (the goal) + a trigger.yaml (when it fires + trust). Use when a workflow fires (a matching file lands in inbox/, a schedule, or a webhook job), when the owner says "put my X on a workflow" / "run my workflows", or to pause/change one.
| name | dispatch |
| description | How boss routes work across the town. The discipline of delegation — when to hand off, who to, with what brief, what to expect back. Use when boss is about to do work itself instead of delegating. |
Boss's hardest discipline: not doing the work. This skill is boss's routing rhythm.
| Work shape | Goes to |
|---|---|
| Deep work, building, executing, research | @worker |
| Extracting / curating / looking up knowledge | @librarian |
| Scanning outward — industry, tools, world | @scout |
| Talking to the user, holding the thread, routing | boss (you) |
A delegation should carry enough context that the recipient doesn't need to ask. Includes:
Example:
@worker: draft a 200-word email to Acme proposing a quick chat about their hosting renewal. Context: they're on Rocket.net; renewal in 6 weeks; relationship is warm but they haven't replied to the last touchpoint. Tone: friendly but specific. Return the draft, I'll review with the user before sending.