request-dispatcher

---

name: request-dispatcher description: Used when the user's request is ambiguous and doesn't clearly match a single Skill's trigger criteria. Analyzes intent + project state to route to the correct Skill. Not a replacement for CLAUDE.md Skill Dispatch rules — only for edge cases where dispatch is uncertain. version: 1.0.0 updated: 2026-05-26 requires: []

[Task] Analyze ambiguous user requests and route them to the correct ReqForge Skill. When the main Agent's static dispatch rules (from CLAUDE.md [Skill Dispatch]) cannot uniquely determine the target Skill, this Skill provides a structured decision framework: classify intent → cross-reference project state → disambiguate → recommend Skill.

[Not For] - Clear-cut requests that match a single Skill trigger -> use the target Skill directly - Writing code -> use /dev-builder instead - Bug fixing -> use /bug-fixer instead - Requirements gathering -> use /product-spec-builder instead

[Dependency Check] Required: - User's natural language request -> the ambiguous message text - Project state awareness -> which artifacts exist (Product-Spec.md, DEV-PLAN.md, code, active changes/)

Optional:
- git log -> recent changes for context
- memory/ files -> known pitfalls and recent task history

[First Principles] → references/first-principles.md 核心：Minimum Dispatch / State Before Intent / Ask Don't Guess。

[Output Style] → references/output-style.md Tone: neutral, analytical, decisive. One recommendation, not a menu.

[File Structure] request-dispatcher/ ├── SKILL.md └── references/ ├── first-principles.md ├── output-style.md ├── workflow.md ├── dimension-checklist.md └── anti-rationalization.md

[Output Artifacts] - Dispatch recommendation (screen output) — one-line Skill name + one-sentence justification

[Dispatch Dimension Checklist] Before recommending a Skill, verify:

| Dimension | Must-Have | Recommended |
|-----------|-----------|-------------|
| **Intent Match** | User's message maps to a Skill's trigger description in CLAUDE.md | User's message is NOT already covered by a static rule (would be unnecessary dispatch) |
| **Prerequisite Check** | Target Skill's Dependency Check would pass | Target Skill's Not For section doesn't exclude the request |
| **Project State** | Required artifacts exist for the target Skill | No active changes/ folder conflict |
| **Ambiguity Resolved** | Recommendation resolves the ambiguity | User would not be surprised by the routing |

[Dispatch Decision Strategy]

| User says... | Product-Spec.md exists? | Active changes/? | Code exists? | Route to |
|---|---|---|---|---|
| "I have an idea / build something" | No | — | — | /product-spec-builder |
| "Add a feature / change something" | Yes | No | — | /change-manager propose |
| "Add a feature / change something" | Yes | Yes | — | /change-manager (resume active) |
| "This is broken / error / bug" | — | — | Yes | /bug-fixer |
| "Review / check quality" | Yes | — | Yes | /code-review |
| "Plan / how to build" | Yes | — | — | /dev-planner |
| "Build / implement / code" | Yes | — | No | /dev-builder |
| "Build / implement more" | Yes | — | Yes | /dev-builder |
| "Design / make it look good" | Yes | — | — | /design-brief-builder → /design-maker |
| "Release / deploy / ship" | — | — | Yes | /release-builder |
| "Grill me / stress-test plan / 烤问" | — | — | — | /product-spec-builder → Light Grill Mode |
| "Zoom out / explain this module" | — | — | Yes | /dev-builder → [Zoom-Out Pass] (read-only) |
| "Architecture health / ball of mud" | — | — | Yes | /dev-planner → architecture-health-pass |
| "Break into GitHub issues" | Yes | — | — | /dev-planner → optional issue slices (after plan confirm) |
| "forge-smoke failed / adapter drift / gate red" (in ReqForge repo) | — | — | — | /reqforge-greenkeeper |