Menü
Finding, creating, claiming, and closing work items (beads)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Project conventions for writing, editing, restructuring, or reviewing the Gas City user documentation — the Mintlify site under docs/. Use this whenever you touch anything in docs/ (pages, tutorials, guides, reference, concept pages, diagrams, navigation) or write/edit prose about Gas City, even when the request is just "fix the docs", "write a docs page", "the docs are wrong/confusing", "rename X across the docs", or an edit to a file under docs/. It defines the canonical six-primitive model, required terminology (orchestrator not controller, platform not SDK, formulas v2 as the value), the prose / emphasis / diagram conventions, the information architecture, the rule that generated docs are edited at their source, and the gates to run before docs work is done.
Routing work to agents with gc sling and formulas
API server and web dashboard — config, start, monitor
Managing agents — list, peek, nudge, suspend, drain
City lifecycle — status, start, stop, init
Sending and reading messages between agents
| name | gc-work |
| description | Finding, creating, claiming, and closing work items (beads) |
Everything in Gas City is a bead — tasks, messages, molecules, convoys.
The gc bd CLI is the primary interface for bead CRUD.
Each rig has its own .beads/ database with its own ID prefix (e.g.
fe- for frontend, be- for beads). A bead must live in the
same database as the agent that will work on it. When you sling a bead
to a rig-scoped agent, sling operates on the agent's rig database — so
the bead must already exist there. The bead ID prefix tells you which
rig it belongs to.
Use gc rig list to see rig names, paths, and prefixes.
Use --rig to create beads in the right database. If the work will
be dispatched to a rig-scoped agent, create the bead in that agent's rig:
gc bd create "title" --rig frontend # Create in frontend's db (fe- prefix)
gc bd create "title" --rig beads # Create in beads db (be- prefix)
gc bd create "title" # Create in current directory's .beads/
gc bd create "title" -t bug # Create with type
gc bd create "title" --label priority=high # Create with labels
gc bd list # List beads in current .beads/
gc bd list --rig <rigname> # List beads in a specific rig
gc bd ready # List beads available for claiming
gc bd ready --label role:worker # Filter by label
gc bd show <id> # Show bead details
gc bd update <id> --claim # Claim a bead (sets assignee + in_progress)
gc bd update <id> --status in_progress # Update status
gc bd update <id> --label <key>=<value> # Add/update labels
gc bd update <id> --note "progress..." # Add a note
gc bd close <id> # Close a completed bead
gc bd close <id> --reason "done" # Close with reason
gc hook show <agent> # Show what's on an agent's hook
gc agent claim <agent> <id> # Put a bead on an agent's hook