@hanzlaa/rcode 3.3.0 → 3.3.1

package/rihal/workflows/discuss-phase-power.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:discuss-phase-power
+# Workflow: rihal-discuss-phase-power
 
 <purpose>
 Power user mode for discuss-phase. Generates ALL questions upfront into a JSON state file and an HTML companion UI, then waits for the user to answer at their own pace. When the user signals readiness, processes all answers in one pass and generates CONTEXT.md.
@@ -12,19 +12,19 @@ Power user mode for discuss-phase. Generates ALL questions upfront into a JSON s
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:discuss-phase --power <argument-here>
+/rihal-discuss-phase --power <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:discuss-phase --power example 1
-/rihal:discuss-phase --power example 2
+/rihal-discuss-phase --power example 1
+/rihal-discuss-phase --power example 2
 ```
 
 STOP — do not proceed.
 
 <trigger>
-This workflow executes when `--power` flag is present in ARGUMENTS to `/rihal:discuss-phase`.
+This workflow executes when `--power` flag is present in ARGUMENTS to `/rihal-discuss-phase`.
 
 The caller (discuss-phase.md) has already:
 - Validated the phase exists
@@ -284,7 +284,7 @@ Process all answered questions from the JSON file and generate CONTEXT.md.
 ```
 Warning: Only {answered}/{total} questions answered ({pct}%).
 CONTEXT.md generated with available decisions. Unanswered questions listed as deferred.
-Consider running /rihal:discuss-phase {N} again to refine before planning.
+Consider running /rihal-discuss-phase {N} again to refine before planning.
 ```
 
 7. Print completion message:
@@ -294,7 +294,7 @@ CONTEXT.md written: {phase_dir}/{padded_phase}-CONTEXT.md
   Decisions captured: {answered}
   Deferred:          {remaining}
 
-Next step: /rihal:plan-phase {N}
+Next step: /rihal-plan-phase {N}
 ```
 </step>
 

package/rihal/workflows/discuss-phase.md

@@ -124,7 +124,7 @@ This is required for Claude Code remote sessions (`/rc` mode) where the Claude A
 cannot forward TUI menu selections back to the host.
 
 Enable text mode:
-- Per-session: pass `--text` flag to any command (e.g., `/rihal:discuss-phase --text`)
+- Per-session: pass `--text` flag to any command (e.g., `/rihal-discuss-phase --text`)
 - Per-project: `rihal-tools config-set workflow.text_mode true`
 
 Text mode applies to ALL workflows in the session, not just discuss-phase.
@@ -132,7 +132,7 @@ Text mode applies to ALL workflows in the session, not just discuss-phase.
 
 <process>
 
-**Express path available:** If you already have a PRD or acceptance criteria document, use `/rihal:plan {phase} --prd path/to/prd.md` to skip this discussion and go straight to planning.
+**Express path available:** If you already have a PRD or acceptance criteria document, use `/rihal-plan {phase} --prd path/to/prd.md` to skip this discussion and go straight to planning.
 
 <step name="initialize" priority="first">
 Phase number from argument (required).
@@ -151,7 +151,7 @@ Parse JSON for: `commit_docs`, `phase_found`, `phase_dir`, `phase_number`, `phas
 ```
 Phase [X] not found in roadmap.
 
-Use /rihal:progress ${Rihal_WS} to see available phases.
+Use /rihal-progress ${Rihal_WS} to see available phases.
 ```
 Exit workflow.
 
@@ -252,7 +252,7 @@ Check `has_plans` and `plan_count` from init. **If `has_plans` is true:**
 - header: "Plans exist"
 - question: "Phase [X] already has {plan_count} plan(s) created without user context. Your decisions here won't affect existing plans unless you replan."
 - options:
-  - "Continue and replan after" — Capture context, then run /rihal:plan {X} ${Rihal_WS} to replan
+  - "Continue and replan after" — Capture context, then run /rihal-plan {X} ${Rihal_WS} to replan
   - "View existing plans" — Show plans before deciding
   - "Cancel" — Skip discuss-phase
 
@@ -554,7 +554,7 @@ After user selects gray areas in present_gray_areas, spawn parallel research age
 2. For EACH user-selected gray area, spawn a Task() in parallel:
 
    Task(
-     prompt="First, read @$HOME/.claude/agents/rihal:advisor-researcher.md for your role and instructions.
+     prompt="First, read @$HOME/.claude/agents/rihal-advisor-researcher.md for your role and instructions.
 
      <gray_area>{area_name}: {area_description from gray area identification}</gray_area>
      <phase_context>{phase_goal and description from ROADMAP.md}</phase_context>
@@ -833,7 +833,7 @@ Write after each area:
 }
 ```
 
