route-work

Routes work kickoff requests to the correct starting workflow owner with a structured card.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jrgilbertson/the-rookery --skill route-work-jrgilbertson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: route-work
Source: https://github.com/jrgilbertson/the-rookery/tree/main/skills/route-work
Command: npx skills add https://github.com/jrgilbertson/the-rookery --skill route-work-jrgilbertson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When starting new work, it is often unclear which workflow should own the first step—brainstorming, planning, debugging, implementation, issue management, or design. This Skill removes that guesswork by assessing an explicit routing request against a fixed contract and returning exactly one routing decision. ## Core Features & Use Cases - Workflow routing: Chooses exactly one starting workflow owner (ce-brainstorm, grill-with-docs, ce-plan, ce-debug, ce-work, managing-issues, or impeccable) based on what needs to happen first. - Pattern and roster sizing: Recommends Single owner, Executor + Reviewer, or Coordinator + Executors patterns, with model and effort assignments per role. - Structured response cards: Renders one of three fixed templates—Route, Resume, or Questions—with a copy/paste kickoff the operator can hand to the coordinator session. - Use Case: You paste an issue and ask where to start. The Skill inspects only the supplied evidence, decides the first workflow, and returns a Route card naming the coordinator model, roster, and a ready-to-paste kickoff. ## Quick Start Ask the agent to route this work kickoff to its first workflow owner using the route-work skill.

Frequently Asked Questions about route-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which workflow should start a new piece of work?▼

Use route-work with an explicit routing request. It assesses what needs to happen first—clarifying scope, planning, debugging, implementing, managing issues, or designing—and returns a Route card naming exactly one starting workflow owner.

How to route work when an issue or plan already has an owner?▼

When a proven active owner exists for the requested phase, route-work returns a Resume card directing you to continue with that owner instead of issuing a duplicate kickoff. Proof requires an operator statement or supplied artifact naming the phase owner.

What evidence does the routing decision use?▼

Routing reads only the request, one explicitly named primary artifact, directly cited repository instructions, and already-supplied metadata. It does not perform broad repository searches, walk issue graphs, or probe external state.

When does route-work ask questions instead of routing?▼

It returns a Questions card when a request fits two owners, two independent workstreams could both start, a required artifact is unreadable, or the needed owner falls outside the seven supported workflows. Each question carries one concrete recommended answer.

What are the limitations of automated work routing?▼

Routing only activates on explicit routing or kickoff requests and never executes the work itself. It cannot route to owners outside its seven supported workflows and relies on supplied evidence rather than discovering repository state on its own.