Skill Router

Quick Reference

HARD-GATE

Non-negotiable: no implementation code until a test exists, runs, and fails for the right reason (feature missing, not config/syntax).
ALWAYS identify the matching skill and name it explicitly as the next skill to use before responding further.

Core Process

Triages and decomposes any Ruby on Rails request into ordered sub-tasks, then delegates to the correct specialized skill. Enforces the Tests Gate Implementation mandate across all code-producing work.

When a task arrives, identify the matching skill from the tables below and name it explicitly as the next skill to use before responding further. In an active response, make the routing statement, such as Next skill: skills/context/load-context, the first substantive line before analysis or implementation. When multiple skills may apply, immediately follow the routing line with one concise priority/chain statement, such as Priority: security-check > review-migration; Chain: security-check then review-migration, before any analysis or implementation. For reference artifacts, show at least one concrete active-response example using this routing-first, priority/chain-second ordering.

Core Skills (Most Common)

Skill Priority

When multiple skills could apply, state this priority rule immediately after the routing statement:

Priority: TDD → Planning → Domain discovery → Process/refactor → Domain implementation.

Use plan-tests when the first failing spec is not obvious.

Key disambiguation signals:

• review-architecture vs code-review: use architecture-review when the question is about system shape, service boundaries, or design patterns; use code-review when the subject is a concrete PR, file, or changeset.
• plan-tests vs write-tests: use tdd-slices when the challenge is which test to write first; use write-tests when the challenge is how to write or improve a test.
• load-context before any other code-producing skill in an unfamiliar or existing codebase.

Fallback for ambiguous requests: If no clear skill match, label this explicitly as Fallback: load-context, load codebase context, then re-evaluate based on findings.

Multi-Concern PR Review Chains

When a request names several changed areas, do not route only to code-review. Decompose the changeset and name the ordered chain:

Start with load-context for an existing PR or unfamiliar codebase, then run the specialized review skills in risk order: security/data-loss first, migrations second, architecture/engine boundaries third, general code review last.

Typical Workflows

Sub-skills are invoked by stating their name as the next skill to apply, e.g. "Next skill: skills/workflows/tdd-workflow", before proceeding with that skill's instructions.

TDD Feature Loop (primary daily workflow) — use skills/workflows/tdd-workflow: skills/context/load-context → [CHECK: context loaded] → skills/workflows/tdd-workflow → PR

Feature (standard): skills/context/load-context → [CHECK: context loaded] → skills/planning/create-prd → [CHECK: PRD approved] → skills/planning/generate-tasks → [CHECK: tasks complete] → skills/workflows/tdd-workflow

Bug fix: skills/testing/triage-bug → [GATE: reproduction spec fails] → skills/workflows/tdd-workflow → fix → verify passes

Multi-concern PR review: skills/context/load-context → skills/code-quality/security-check (if auth/input/secrets touched) → skills/infrastructure/review-migration (if schema touched) → skills/engines/review-engine (if engine touched) → skills/code-quality/review-architecture (if boundaries touched) → skills/code-quality/code-review

Extended Resources

• assets/examples.md — 20+ routing examples covering ambiguous requests, multi-concern PRs, DDD-first features, engines, and edge cases
• assets/workflows.md — Extended workflow definitions for DDD-first, code review, engines, refactoring, and GraphQL
• docs/reference/skill-catalog.md — Complete skill catalog with trigger words, descriptions, and stage-based navigation

Output Style

1. Routing statement: Clearly state the next skill being invoked as the first substantive line of the response.

   Next skill: skills/context/load-context
   
   This is a feature request with unclear scope. I'll start by loading the codebase context, then create a PRD.

   Put this routing statement before any deeper analysis. If multiple skills apply, immediately follow it with one concise priority/chain statement before analysis or implementation:

   Next skill: skills/context/load-context
   Priority: security-check > review-migration > code-review; Chain: load-context then security-check, review-migration, code-review.
   
   This PR spans authorization, schema changes, and general Rails behavior, so I will load context first and then review in risk order.

2. Language: Generated artifacts (YARD docs, Postman collections, READMEs) and output MUST be in English unless explicitly requested otherwise.

Integration