Dream Routing

Routing Priority

When multiple intents could match, use this priority order:

1. Explicit skill name — user says "use dream-close" → route directly
2. Explicit plan ID — "Fix PP{NN}" → resolve plan, then route by verb
3. Action verb — "Create", "Close", "Fix" → match dispatch table
4. Fallback — ambiguous → disambiguate (see rules below)

Plan Type Detection

Determine SP vs PP BEFORE routing to a create skill. Plan type is about the NATURE of the work, not scope size.

Note: Task count and scope size determine TIER (One-Page vs Blueprint), not plan TYPE (SP vs PP). A small architecture change is still an SP; a large migration is still a PP.

Quick Decision

Is the primary deliverable NEW architecture?
  YES → SP (System Plan)
  NO  → Is it a workflow, migration, or process change?
    YES → PP (Procedure Plan)
    NO  → Ask user: "Is this new architecture (SP) or a process/migration (PP)?"

Disambiguation Rules

When user intent is ambiguous, resolve before routing.

Never Guess

If disambiguation rules don't resolve the intent, ask. One clarifying question is faster than undoing a wrong operation.

Dispatch Protocol

Execute these steps in order for every DREAM request:

1. Classify — Match user intent against the dispatch table
2. Detect plan type — If creating, determine SP or PP
3. Disambiguate — If ambiguous, apply disambiguation rules; ask if still unclear
4. Resolve target — If a plan ID is mentioned, verify it exists
5. Load leaf skill — Route to the target skill from the dispatch table
6. Execute — Follow the leaf skill's SOP

Routing Failures

Leaf Skill Status

For planned skills that don't yet exist, fall back to dream-vision (for exploratory work) or dream-planning (for structural work) as appropriate.

Templates

All DREAM document templates are bundled with this skill in assets/.

Full template catalog: assets/ subdirectory of this skill.

What This Skill Does NOT Do

Anti-Patterns

Cross-References