-This is a structured checkpoint, not the final CONTEXT.md — the `write_context` step still produces the canonical output. But if the session dies, the next `/rihal:discuss-phase` invocation can detect this checkpoint and offer to resume from it instead of starting from scratch.
+This is a structured checkpoint, not the final CONTEXT.md — the `write_context` step still produces the canonical output. But if the session dies, the next `/rihal-discuss-phase` invocation can detect this checkpoint and offer to resume from it instead of starting from scratch.
 
 **On session resume:** In the `check_existing` step, also check for `*-DISCUSS-CHECKPOINT.json`. If found and no CONTEXT.md exists:
 - Display: "Found interrupted discussion checkpoint ({N} areas completed). Resume from checkpoint?"
@@ -999,14 +999,14 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 
 `/clear` then:
 
-`/rihal:plan ${PHASE} ${Rihal_WS}`
+`/rihal-plan ${PHASE} ${Rihal_WS}`
 
 ---
 
 **Also available:**
-- `/rihal:discuss-phase ${PHASE} --chain ${Rihal_WS}` — re-run with auto plan+execute after
-- `/rihal:plan ${PHASE} --skip-research ${Rihal_WS}` — plan without research
-- `/rihal:ui-phase ${PHASE} ${Rihal_WS}` — generate UI design contract before planning (if phase has frontend work)
+- `/rihal-discuss-phase ${PHASE} --chain ${Rihal_WS}` — re-run with auto plan+execute after
+- `/rihal-plan ${PHASE} --skip-research ${Rihal_WS}` — plan without research
+- `/rihal-ui-phase ${PHASE} ${Rihal_WS}` — generate UI design contract before planning (if phase has frontend work)
 - Review/edit CONTEXT.md before continuing
 
 ---
@@ -1139,22 +1139,22 @@ This keeps the auto-advance chain flat — discuss, plan, and execute all run at
 
   /clear then:
 
-  Next: /rihal:discuss-phase ${NEXT_PHASE} ${WAS_CHAIN ? "--chain" : "--auto"} ${Rihal_WS}
+  Next: /rihal-discuss-phase ${NEXT_PHASE} ${WAS_CHAIN ? "--chain" : "--auto"} ${Rihal_WS}
   ```
 - **PLANNING COMPLETE** → Planning done, execution didn't complete:
   ```
   Auto-advance partial: Planning complete, execution did not finish.
-  Continue: /rihal:execute-phase ${PHASE} ${Rihal_WS}
+  Continue: /rihal-execute-phase ${PHASE} ${Rihal_WS}
   ```
 - **PLANNING INCONCLUSIVE / CHECKPOINT** → Stop chain:
   ```
   Auto-advance stopped: Planning needs input.
-  Continue: /rihal:plan ${PHASE} ${Rihal_WS}
+  Continue: /rihal-plan ${PHASE} ${Rihal_WS}
   ```
 - **GAPS FOUND** → Stop chain:
   ```
   Auto-advance stopped: Gaps found during execution.
-  Continue: /rihal:plan ${PHASE} --gaps ${Rihal_WS}
+  Continue: /rihal-plan ${PHASE} --gaps ${Rihal_WS}
   ```
 
 **If none of `--auto`, `--chain`, nor config enabled:**

package/rihal/workflows/discuss.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:discuss
+# Workflow: rihal-discuss
 
 <purpose>
 Orchestrate a single-agent quick sync session. This is the lightweight alternative to council — one agent, one round, conversational tone, no mandatory artifact. Feels like texting one colleague, not calling a board meeting.
@@ -10,7 +10,7 @@ Lightweight — no full banner. Open with one-line header:
 ◆ Spawning {agent-id}...
 ```
 Agent response opens with header: `🧭 **Sadiq (صادق) — Director of Strategy:**`.
-No closure banner (discuss is lightweight). End with optional Next Up if the user should escalate: `Want to convene full council? /rihal:council <question>`.
+No closure banner (discuss is lightweight). End with optional Next Up if the user should escalate: `Want to convene full council? /rihal-council <question>`.
 </output_format>
 
 <required_reading>
@@ -26,15 +26,15 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:discuss [agent-name] <question>
+/rihal-discuss [agent-name] <question>
 ```
 
 **Examples:**
 ```
-/rihal:discuss sadiq should I pivot this idea?
-/rihal:discuss waleed what stack should I use for a multi-tenant SaaS?
-/rihal:discuss what's the kill criterion for this project?
-/rihal:discuss fatima is this release ready to ship?
+/rihal-discuss sadiq should I pivot this idea?
+/rihal-discuss waleed what stack should I use for a multi-tenant SaaS?
+/rihal-discuss what's the kill criterion for this project?
+/rihal-discuss fatima is this release ready to ship?
 ```
 
 Only after the user provides arguments, proceed to Step 0.5.
@@ -60,9 +60,9 @@ If either condition holds:
 ```
 ⚠ Strategic / market decisions benefit from multiple perspectives.
 
-/rihal:discuss is single-agent. For "should we" questions across domains, use:
+/rihal-discuss is single-agent. For "should we" questions across domains, use:
 
