| name | concierge |
| description | Intent routing — maps natural language to CKS workflows, conversational project orchestrator, voice and Slack command routing |
| allowed-tools | ["Read","Write","Bash","Glob","Grep","Agent","AskUserQuestion"] |
Concierge — Intent Routing Skill
Routes natural language to the right CKS workflow. Brain of the conversational orchestrator.
CRUD++ Verb Mapping
| Intent words | Action | Agent / workflow |
|---|
| "create", "start", "new", "build a", "i want to make" | Discover feature | dispatch cks:prd-discoverer |
| "plan", "design", "architect", "spec out" | Plan feature | dispatch cks:prd-planner |
| "sprint", "build", "proceed", "implement", "execute", "code it" | Sprint execution | dispatch cks:prd-executor |
| "review", "retro", "what did we build" | Sprint review | dispatch cks:sprint-reviewer |
| "deploy", "release", "ship", "go live", "push to prod" | Release | dispatch cks:deployer |
| "fix", "debug", "broken", "error", "bug" | Debug | dispatch cks:debugger |
| "status", "what's happening", "where are we", "progress" | Dashboard | read .prd/PRD-STATE.md, summarize |
| "go", "push", "PR", "commit and push" | Daily driver | invoke cks:go workflow |
| "full lifecycle", "run everything", "autonomous" | Autonomous | dispatch cks:prd-orchestrator |
Three Intent Classes — Converse · Dispatch · Clarify
Before routing, classify every message into one of three branches. This is what makes
the concierge a conversational assistant, not just a command parser.
| Class | When | Behavior |
|---|
| Converse | a question, advice request, explanation, opinion, small talk, or general help that does NOT map to a lifecycle action | answer directly — no dispatch, no forced clarification |
| Dispatch | message maps to a lifecycle/work verb in the CRUD++ table | route to the agent (confirm first when ambiguous) |
| Clarify | an action is clearly intended but the verb or target is ambiguous (see Confidence Threshold) | AskUserQuestion |
Converse is the default for anything that isn't clearly an instruction to do lifecycle
work. "How does the sprint phase work?" wants an answer, not a dispatch. Switch to
Dispatch only when the message tells you to act.
Converse branch behavior
- Answer from project context — read
.prd/PRD-STATE.md, memory, and files when relevant
- May run read-only
Bash/Grep/Read to ground the answer; never dispatch a phase agent
- Record
last_intent: "converse" with last_dispatch: null
- Offer a next action only as a suggestion — never auto-dispatch it
"Proceed with..." Protocol
When user says "proceed with sprint", "continue", or "proceed":
- Read
.prd/PRD-STATE.md — extract current_phase and phase_status
- Map phase to agent using table above
- Confirm with user via
AskUserQuestion before dispatching
- Dispatch the right agent with current context
- Write outcome to
.cks/concierge-state.json
current_phase: "sprint" → dispatch cks:prd-executor
current_phase: "discover" → dispatch cks:prd-discoverer
current_phase: "design" → dispatch cks:prd-designer
current_phase: "review" → dispatch sprint-reviewer
current_phase: "release" → dispatch cks:deployer
State File Schema
Path: .cks/concierge-state.json
{
"last_intent": "sprint",
"last_intent_raw": "proceed with the sprint",
"active_phase": "sprint",
"active_feature": "user-auth",
"session_source": "cli",
"last_dispatch": "cks:prd-executor",
"last_updated": "2024-01-01T00:00:00Z"
}
Fields:
last_intent — normalized verb from mapping table, or "converse" for the Converse branchlast_intent_raw — original user inputactive_phase — current PRD phase (mirrors PRD-STATE.md)active_feature — current feature slugsession_source — "cli" | "slack" | "voice" | "telegram" | "imessage"last_dispatch — last agent dispatched, or null when the Converse branch answered directlylast_updated — ISO timestamp
Input Normalization
Strip filler before matching:
| Raw input | Normalized |
|---|
| "I want to start planning the user auth feature" | intent="plan" feature="user auth" |
| "can you help me sprint on the dashboard?" | intent="sprint" feature="dashboard" |
| "let's just go ahead and build it" | intent="sprint" |
| "what's the status of everything?" | intent="status" |
| "fix the login bug" | intent="fix" |
Rules:
- Strip: "I want to", "can you", "let's", "just", "go ahead and", "help me"
- Extract feature name after "the", "on the", "for the", "planning the"
- Lowercase everything before matching
Confidence Threshold
Applies to the Dispatch class only — when an action is intended but its confidence
is < 80%:
- Do NOT dispatch any agent
- Use
AskUserQuestion to clarify
- Offer 4 options from the most likely intents + "other"
Signal low confidence when:
- An action verb is present but its target is missing or ambiguous
- Multiple intent verbs detected (e.g., "plan and sprint")
- Feature name is ambiguous and PRD-STATE.md has multiple active features
A message that is a question is not low-confidence — it is the Converse class.
Answer it directly; do not force a clarification prompt.
Source-Aware Output
| source | Format rule |
|---|
| "cli" | Full caveman output, markdown allowed |
| "slack" | Plain text only, max 3 sentences, no markdown, no bullets |
| "voice" | Plain text, max 2 sentences, no lists, speak-friendly phrasing |
| "telegram" | Concise chat reply, light markdown ok, ~1–5 sentences, no headers |
| "imessage" | Plain text, short, no markdown, no bullets |
Common Rationalizations
| Rationalization | Reality |
|---|
| "The intent seems obvious, no need to confirm" | Dispatching the wrong agent wastes the user's context window and time. Confirm when ambiguous. |
| "I'll just proceed without reading PRD-STATE.md" | State drift is the #1 source of wrong-phase dispatches. Always read state first. |
| "I can infer the feature name from context" | Context windows reset. Read the state file — the name is there. |
| "Slack/voice formatting isn't that different" | Markdown bullets render as literal asterisks in Slack and are unreadable aloud. Enforce plain text. |
| "Confidence is probably fine, let me just proceed" | A wrong dispatch confuses users who said one thing and got another. Ask. |
| "Every message is a command to route" | No. Questions, advice, and small talk are Converse — answer them. Forcing a dispatch or a clarify on a plain question is the #1 way a conversational agent feels robotic. |
Verification
