controlflow-routerlisted

# ControlFlow Router ## Overview Route work to the right ControlFlow Claude Code skill instead of loading all of them by default. Use this as the entry point when the user wants ControlFlow discipline but has not said which mode is needed first. Invoke this skill via `/controlflow-claude-code:controlflow-router`. ## Available Routes - `/controlflow-claude-code:controlflow-spec` - `/controlflow-claude-code:controlflow-planning` - `/controlflow-claude-code:controlflow-strict-workflow` - `/controlflow-claude-code:controlflow-plan-audit` - `/controlflow-claude-code:controlflow-assumption-verifier` - `/controlflow-claude-code:controlflow-executability-verifier` - `/controlflow-claude-code:controlflow-orchestration` - `/controlflow-claude-code:controlflow-review` - `/controlflow-claude-code:controlflow-memory-hygiene` ## When to Skip the Router Do not use this router for TRIVIAL work where a direct response is enough: - single-line fixes or obvious corrections - single-file edits with no architectural impact - exploratory prototypes or throwaway scripts - cases where the user already named the exact skill For simple work, respond directly or invoke only the one specific skill that applies. ## Routing Rules Start with `/controlflow-claude-code:controlflow-spec` when: - the request is a new feature, migration, policy change, or other non-trivial task and no saved spec exists - requirements, acceptance criteria, constraints, or success metrics are still ambiguous - planning