-/rihal:council $ARGUMENTS
+/rihal-council $ARGUMENTS
 ```
 
 Only proceed past this step if both checks pass — question is tactical or single-domain (codebase, team, release, design) AND top agent is sadiq/waleed/fatima.

package/rihal/workflows/do.md

@@ -86,21 +86,21 @@ If `$QUESTION` is empty, present the main menu via AskUserQuestion:
 ```
 What would you like to do?
 
-1. Quick chat with one expert (/rihal:discuss)
-2. Convene the council (/rihal:council)
-3. Discuss an unlocked phase (/rihal:discuss-phase)
-4. Plan a phase (/rihal:plan)
-5. Execute a phase (/rihal:execute)
-6. Sprint planning (/rihal:sprint-planning)
-7. Execute a sprint (/rihal:execute-sprint)
-8. Check sprint status (/rihal:sprint-status)
-9. Break milestone into epics & stories (/rihal:create-epics-and-stories)
-10. Implement a story (/rihal:dev-story)
-11. Check progress (/rihal:progress)
-12. Auto-advance to next step (/rihal:next)
-13. Debug an issue (/rihal:debug)
-14. Resume paused work (/rihal:resume-work)
-15. Add a note (/rihal:note)
+1. Quick chat with one expert (/rihal-discuss)
+2. Convene the council (/rihal-council)
+3. Discuss an unlocked phase (/rihal-discuss-phase)
+4. Plan a phase (/rihal-plan)
+5. Execute a phase (/rihal-execute)
+6. Sprint planning (/rihal-sprint-planning)
+7. Execute a sprint (/rihal-execute-sprint)
+8. Check sprint status (/rihal-sprint-status)
+9. Break milestone into epics & stories (/rihal-create-epics-and-stories)
+10. Implement a story (/rihal-dev-story)
+11. Check progress (/rihal-progress)
+12. Auto-advance to next step (/rihal-next)
+13. Debug an issue (/rihal-debug)
+14. Resume paused work (/rihal-resume-work)
+15. Add a note (/rihal-note)
 16. Something else — describe it
 ```
 
@@ -136,18 +136,18 @@ Apply this guard BEFORE the routing table below:
 
 | Intent contains... | AND state shows... | Then re-route to... | Why |
 |--------------------|---------------------|----------------------|-----|
-| "draft phases", "all phases", "build all phases", "groom phases", "auto mode" + "phases" | `HAS_PRD=false` | `/rihal:create-prd` first | Phases need a PRD foundation. Without one, the autonomous flow hallucinates requirements. |
-| "execute phase", "build phase N", "run phase N" | `HAS_PHASES=false` OR PLAN.md missing for phase N | `/rihal:plan N` first (or `/rihal:create-prd` if no PRD) | Can't execute what hasn't been planned. |
-| "sprint planning", "plan the sprint" | `HAS_EPICS=false` | `/rihal:create-epics-and-stories` first | Sprints draw stories from epics. No epics = no stories to schedule. |
-| "create stories", "epics" | `HAS_PRD=false` | `/rihal:create-prd` first | Epics decompose a milestone. Milestone needs PRD. |
-| "create milestones", "roadmap" | `HAS_PRD=false` | `/rihal:create-prd` first | Roadmap is derived from PRD success metrics. |
+| "draft phases", "all phases", "build all phases", "groom phases", "auto mode" + "phases" | `HAS_PRD=false` | `/rihal-create-prd` first | Phases need a PRD foundation. Without one, the autonomous flow hallucinates requirements. |
+| "execute phase", "build phase N", "run phase N" | `HAS_PHASES=false` OR PLAN.md missing for phase N | `/rihal-plan N` first (or `/rihal-create-prd` if no PRD) | Can't execute what hasn't been planned. |
+| "sprint planning", "plan the sprint" | `HAS_EPICS=false` | `/rihal-create-epics-and-stories` first | Sprints draw stories from epics. No epics = no stories to schedule. |
+| "create stories", "epics" | `HAS_PRD=false` | `/rihal-create-prd` first | Epics decompose a milestone. Milestone needs PRD. |
+| "create milestones", "roadmap" | `HAS_PRD=false` | `/rihal-create-prd` first | Roadmap is derived from PRD success metrics. |
 
 When the guard fires, print a clear message:
 
 ```
 ⚠ Cannot {requested action}: missing prerequisite — {what's missing}.
 
-Re-routing to: /rihal:{prerequisite-command}
+Re-routing to: /rihal-{prerequisite-command}
 Once that completes, re-run your original request.
 ```
 
@@ -159,7 +159,7 @@ The guard never silently rejects intent — it always either dispatches to a sen
 <step name="external_data_guard" priority="first-match">
 **Block code-only routing when the actionable signal lives in an external system.**
 
-Some tasks reference systems whose data is NOT in the repo — observability platforms, issue trackers, analytics, and product dashboards. A pure codebase scan can map *instrumentation* but cannot classify *what is actually firing*. Routing such requests to `/rihal:scan` or `/rihal:map-codebase` without first establishing a data source produces theoretical output (violates the codebase-first rule).
+Some tasks reference systems whose data is NOT in the repo — observability platforms, issue trackers, analytics, and product dashboards. A pure codebase scan can map *instrumentation* but cannot classify *what is actually firing*. Routing such requests to `/rihal-scan` or `/rihal-map-codebase` without first establishing a data source produces theoretical output (violates the codebase-first rule).
 
 **External-data signals** — match if `$QUESTION` contains any of:
 
@@ -185,9 +185,9 @@ How should we access the external data?
 ```
 
 Then route accordingly:
-- **Option 1:** Continue to `route` step but tag the chosen command with a note to use the external data source. If no Rihal command natively reads the external system, route to `/rihal:discuss` and have the agent guide MCP/API setup.
-- **Option 2:** Route to `/rihal:discuss` so the user can paste data into a focused conversation, OR `/rihal:note` to capture, then re-run.
-- **Option 3:** Continue to `route` step normally (likely `/rihal:scan` or `/rihal:map-codebase`) but display a clear caveat: *"Output will be an instrumentation map only — it cannot classify which errors are noisy vs critical."*
+- **Option 1:** Continue to `route` step but tag the chosen command with a note to use the external data source. If no Rihal command natively reads the external system, route to `/rihal-discuss` and have the agent guide MCP/API setup.
+- **Option 2:** Route to `/rihal-discuss` so the user can paste data into a focused conversation, OR `/rihal-note` to capture, then re-run.
+- **Option 3:** Continue to `route` step normally (likely `/rihal-scan` or `/rihal-map-codebase`) but display a clear caveat: *"Output will be an instrumentation map only — it cannot classify which errors are noisy vs critical."*
 - **Option 4:** Stop. Print the original input back so the user can rephrase.
 
 Skip this guard when `AUTO_MODE=true` AND the input explicitly contains `--codebase-only` or `instrumentation map` — those signal the user already accepted the limitation.
@@ -198,7 +198,7 @@ Skip this guard when `AUTO_MODE=true` AND the input explicitly contains `--codeb
 
 When the user uses a literal create/make/start verb paired with a scope-noun (milestone, phase, story, epic, sprint, plan, PRD, roadmap, council), dispatch IMMEDIATELY. Do not present a multi-route ambiguity menu. The user already chose.
 
-This was a real bug: `/rihal:do "milestone bnao aur ... list down karo"` triggered an ambiguity prompt offering new-milestone vs add-phase vs create-epics-and-stories — even though the user literally said "milestone bnao" (= "create a milestone" in Roman Urdu). That second-guessing wasted the user's time and broke trust.
+This was a real bug: `/rihal-do "milestone bnao aur ... list down karo"` triggered an ambiguity prompt offering new-milestone vs add-phase vs create-epics-and-stories — even though the user literally said "milestone bnao" (= "create a milestone" in Roman Urdu). That second-guessing wasted the user's time and broke trust.
 
 **Verb + scope detection — sourced from `@.rihal/references/verb-dictionary.md`.**
 
@@ -208,15 +208,15 @@ The full mapping is in the dictionary's "Scope nouns" table. Pre-conditions enfo
 
 | Scope noun | Direct route | Pre-condition (this workflow only) |
 |---|---|---|
-| milestone | `/rihal:new-milestone` | none — methodology chain assumed when greenfield_guard cleared |
-| phase | `/rihal:add-phase` | HAS_PHASES OR HAS_PRD true |
-| story | `/rihal:create-story` | HAS_EPICS true |
-| epic | `/rihal:create-epics-and-stories` | HAS_PRD true |
-| sprint | `/rihal:sprint-planning` | HAS_EPICS true |
-| PRD | `/rihal:create-prd` | none |
-| roadmap | `/rihal:create-milestone` | HAS_PRD true |
-| council | `/rihal:council` | none |
-| plan (verb) | `/rihal:plan` | HAS_PHASES true |
+| milestone | `/rihal-new-milestone` | none — methodology chain assumed when greenfield_guard cleared |
+| phase | `/rihal-add-phase` | HAS_PHASES OR HAS_PRD true |
+| story | `/rihal-create-story` | HAS_EPICS true |
+| epic | `/rihal-create-epics-and-stories` | HAS_PRD true |
+| sprint | `/rihal-sprint-planning` | HAS_EPICS true |
+| PRD | `/rihal-create-prd` | none |
+| roadmap | `/rihal-create-milestone` | HAS_PRD true |
+| council | `/rihal-council` | none |
+| plan (verb) | `/rihal-plan` | HAS_PHASES true |
 
 **Behavior:**
 1. If both a verb AND a scope-noun match, fire this step.
@@ -231,10 +231,10 @@ The naive route is "user said milestone bnao → dispatch new-milestone". But if
 
 | Verb + scope | State signal | Redirect | Banner message |
 |---|---|---|---|
-| create + milestone | `$ACTIVE_MILESTONE` is non-empty AND user did NOT pass `--force-new-milestone` | `/rihal:add-phase` | `$ACTIVE_MILESTONE is active — adding as a phase to it instead of opening a new milestone. Override: add `--force-new-milestone` to the original input.` |
-| create + milestone | No active milestone | `/rihal:new-milestone $NEXT_VERSION` (auto-derived from `$LAST_SHIPPED_VERSION` + 0.1) | `Auto-versioned $NEXT_VERSION based on last shipped $LAST_SHIPPED_VERSION.` |
-| create + phase | `$HAS_PHASES=false` AND `$HAS_PRD=false` | `/rihal:create-prd` | greenfield_guard already covers this; this row is for completeness. |
-| create + story | `$HAS_EPICS=false` | `/rihal:create-epics-and-stories` (greenfield_guard) | likewise. |
+| create + milestone | `$ACTIVE_MILESTONE` is non-empty AND user did NOT pass `--force-new-milestone` | `/rihal-add-phase` | `$ACTIVE_MILESTONE is active — adding as a phase to it instead of opening a new milestone. Override: add `--force-new-milestone` to the original input.` |
+| create + milestone | No active milestone | `/rihal-new-milestone $NEXT_VERSION` (auto-derived from `$LAST_SHIPPED_VERSION` + 0.1) | `Auto-versioned $NEXT_VERSION based on last shipped $LAST_SHIPPED_VERSION.` |
+| create + phase | `$HAS_PHASES=false` AND `$HAS_PRD=false` | `/rihal-create-prd` | greenfield_guard already covers this; this row is for completeness. |
+| create + story | `$HAS_EPICS=false` | `/rihal-create-epics-and-stories` (greenfield_guard) | likewise. |
 
 **Auto-version computation when no milestone is active:**
 
@@ -251,7 +251,7 @@ fi
 
 Pass `$NEXT_VERSION` as the dispatch arg. The user is NOT prompted to pick a version — the workflow just chose the right one based on history.
 
-**Edge case — multiple scope-nouns in one input** (e.g. "milestone bnao aur usmy phase 1 banao"): take the OUTER/PARENT scope. "Milestone bnao aur usmy phase X" → state-aware-redirect kicks in. If active milestone exists → `/rihal:add-phase` (the inner phase becomes the dispatched action directly). If not → `/rihal:new-milestone $NEXT_VERSION` (the dispatched workflow will create phase 1 internally).
+**Edge case — multiple scope-nouns in one input** (e.g. "milestone bnao aur usmy phase 1 banao"): take the OUTER/PARENT scope. "Milestone bnao aur usmy phase X" → state-aware-redirect kicks in. If active milestone exists → `/rihal-add-phase` (the inner phase becomes the dispatched action directly). If not → `/rihal-new-milestone $NEXT_VERSION` (the dispatched workflow will create phase 1 internally).
 
 **Edge case — verb without scope-noun** (e.g. "kuch karo", "do something"): do NOT fire this step. Fall through to the normal routing table which can ask for clarification.
 
@@ -269,37 +269,37 @@ Evaluate `$QUESTION` against these routing rules. Apply the **first matching** r
 
 | If the text describes... | Route to | Why |
 |--------------------------|----------|-----|
-| Starting a new project, "set up", "initialize" | `/rihal:new-project` | Needs full project initialization |
-| Mapping or analyzing an existing codebase | `/rihal:map-codebase` | Codebase discovery |
-| A bug, error, crash, failure, or something broken | `/rihal:debug` | Needs systematic investigation |
-| Validate an idea, "working backwards", "press release", "PRFAQ", "is this worth building" | `/rihal:prfaq` | Stress-test concept before committing sprint capacity |
-| Brainstorm, generate ideas, "explore options", "what could we do" | `/rihal:brainstorm` | Structured ideation before planning |
-| Audit code quality, "review changes", "karpathy", "check my diff", "too complex" | `/rihal:code-review --karpathy` | 4-principle code audit against recent diff |
-| Walk through a change, "checkpoint", "explain this diff", "human review" | `/rihal:checkpoint-preview` | Human-in-the-loop diff walkthrough |
-| Exploring, researching, comparing, or "how does X work" | `/rihal:research-phase` | Domain research before planning |
-| Scope unclear, conflicting UIs/options, "which one", "better UX", "still have confusion", "how should X look", brainstorming vision | `/rihal:discuss-phase` | Decisions not yet locked — gather before planning |
-| A complex task: refactoring, migration, multi-file architecture, system redesign | `/rihal:add-phase` | Needs a full phase with plan/build cycle |
-| Planning a specific phase, "plan phase N" | `/rihal:plan` | Direct phase-level planning |
-| "Sprint planning", "plan the sprint", "next sprint", "what's in this sprint" | `/rihal:sprint-planning` | Sprint-level scope/capacity planning |
-| Executing a sprint, "run the sprint", "start sprint", "work on sprint" | `/rihal:execute-sprint` | Sprint execution with wave batching |
-| Sprint status, "how is the sprint going", "sprint board", "sprint progress" | `/rihal:sprint-status` | Current sprint state |
-| "Create milestones", "plan milestones", "create roadmap", "what milestones do I need", "break project into milestones" | `/rihal:create-milestone` | Roadmap-level planning — designs M1..Mn from the PRD. Do NOT route to `create-epics-and-stories`; that skill decomposes a single milestone into epics |
-| Break milestone into epics/stories, "create stories", "user stories", "epics" | `/rihal:create-epics-and-stories` | Milestone → epic → story decomposition (assumes roadmap already exists) |
-| Create a single story, "add story", "write a story for X" | `/rihal:create-story` | Single story addition |
-| Implement a story, "work on story", "dev story", "build story" | `/rihal:dev-story` | Story-level implementation |
-| Find gaps in milestone plans, "gaps in plans", "missing plan", "unplanned phases" | `/rihal:plan-milestone-gaps` | Identify and fill planning gaps |
-| Executing a phase, "build phase N", "run phase N", "implement phase" | `/rihal:execute` | Direct phase execution request |
-| Running all remaining phases automatically | `/rihal:autonomous` | Full autonomous execution |
-| A review or quality concern about existing work | `/rihal:verify-work` | Needs verification |
-| "Council", "discuss strategy", "should we" | `/rihal:council` | Multi-agent strategic discussion |
-| List plans across phases, "all plans", "show plans" | `/rihal:list-plans` | Cross-phase plan table |
-| Checking progress, status, "where am I", "board" | `/rihal:progress` | Status check |
-| Resuming work, "pick up where I left off" | `/rihal:resume-work` | Session restoration |
-| A note, idea, or "remember to..." | `/rihal:note` | Capture for later |
-| Adding tests, "write tests", "test coverage" | `/rihal:add-tests` | Test generation |
-| Completing a milestone, shipping, releasing | `/rihal:complete-milestone` | Milestone lifecycle |
-| A specific, actionable, small task (add feature, fix typo, update config) | `/rihal:quick` | Self-contained, single executor |
-| Market/discovery/greenfield question (from classify) | `/rihal:council` | Needs multi-perspective discovery |
+| Starting a new project, "set up", "initialize" | `/rihal-new-project` | Needs full project initialization |
+| Mapping or analyzing an existing codebase | `/rihal-map-codebase` | Codebase discovery |
+| A bug, error, crash, failure, or something broken | `/rihal-debug` | Needs systematic investigation |
+| Validate an idea, "working backwards", "press release", "PRFAQ", "is this worth building" | `/rihal-prfaq` | Stress-test concept before committing sprint capacity |
+| Brainstorm, generate ideas, "explore options", "what could we do" | `/rihal-brainstorm` | Structured ideation before planning |
+| Audit code quality, "review changes", "karpathy", "check my diff", "too complex" | `/rihal-code-review --karpathy` | 4-principle code audit against recent diff |
+| Walk through a change, "checkpoint", "explain this diff", "human review" | `/rihal-checkpoint-preview` | Human-in-the-loop diff walkthrough |
+| Exploring, researching, comparing, or "how does X work" | `/rihal-research-phase` | Domain research before planning |
+| Scope unclear, conflicting UIs/options, "which one", "better UX", "still have confusion", "how should X look", brainstorming vision | `/rihal-discuss-phase` | Decisions not yet locked — gather before planning |
+| A complex task: refactoring, migration, multi-file architecture, system redesign | `/rihal-add-phase` | Needs a full phase with plan/build cycle |
+| Planning a specific phase, "plan phase N" | `/rihal-plan` | Direct phase-level planning |
+| "Sprint planning", "plan the sprint", "next sprint", "what's in this sprint" | `/rihal-sprint-planning` | Sprint-level scope/capacity planning |
+| Executing a sprint, "run the sprint", "start sprint", "work on sprint" | `/rihal-execute-sprint` | Sprint execution with wave batching |
+| Sprint status, "how is the sprint going", "sprint board", "sprint progress" | `/rihal-sprint-status` | Current sprint state |
+| "Create milestones", "plan milestones", "create roadmap", "what milestones do I need", "break project into milestones" | `/rihal-create-milestone` | Roadmap-level planning — designs M1..Mn from the PRD. Do NOT route to `create-epics-and-stories`; that skill decomposes a single milestone into epics |
+| Break milestone into epics/stories, "create stories", "user stories", "epics" | `/rihal-create-epics-and-stories` | Milestone → epic → story decomposition (assumes roadmap already exists) |
+| Create a single story, "add story", "write a story for X" | `/rihal-create-story` | Single story addition |
+| Implement a story, "work on story", "dev story", "build story" | `/rihal-dev-story` | Story-level implementation |
+| Find gaps in milestone plans, "gaps in plans", "missing plan", "unplanned phases" | `/rihal-plan-milestone-gaps` | Identify and fill planning gaps |
+| Executing a phase, "build phase N", "run phase N", "implement phase" | `/rihal-execute` | Direct phase execution request |
+| Running all remaining phases automatically | `/rihal-autonomous` | Full autonomous execution |
+| A review or quality concern about existing work | `/rihal-verify-work` | Needs verification |
+| "Council", "discuss strategy", "should we" | `/rihal-council` | Multi-agent strategic discussion |
+| List plans across phases, "all plans", "show plans" | `/rihal-list-plans` | Cross-phase plan table |
+| Checking progress, status, "where am I", "board" | `/rihal-progress` | Status check |
+| Resuming work, "pick up where I left off" | `/rihal-resume-work` | Session restoration |
+| A note, idea, or "remember to..." | `/rihal-note` | Capture for later |
+| Adding tests, "write tests", "test coverage" | `/rihal-add-tests` | Test generation |
+| Completing a milestone, shipping, releasing | `/rihal-complete-milestone` | Milestone lifecycle |
+| A specific, actionable, small task (add feature, fix typo, update config) | `/rihal-quick` | Self-contained, single executor |
+| Market/discovery/greenfield question (from classify) | `/rihal-council` | Needs multi-perspective discovery |
 
 If no rule matches, fall back to the classifier:
 
@@ -307,9 +307,9 @@ If no rule matches, fall back to the classifier:
 CLASSIFY=$(node ".rihal/bin/rihal-tools.cjs" classify-question "$QUESTION")
 ```
 
-Parse `type` from JSON — map codebase/team/release → `/rihal:discuss`; market/discovery/greenfield → `/rihal:council`. Default: `/rihal:discuss`.
+Parse `type` from JSON — map codebase/team/release → `/rihal-discuss`; market/discovery/greenfield → `/rihal-council`. Default: `/rihal-discuss`.
 
-**Requires `.planning/` directory:** All routes except `/rihal:new-project`, `/rihal:map-codebase`, `/rihal:help`, `/rihal:discuss`, `/rihal:council`. If the project doesn't exist and the route requires it, suggest `/rihal:new-project` first.
+**Requires `.planning/` directory:** All routes except `/rihal-new-project`, `/rihal-map-codebase`, `/rihal-help`, `/rihal-discuss`, `/rihal-council`. If the project doesn't exist and the route requires it, suggest `/rihal-new-project` first.
 
 **Ambiguity handling:** If the text could reasonably match multiple routes, ask the user via AskUserQuestion with the top 2-3 options. Prefer `discuss-phase` over `plan`/`add-phase` when scope-uncertainty signals are present ("confusion", "not sure", "which one", "better way", "how should", ≥2 conflicting UIs/options mentioned).
 
@@ -317,9 +317,9 @@ Example:
 
 ```
 "Refactor the auth system" could be:
-1. /rihal:add-phase — Full planning cycle (recommended for multi-file refactors)
-2. /rihal:discuss-phase — Gather decisions first (recommended if scope is fuzzy)
-3. /rihal:quick — Quick execution (if scope is small and clear)
+1. /rihal-add-phase — Full planning cycle (recommended for multi-file refactors)
+2. /rihal-discuss-phase — Gather decisions first (recommended if scope is fuzzy)
+3. /rihal-quick — Quick execution (if scope is small and clear)
 
 Which approach fits better?
 ```
@@ -346,13 +346,13 @@ Reason: {one-line why}
 If `AUTO_MODE` is true OR routing is unambiguous, invoke immediately:
 
 ```
-/rihal:{command} {arguments}
+/rihal-{command} {arguments}
 ```
 
 Otherwise show suggestion and ask via AskUserQuestion:
 
 ```
-Based on your request, I'd use: /rihal:{command} {arguments}
+Based on your request, I'd use: /rihal-{command} {arguments}
 
 1. Yes, run it
 2. Pick a different route
@@ -370,7 +370,7 @@ After invoking the command, stop. The dispatched command handles everything from
 - [ ] Input validated (not empty)
 - [ ] Intent matched to exactly one Rihal command
 - [ ] Ambiguity resolved via user question (if needed)
-- [ ] Scope-uncertainty signals steer to `/rihal:discuss-phase` over planning routes
+- [ ] Scope-uncertainty signals steer to `/rihal-discuss-phase` over planning routes
 - [ ] Project existence checked for routes that require it
 - [ ] Routing decision displayed before dispatch
 - [ ] Command invoked with appropriate arguments

package/rihal/workflows/docs-update.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:docs-update
+# Workflow: rihal-docs-update
 
 <purpose>
 Generate, update, and verify project documentation — both canonical doc types and existing hand-written docs. The orchestrator detects the project's doc structure, assembles a work manifest tracking every item, dispatches parallel doc-writer and doc-verifier agents across waves, reviews existing docs for accuracy, identifies documentation gaps, and fixes inaccuracies via a bounded fix loop. All state is persisted in a work manifest so no work item is lost between steps. Output: Complete, structure-aware documentation verified against the live codebase.
@@ -18,13 +18,13 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:docs-update [phase]
+/rihal-docs-update [phase]
 ```
 
 **Examples:**
 ```
-/rihal:docs-update
-/rihal:docs-update 02
+/rihal-docs-update
+/rihal-docs-update 02
 ```
 
 <process>
@@ -224,10 +224,10 @@ ${ISSUES:+
 Issues to fix:
 {list}
 
-Run /rihal:docs-update --fix to auto-correct found issues.
+Run /rihal-docs-update --fix to auto-correct found issues.
 }
 
-Next: Review docs in your editor or run verification again with /rihal:docs-update
+Next: Review docs in your editor or run verification again with /rihal-docs-update
 ```
 
 </process>

package/rihal/workflows/document-project.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:document-project
+# Workflow: rihal-document-project
 
 <purpose>
 Load documentation-requirements.csv, audit current documentation for coverage and staleness, identify missing or outdated docs, and file them as SPRINT.md subtasks or separate plan phases.
@@ -10,13 +10,13 @@ Load documentation-requirements.csv, audit current documentation for coverage an
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:document-project <argument-here>
+/rihal-document-project <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:document-project example 1
-/rihal:document-project example 2
+/rihal-document-project example 1
+/rihal-document-project example 2
 ```
 
 STOP — do not proceed.
@@ -152,7 +152,7 @@ Summary:
 
 Missing docs filed as tasks. Run:
 
-/rihal:plan .planning/plans/documentation-updates/SPRINT.md
+/rihal-plan .planning/plans/documentation-updates/SPRINT.md
 ```
 
 ## Step 5 — Auto-inject into Resume-Work

package/rihal/workflows/enable-hooks.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:enable-hooks
+# Workflow: rihal-enable-hooks
 
 <purpose>
 Merge Rihal opt-in hooks from settings-hooks.json into .claude/settings.json. Creates settings.json if missing. Enables pre-edit (read-before-edit check), pre-workflow (command hint), and post-commit (format validation) guardrails.
@@ -10,13 +10,13 @@ Merge Rihal opt-in hooks from settings-hooks.json into .claude/settings.json. Cr
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:enable-hooks <argument-here>
+/rihal-enable-hooks <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:enable-hooks example 1
-/rihal:enable-hooks example 2
+/rihal-enable-hooks example 1
+/rihal-enable-hooks example 2
 ```
 
 STOP — do not proceed.
@@ -79,7 +79,7 @@ Print success message:
 
 Enabled guardrails:
   • pre-edit: Verifies files are Read() before Edit/Write
-  • pre-workflow: Warns if rihal:* commands look suspicious
+  • pre-workflow: Warns if rihal-* commands look suspicious
   • post-commit: Validates commit format and bans "Generated with Claude" patterns
 
 To disable, remove the hooks section from .claude/settings.json or edit .rihal/templates/settings-hooks.json and re-run.

package/rihal/workflows/execute-sprint.md

@@ -499,9 +499,9 @@ If `USER_SETUP_CREATED=true`: display `⚠️ USER SETUP REQUIRED` with path + e
 
 | Condition | Route | Action |
 |-----------|-------|--------|
-| summaries < plans | **A: More plans** | Find next PLAN without SUMMARY. Yolo: auto-continue. Interactive: show next plan, suggest `/rihal:execute-phase {phase}` + `/rihal:verify-work`. STOP here. |
-| summaries = plans, current < highest phase | **B: Phase done** | Show completion, suggest `/rihal:plan-phase {Z+1}` + `/rihal:verify-work {Z}` + `/rihal:discuss-phase {Z+1}` |
-| summaries = plans, current = highest phase | **C: Milestone done** | Show banner, suggest `/rihal:complete-milestone` + `/rihal:verify-work` + `/rihal:add-phase` |
+| summaries < plans | **A: More plans** | Find next PLAN without SUMMARY. Yolo: auto-continue. Interactive: show next plan, suggest `/rihal-execute-phase {phase}` + `/rihal-verify-work`. STOP here. |
+| summaries = plans, current < highest phase | **B: Phase done** | Show completion, suggest `/rihal-plan-phase {Z+1}` + `/rihal-verify-work {Z}` + `/rihal-discuss-phase {Z+1}` |
+| summaries = plans, current = highest phase | **C: Milestone done** | Show banner, suggest `/rihal-complete-milestone` + `/rihal-verify-work` + `/rihal-add-phase` |
 
 All routes: `/clear` first for fresh context.
 </step>