Command Routing
Four agents share this routing table. Each owns a distinct domain — do not cross boundaries:
| Agent | Entry point | Domain |
|---|---|---|
| starscribe | starspec/starscribe.agent.md | Spec documents: domains, features, flows, stories, manifests, milestones, changesets, blueprints |
| stardesign | starspec/stardesign.agent.md | UI surface documents |
| starfix | starspec/starfix.agent.md | Convention enforcement: lint, sanitize, naming audits |
| starspec | starspec/starspec.agent.md | Compiler evolution: adding or modifying tags, processors, aggregate pages |
Fetch the relevant instruction path before doing any work. Never improvise a design loop step.
Starscribe commands
Starscribe command-to-instruction routing
CommandFetch (for mode overview); no separate loop — see scaffold mode in
Stardesign commands
UI authoring routes to the stardesign agent — do not handle these in starscribe:
Stardesign UI authoring command routing
CommandFetch
Starfix commands
Convention enforcement and fixing routes to the starfix agent — do not handle these in starscribe:
| Command | Fetch |
|---|---|
lint | starspec/agents/starfix/schema.lint |
sanitize | starspec/agents/starfix/model.sanitize |
audit naming | starspec/agents/conventions/naming-standards |
fix naming | starspec/agents/conventions/naming-standards |
Starspec commands
Compiler evolution routes to the starspec agent — do not handle these in starscribe or stardesign:
| Command | Fetch |
|---|---|
add tag <name> | starspec/extend-starspec then starspec/adding-a-tag |
modify tag <name> | starspec/tag/{name} then starspec/architecture |
add aggregate page <name> | starspec/architecture |
add instruction doc <path> | starspec/fragments |
Updating this table
When a new design loop is added to instructions/, add a row here. The agent entry points do not need updating — they reference this fragment via get_instructions("starspec/agents/common/command-routing").