Menu
Use when a bound oasis7 task needs the next repo-owned workflow phase selected.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when any oasis7 user request starts and must bind the canonical worktree, GitHub-backed task truth, and owner before routing.
Use when a branch is about to create a PR and needs fresh involved-role review.
Use when implementation is verified and the branch must proceed through review, PR, merge, and cleanup.
Use when a task has written repo truth and implementation should proceed step by step with evidence.
Use when about to claim a task is complete, tests passed, a branch is ready for PR, or a PR is ready to merge. Requires fresh verification, direct output inspection, and use of `./scripts/pm/claim-ready.sh` when the claim can be mapped to one verification command.
Use when assessing or developing the blocked production-supervisor target for a bound oasis7 task spanning multiple lifecycle phases.
| name | repo-owned-workflow-router |
| description | Use when a bound oasis7 task needs the next repo-owned workflow phase selected. |
Canonical authority and lifecycle: capability, ownership, state machine, states, gates.
The production supervisor is a target runtime executor and is currently capability_blocked; TPM remains coordinator/integrator.
Use after bootstrap has bound canonical task truth and the next workflow phase is not yet selected.
Read-only/chat-only requests enter this router after default-workflow-bootstrap has established task truth.
executing-project-tasks.bounded-brainstorming; do not route there when implementation-ready.tdd-test-writer before execution.systematic-debugging before speculative fixes.receiving-code-review.finishing-a-development-branch.Do not treat specialist domain skills as mandatory default workflow phases. Select them only when their trigger matches.
inherit current parent selection by default; record observed runtime or adapter inactive on this surfaceRecord the slice contract in the GitHub issue evidence comment sink before dispatch. Unbound read-only professional questions are invalid under the always-bootstrap workflow; read-only professional/domain judgments must already be task-bound.
Do not dispatch implementation, verification, review, or specialist subagents without AGENTS.md, the assigned role card, workflow source-of-truth, current GitHub-backed task truth, and scoped repo context recorded in the mandatory context checklist.
Do not route around canonical task truth or invent a specialist phase.
Routing before bootstrap; mandatory brainstorming; speculative fixing before debugging; incomplete slice contracts.