genie

# Genie Route the request using the active runtime’s discovered skills. Preserve the user’s scope and existing authorization. ## Choose a route Inspect related `.genie/wishes/` and `.genie/brainstorms/` only as needed. Resume matching work before creating a new plan. An explicit skill request selects that skill; a mention of Genie is not necessarily an invocation. Ordinary unrelated requests bypass the lifecycle unless the user asks for Genie or the work needs durable planning, unresolved product/architecture decisions, coordinated workstreams, or tracking across sessions. Announce the bypass in one line and proceed without creating `.genie` artifacts or adding Genie gates. Repository validation and safety rules still apply. Use cheap read-only inspection when uncertain. Security-sensitive changes retain review gates unless the user explicitly chooses otherwise. Precedence when more than one row matches, highest first: an explicit skill request wins; then a resumable wish or design that already covers the request; then the route that carries the safety — investigate before planning, plan before executing, verify before declaring; then the narrower route over the broader one. Still tied after those four: take the heavier route and say so in one line. | Request | Route | Hands off to | Do not take this route when | |---|---|---|---| | Ambiguous idea needing decisions | `brainstorm` | `wish`, once the design is reviewed | The decisions are already settled; write the plan i...