@hanzlaa/rcode 3.3.0 → 3.3.1

package/rihal/workflows/code-review-fix.md

@@ -19,13 +19,13 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:code-review-fix <phase> [--auto]
+/rihal-code-review-fix <phase> [--auto]
 ```
 
 **Examples:**
 ```
-/rihal:code-review-fix 01
-/rihal:code-review-fix 02.1 --auto
+/rihal-code-review-fix 01
+/rihal-code-review-fix 02.1 --auto
 ```
 
 <process>
@@ -53,7 +53,7 @@ fi
 **Phase validation (before config gate):**
 If `phase_found` is false, report error and exit:
 ```
-Error: Phase ${PHASE_ARG} not found. Run /rihal:status to see available phases.
+Error: Phase ${PHASE_ARG} not found. Run /rihal-status to see available phases.
 ```
 
 This runs BEFORE config gate check so user errors are surfaced immediately regardless of config state.
@@ -110,7 +110,7 @@ Verify that REVIEW.md exists:
 
 ```bash
 if [ ! -f "${REVIEW_PATH}" ]; then
-  echo "Error: No REVIEW.md found for Phase ${PHASE_ARG}. Run /rihal:code-review ${PHASE_ARG} first."
+  echo "Error: No REVIEW.md found for Phase ${PHASE_ARG}. Run /rihal-code-review ${PHASE_ARG} first."
   exit 1
 fi
 ```
@@ -238,7 +238,7 @@ Check if FIX_REPORT_PATH exists:
 Either way:
 ```
 Some fix commits may already exist in git history — check git log for fix(${PADDED_PHASE}) commits.
-You can retry with /rihal:code-review-fix ${PHASE_ARG}.
+You can retry with /rihal-code-review-fix ${PHASE_ARG}.
 ```
 
 Exit workflow (skip auto loop).
@@ -411,7 +411,7 @@ if [ ! -f "${FIX_REPORT_PATH}" ]; then
   echo "The fixer agent may have failed before completing."
   echo "Check git log for any fix(${PADDED_PHASE}) commits."
   echo ""
-  echo "Retry: /rihal:code-review-fix ${PHASE_ARG}"
+  echo "Retry: /rihal-code-review-fix ${PHASE_ARG}"
   echo ""
   echo "═══════════════════════════════════════════════════════════════"
   exit 1
@@ -468,7 +468,7 @@ if [ "$FIX_STATUS" = "all_fixed" ]; then
   echo "Full report: ${FIX_REPORT_PATH}"
   echo ""
   echo "Next step:"
-  echo "  /rihal:verify-work  — Verify phase completion"
+  echo "  /rihal-verify-work  — Verify phase completion"
   echo ""
 fi
 ```
@@ -482,8 +482,8 @@ if [ "$FIX_STATUS" = "partial" ] || [ "$FIX_STATUS" = "none_fixed" ]; then
   echo ""
   echo "Next steps:"
   echo "  cat ${FIX_REPORT_PATH}                     — View fix report"
-  echo "  /rihal:code-review ${PHASE_NUMBER}         — Re-review code"
-  echo "  /rihal:verify-work                         — Verify phase completion"
+  echo "  /rihal-code-review ${PHASE_NUMBER}         — Re-review code"
+  echo "  /rihal-verify-work                         — Verify phase completion"
   echo ""
 fi
 ```

package/rihal/workflows/code-review.md

@@ -18,15 +18,15 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:code-review <phase> [--depth=quick|standard|deep] [--files=path1,path2] [--karpathy]
+/rihal-code-review <phase> [--depth=quick|standard|deep] [--files=path1,path2] [--karpathy]
 ```
 
 **Examples:**
 ```
-/rihal:code-review 01
-/rihal:code-review 02.1 --depth=deep
-/rihal:code-review 03 --files=src/auth.js,src/db.js
-/rihal:code-review HEAD~5..HEAD --karpathy
+/rihal-code-review 01
+/rihal-code-review 02.1 --depth=deep
+/rihal-code-review 03 --files=src/auth.js,src/db.js
+/rihal-code-review HEAD~5..HEAD --karpathy
 ```
 
 ## Step 0a — Karpathy mode delegation
@@ -84,7 +84,7 @@ fi
 **Phase validation (before config gate):**
 If `phase_found` is false, report error and exit:
 ```
-Error: Phase ${PHASE_ARG} not found. Run /rihal:status to see available phases.
+Error: Phase ${PHASE_ARG} not found. Run /rihal-status to see available phases.
 ```
 
 This runs BEFORE config gate check so user errors are surfaced immediately regardless of config state.
@@ -261,7 +261,7 @@ if [ ${#REVIEW_FILES[@]} -eq 0 ]; then
   else
     # Fail closed — no reliable diff base found. Do not use arbitrary HEAD~N.
     echo "Warning: No phase commits found for '${PADDED_PHASE}'. Cannot determine reliable diff scope."
-    echo "Use --files flag to specify files explicitly: /rihal:code-review ${PHASE_ARG} --files=file1,file2,..."
+    echo "Use --files flag to specify files explicitly: /rihal-code-review ${PHASE_ARG} --files=file1,file2,..."
   fi
 fi
 ```
@@ -406,7 +406,7 @@ If the Task() call fails (agent error, timeout, or exception):
 ```
 Error: Code review agent failed: ${error_message}
 
-No REVIEW.md created. You can retry with /rihal:code-review ${PHASE_ARG} or check agent logs.
+No REVIEW.md created. You can retry with /rihal-code-review ${PHASE_ARG} or check agent logs.
 ```
 
 Do NOT proceed to commit_review step. Do NOT create a partial or empty REVIEW.md. Exit workflow.
@@ -479,7 +479,7 @@ if [ -f "${REVIEW_PATH}" ]; then
   fi
 else
   echo "Warning: Agent completed but REVIEW.md not found at ${REVIEW_PATH}. This may indicate an agent issue."
-  echo "No REVIEW.md to commit. Please retry with /rihal:code-review ${PHASE_ARG}"
+  echo "No REVIEW.md to commit. Please retry with /rihal-code-review ${PHASE_ARG}"
 fi
 ```
 </step>
@@ -538,7 +538,7 @@ If total findings > 0:
 Full report: ${REVIEW_PATH}
 
 Next steps:
-  /rihal:code-review-fix ${PHASE_NUMBER}  — Auto-fix issues
+  /rihal-code-review-fix ${PHASE_NUMBER}  — Auto-fix issues
   cat ${REVIEW_PATH}                       — View full report
 ```
 

package/rihal/workflows/complete-milestone.md

@@ -99,7 +99,7 @@ Requirements: {N}/{M} v1 requirements checked off
 
 MUST present 3 options via AskUserQuestion:
 1. **Proceed anyway** — mark milestone complete with known gaps
-2. **Run audit first** — `/rihal:audit-milestone` to assess gap severity
+2. **Run audit first** — `/rihal-audit-milestone` to assess gap severity
 3. **Abort** — return to development
 
 If user selects "Proceed anyway": note incomplete requirements in MILESTONES.md under `### Known Gaps` with REQ-IDs and descriptions.
@@ -427,7 +427,7 @@ find .planning/phases -mindepth 1 -maxdepth 1 -type d -exec mv {} "$ARCHIVE_DIR/
 
 Verify: `✅ Phase directories archived to .planning/milestones/v[X.Y]-phases/`
 
-If "Skip": Phase directories remain in `.planning/phases/` as raw execution history. Use `/rihal:cleanup` later to archive retroactively.
+If "Skip": Phase directories remain in `.planning/phases/` as raw execution history. Use `/rihal-cleanup` later to archive retroactively.
 
 </step>
 
@@ -483,7 +483,7 @@ After archival, reorganize ROADMAP.md with milestone groupings, then delete orig
 rm .planning/REQUIREMENTS.md
 ```
 
-(ROADMAP.md is retained in its reorganized form. Do NOT delete it — deletion is reserved for between-milestone resets via `/rihal:new-milestone`.)
+(ROADMAP.md is retained in its reorganized form. Do NOT delete it — deletion is reserved for between-milestone resets via `/rihal-new-milestone`.)
 
 </step>
 
@@ -780,7 +780,7 @@ Confirm: "Committed: chore: complete v[X.Y] milestone" (or the gitignored notice
 
 `/clear` then:
 
-`/rihal:new-milestone`
+`/rihal-new-milestone`
 
 ---
 ```
@@ -830,7 +830,7 @@ Milestone completion is successful when:
 - [ ] Known gaps recorded in MILESTONES.md if user proceeded with incomplete requirements
 - [ ] RETROSPECTIVE.md updated with milestone section
 - [ ] Cross-milestone trends updated
-- [ ] User knows next step (/rihal:new-milestone)
+- [ ] User knows next step (/rihal-new-milestone)
 
 </success_criteria>
 </output>

package/rihal/workflows/correct-course.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:correct-course
+# Workflow: rihal-correct-course
 
 <purpose>
 Load original PRD and architecture docs, compare against current codebase implementation. Identify deviations, classify by type (scope drift, wrong architecture, missing acceptance criteria, tech debt), and produce ordered remediation plan with updated story file.
@@ -10,13 +10,13 @@ Load original PRD and architecture docs, compare against current codebase implem
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:correct-course <argument-here>
+/rihal-correct-course <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:correct-course example 1
-/rihal:correct-course example 2
+/rihal-correct-course example 1
+/rihal-correct-course example 2
 ```
 
 STOP — do not proceed.
@@ -126,7 +126,7 @@ Task tool call:
     - Rollback risk
     - Acceptance criteria for "fixed"
     
-    Output: SPRINT.md that can be executed with /rihal:execute
+    Output: SPRINT.md that can be executed with /rihal-execute
 ```
 
 ## Step 4 — Generate Report and Plan
@@ -155,7 +155,7 @@ Add section to story file:
 ### Tech Debt
 - {list}
 
-Remediation: See /rihal:correct-course for ordered fix plan
+Remediation: See /rihal-correct-course for ordered fix plan
 ```
 
 Print:
@@ -173,7 +173,7 @@ Reports:
   • Remediation plan: {remediation_plan_path}
 
 Run remediation with:
-/rihal:execute {remediation_plan_path}
+/rihal-execute {remediation_plan_path}
 ```
 
 ## Success Criteria

package/rihal/workflows/council.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:council
+# Workflow: rihal-council
 
 <purpose>
 Orchestrate a parallel panel of Rihal specialist subagents answering a strategic question. This is the v2 council — deterministic panel scoring via `rihal-tools.cjs`, parallel Task-tool spawning (not sequential roleplay), and structured artifact output to `.planning/council-sessions/`.
@@ -39,7 +39,7 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:council <question> [--full] [--verbose] [--agents=a,b,c] [--explain] [--resume <session-path>]
+/rihal-council <question> [--full] [--verbose] [--agents=a,b,c] [--explain] [--resume <session-path>]
 ```
 
 **Flag semantics:**
@@ -49,12 +49,12 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Examples:**
 ```
-/rihal:council should I start a new project or continue this one?
-/rihal:council --agents=sadiq,waleed,fatima is this plan ready to ship?
-/rihal:council --explain what stack should I use for a multi-tenant SaaS?
-/rihal:council --full should we rewrite the auth layer?
-/rihal:council --verbose --debate deep-dive the TTFT tradeoffs
-/rihal:council --resume .planning/council-sessions/council-2026-04-12-should-i-start.md
+/rihal-council should I start a new project or continue this one?
+/rihal-council --agents=sadiq,waleed,fatima is this plan ready to ship?
+/rihal-council --explain what stack should I use for a multi-tenant SaaS?
+/rihal-council --full should we rewrite the auth layer?
+/rihal-council --verbose --debate deep-dive the TTFT tradeoffs
+/rihal-council --resume .planning/council-sessions/council-2026-04-12-should-i-start.md
 ```
 
 **With --resume:** continue a prior council session with a new question. The prior session context is surfaced to the panel.
@@ -77,11 +77,11 @@ Proceed to Step 1 with the prior session context pre-loaded.
 If `$ARGUMENTS` starts with an agent name (sadiq/waleed/fatima/mariam/hussain-pm) and looks like a question directed at one person (e.g., "ask waleed about X", "what does fatima think"):
 
 ```
-⚠ That looks like a single-agent question — /rihal:discuss is faster.
+⚠ That looks like a single-agent question — /rihal-discuss is faster.
 
 Council spawns 3-5 agents in parallel for debate. For one expert, use:
 
-/rihal:discuss $ARGUMENTS
+/rihal-discuss $ARGUMENTS
 ```
 
 Only proceed past this step if the input is a true multi-perspective question (e.g., "should we...?", "is X a good idea?", "which approach is best?").
@@ -131,11 +131,11 @@ Print warning and use AskUserQuestion to confirm:
 ⚠ This appears to be a fresh project with no context.
 Council answers may be generic without project-specific signal.
 
-Run /rihal:init first for richer context, or proceed anyway?
+Run /rihal-init first for richer context, or proceed anyway?
 ```
 
 Options:
-- "Run /rihal:init first" → Print: `Copy-paste this: /rihal:init` and STOP
+- "Run /rihal-init first" → Print: `Copy-paste this: /rihal-init` and STOP
 - "Proceed anyway" → Continue to Step 2
 
 ## Step 1 — Initialize
@@ -456,7 +456,7 @@ AskUserQuestion:
     - label: "Both — in parallel tracks"
       description: "{only offer if feasible}"
     - label: "Discuss further with {agent-name}"
-      description: "Route to /rihal:discuss for a deeper 1:1"
+      description: "Route to /rihal-discuss for a deeper 1:1"
 ```
 
 After the user picks, emit a one-line decision record and proceed to
@@ -520,7 +520,7 @@ Format each as a checkbox:}
 
 The `{slug}` is a lowercase-hyphenated slug of the first 6 words of the question. Create `{paths.sessions_dir}` if it doesn't exist (`mkdir -p`).
 
-**Follow-ups must NOT be empty.** Every council session produces at least one actionable item. If panelists only asked clarifying questions, the follow-up is "Answer the panel's clarifying questions and re-run /rihal:council".
+**Follow-ups must NOT be empty.** Every council session produces at least one actionable item. If panelists only asked clarifying questions, the follow-up is "Answer the panel's clarifying questions and re-run /rihal-council".
 
 Print the artifact path to the user at the end:
 
@@ -557,7 +557,7 @@ node .rihal/bin/rihal-tools.cjs state record-session
 ## On Error
 
 - **Empty arguments or --help:** print usage block (Step 0), stop.
-- **Single-agent question detected:** redirect to `/rihal:discuss` (Step 0.5).
+- **Single-agent question detected:** redirect to `/rihal-discuss` (Step 0.5).
 - **`rihal-tools.cjs` not found:** user has v1 installed or package broken. Tell user to run `npx @hanzlaa/rcode install` (or `rcode install` if installed globally).
 - **Panel contains unknown agent:** print the installed-agent list and exit.
 - **state.json missing or corrupted:** continue without error — session artifact is mandatory, state tracking is optional.

package/rihal/workflows/create-epics-and-stories.md

@@ -1,7 +1,7 @@
-# Workflow: rihal:create-epics-and-stories
+# Workflow: rihal-create-epics-and-stories
 
 <purpose>
-Parse a PRD, PROJECT.md, or project document to generate numbered epic files in `.planning/epics/`. Each epic file contains user stories with acceptance criteria, development notes, and effort estimates. Output is ready for `/rihal:sprint-planning`.
+Parse a PRD, PROJECT.md, or project document to generate numbered epic files in `.planning/epics/`. Each epic file contains user stories with acceptance criteria, development notes, and effort estimates. Output is ready for `/rihal-sprint-planning`.
 </purpose>
 
 
@@ -38,7 +38,7 @@ done
 ```
 No PRD or PROJECT.md found. How should we proceed?
 
-1. Initialize the project first — run /rihal:new-project to capture goals, stack, 
+1. Initialize the project first — run /rihal-new-project to capture goals, stack, 
    milestones, and generate PROJECT.md. Recommended if this is a new project.
 
 2. Gather context from codebase + GitHub issues — I'll scan the repo, read open 
@@ -48,7 +48,7 @@ No PRD or PROJECT.md found. How should we proceed?
    generate stories from that description directly.
 ```
 
-- If **1**: invoke `/rihal:new-project` and stop.
+- If **1**: invoke `/rihal-new-project` and stop.
 - If **2**: set `CONTEXT_MODE=codebase`
 - If **3**: capture description → set `CONTEXT_MODE=interactive`, `DESCRIPTION=$response`
 
@@ -234,7 +234,7 @@ If any story fails, ask roadmapper to fix before continuing.
     2.1.md
 ```
 
-**Why split:** Epic files are kept lean so GitHub API updates only rewrite one small story file instead of the full epic. Token cost per `/rihal:dev-story` is proportional to one story, not the whole epic.
+**Why split:** Epic files are kept lean so GitHub API updates only rewrite one small story file instead of the full epic. Token cost per `/rihal-dev-story` is proportional to one story, not the whole epic.
 
 ```bash
 mkdir -p .planning/epics/stories
@@ -294,7 +294,7 @@ As a {persona}, I want to {action} so that {outcome}.
 {Exact file paths, function names, line-level hints}
 
 ---
-*Start: `/rihal:dev-story {N}.{M}`*
+*Start: `/rihal-dev-story {N}.{M}`*
 ```
 
 ## Step 5 — Write INDEX.md
@@ -325,7 +325,7 @@ Generated: {ISO date} | Source: {input filename}
 
 ---
 *Update story status: edit `.planning/epics/stories/{N}.{M}.md` → change `Status:` line*
-*Next: `/rihal:sprint-planning` or `/rihal:dev-story {N}.{M}`*
+*Next: `/rihal-sprint-planning` or `/rihal-dev-story {N}.{M}`*
 ```
 
 ## Step 6 — Commit
@@ -346,8 +346,8 @@ Index:   .planning/epics/INDEX.md
 Effort:  ~{weeks} total
 
 Next:
-  /rihal:sprint-planning          organise into sprints
-  /rihal:dev-story {N}.{M}        start working on a story
+  /rihal-sprint-planning          organise into sprints
+  /rihal-dev-story {N}.{M}        start working on a story
 ```
 
 ## Errors

package/rihal/workflows/create-story.md

@@ -1,7 +1,7 @@
-# Workflow: rihal:create-story
+# Workflow: rihal-create-story
 
 <purpose>
-Convert a single story from an EPIC file into a self-contained STORY.md file. This story is ready for `/rihal:dev-story` to be wrapped for AI-coder execution. Entry is gated by checklist-story-draft.md.
+Convert a single story from an EPIC file into a self-contained STORY.md file. This story is ready for `/rihal-dev-story` to be wrapped for AI-coder execution. Entry is gated by checklist-story-draft.md.
 </purpose>
 
 
@@ -10,13 +10,13 @@ Convert a single story from an EPIC file into a self-contained STORY.md file. Th
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:create-story <argument-here>
+/rihal-create-story <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:create-story example 1
-/rihal:create-story example 2
+/rihal-create-story example 1
+/rihal-create-story example 2
 ```
 
 STOP — do not proceed.
@@ -26,11 +26,11 @@ STOP — do not proceed.
 **If no arguments:**
 
 ```
-Usage: /rihal:create-story <EPIC-file.md> [--story <id>]
+Usage: /rihal-create-story <EPIC-file.md> [--story <id>]
 
 Examples:
-  /rihal:create-story .planning/epics/EPIC-01.md
-  /rihal:create-story .planning/epics/EPIC-01.md --story EPIC-01.1
+  /rihal-create-story .planning/epics/EPIC-01.md
+  /rihal-create-story .planning/epics/EPIC-01.md --story EPIC-01.1
 ```
 
 Stop and wait for arguments.
@@ -243,7 +243,7 @@ Use checklist-story-dod.md. A story is "Done" when:
 
 **Before you start:** Review this story, dev notes, and dependencies.
 
-**During development:** See `/rihal:dev-story` to wrap this STORY.md for AI-coder execution.
+**During development:** See `/rihal-dev-story` to wrap this STORY.md for AI-coder execution.
 
 **After complete:** Run checklist-story-dod.md to verify done.
 
@@ -251,7 +251,7 @@ Use checklist-story-dod.md. A story is "Done" when:
 
 **Created:** {ISO date}
 
-**Ready for:** /rihal:dev-story → /rihal:code → Definition of Done verification
+**Ready for:** /rihal-dev-story → /rihal-code → Definition of Done verification
 ```
 
 ## Step 6 — Commit Story File
@@ -272,7 +272,7 @@ Title: {Story title}
 Effort: {Estimate}
 Persona: {Persona}
 
-Next step: /rihal:dev-story .planning/stories/{story-id}.md
+Next step: /rihal-dev-story .planning/stories/{story-id}.md
 ```
 
 ## Errors

package/rihal/workflows/dashboard.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:dashboard
+# Workflow: rihal-dashboard
 
 <purpose>
 Start the Diwan view-only dashboard — a local web UI that visualizes .rihal/state.json, .planning/ artifacts, phases, decisions, and council sessions. The dashboard is read-only (no write endpoints) and runs dep-free on Node stdlib.
@@ -9,14 +9,14 @@ Start the Diwan view-only dashboard — a local web UI that visualizes .rihal/st
 If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
-/rihal:dashboard [--port <N>] [--no-open]
+/rihal-dashboard [--port <N>] [--no-open]
 ```
 
 **Examples:**
 ```
-/rihal:dashboard                  # start on port 7717, open browser
-/rihal:dashboard --port 8080      # use a different port
-/rihal:dashboard --no-open        # don't auto-open the browser
+/rihal-dashboard                  # start on port 7717, open browser
+/rihal-dashboard --port 8080      # use a different port
+/rihal-dashboard --no-open        # don't auto-open the browser
 ```
 
 STOP — do not proceed.
@@ -121,13 +121,13 @@ The server runs until the user kills it. The slash command returns after announc
 ## Examples
 
 ### Happy Path
-**Input:** `/rihal:dashboard`
+**Input:** `/rihal-dashboard`
 **Expected:** Server starts on 7717, browser opens, confirmation printed.
 
 ### Edge Case: Port in use
-**Input:** `/rihal:dashboard` (when 7717 is taken)
+**Input:** `/rihal-dashboard` (when 7717 is taken)
 **Expected:** Server reports EADDRINUSE. Suggest `--port` flag with alternative.
 
 ### Negative Test
-**Input:** `/rihal:dashboard --write something`
+**Input:** `/rihal-dashboard --write something`
 **Expected:** Dashboard is view-only. Reject unknown write-related flags.

package/rihal/workflows/debug.md

@@ -12,13 +12,13 @@ Orchestrator stays lean: parse issues, spawn agents, collect results, synthesize
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:debug <argument-here>
+/rihal-debug <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:debug example 1
-/rihal:debug example 2
+/rihal-debug example 1
+/rihal-debug example 2
 ```
 
 STOP — do not proceed.
@@ -48,10 +48,10 @@ With diagnosis: "Feature doesn't work" → "missing error handler" → precise f
 If input contains "should we", "what is the best way to", "how do I implement" — these are not bugs, they are how-to or strategy questions.
 
 ```
-⚠ /rihal:debug investigates broken behavior, not how-to questions.
+⚠ /rihal-debug investigates broken behavior, not how-to questions.
 
-For implementation guidance: /rihal:discuss waleed $ARGUMENTS
-For a strategic decision: /rihal:council $ARGUMENTS
+For implementation guidance: /rihal-discuss waleed $ARGUMENTS
+For a strategic decision: /rihal-council $ARGUMENTS
 ```
 
 Only proceed past this step if the input describes broken or unexpected behavior (e.g., "error X occurs", "feature Y doesn't work", "API returns wrong data").

package/rihal/workflows/decisions.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:decisions
+# Workflow: rihal-decisions
 
 <purpose>
 Surface recent decisions across every Rihal project on this machine. Decisions are mirrored to `~/.rihal/decisions.jsonl` whenever a project runs `state add-decision`. Use this to see what was decided elsewhere, find precedent for a similar call you are about to make, or answer "what did I commit to last week?".
@@ -26,7 +26,7 @@ Newest decisions first. One row per decision with project, date, phase, and summ
 If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
-/rihal:decisions [--limit N] [--project <name>] [--since <ISO-date>] [--this-project]
+/rihal-decisions [--limit N] [--project <name>] [--since <ISO-date>] [--this-project]
 
   --limit N         Max rows to show (default 20, max 500)
   --project <name>  Filter to one project name (as recorded in state.project)
@@ -61,7 +61,7 @@ The result is JSON: `{decisions: [...], total: N}`. If `decisions` is empty:
 ```
 No decisions logged yet.
 
-Decisions are mirrored to ~/.rihal/decisions.jsonl whenever /rihal:execute or /rihal:council records one. Run a council or complete a sprint to populate this log.
+Decisions are mirrored to ~/.rihal/decisions.jsonl whenever /rihal-execute or /rihal-council records one. Run a council or complete a sprint to populate this log.
 ```
 
 STOP.
@@ -90,8 +90,8 @@ Where filter suffix is, for example: ` · project=rihal-code · since=2026-01-01
 
 ## Step 5 — Next Up routing
 
-- If `--this-project` was used and results look thin (fewer than 3) → `Next: /rihal:council "<open question>"  (then decisions flow back here)`
-- Otherwise → `Next: /rihal:decisions --project <name>  for deeper history on one project`
+- If `--this-project` was used and results look thin (fewer than 3) → `Next: /rihal-council "<open question>"  (then decisions flow back here)`
+- Otherwise → `Next: /rihal-decisions --project <name>  for deeper history on one project`
 </process>
 
 ## Success Criteria

package/rihal/workflows/dev-story.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:dev-story
+# Workflow: rihal-dev-story
 
 <purpose>
 Wrap a STORY.md file for AI-coder consumption. Produces:
@@ -57,14 +57,14 @@ elif [[ "$ARGS" =~ ^[Ee]pic[[:space:]]+([0-9]+)$ ]] || [[ "$ARGS" =~ ^[Ee][Pp][I
   EPIC_FILE=".planning/epics/EPIC-$(printf '%02d' $EPIC_NUM).md"
 
 else
-  echo "Usage: /rihal:dev-story <epic-ref> [--branch]"
+  echo "Usage: /rihal-dev-story <epic-ref> [--branch]"
   echo ""
   echo "Examples:"
-  echo "  /rihal:dev-story epic 1             # list stories in EPIC-01"
-  echo "  /rihal:dev-story epic 1 story 3     # work on EPIC-01, story 3"
-  echo "  /rihal:dev-story EPIC-01.3          # same as above"
-  echo "  /rihal:dev-story 1.3 --branch       # with new git branch"
-  echo "  /rihal:dev-story .planning/epics/stories/1.3.md  # direct path"
+  echo "  /rihal-dev-story epic 1             # list stories in EPIC-01"
+  echo "  /rihal-dev-story epic 1 story 3     # work on EPIC-01, story 3"
+  echo "  /rihal-dev-story EPIC-01.3          # same as above"
+  echo "  /rihal-dev-story 1.3 --branch       # with new git branch"
+  echo "  /rihal-dev-story .planning/epics/stories/1.3.md  # direct path"
   echo ""
   echo "Story files live in: .planning/epics/stories/"
   STOP
@@ -89,7 +89,7 @@ if [[ -z "$STORY_NUMBER" ]]; then
   AVAILABLE=$(ls .planning/epics/stories/${EPIC_NUM}.*.md 2>/dev/null)
   if [[ -z "$AVAILABLE" ]]; then
     echo "Error: No stories found for Epic ${EPIC_NUM} in .planning/epics/stories/"
-    echo "Run /rihal:create-epics-and-stories first."
+    echo "Run /rihal-create-epics-and-stories first."
     STOP
   fi
   echo "Stories in Epic ${EPIC_NUM}:"
@@ -334,7 +334,7 @@ This story is "Done" when all items in checklist-story-dod.md are checked:
 To execute with an AI coder:
 
 ```bash
-/rihal:code .planning/dev-sessions/{story-id}-dev-prompt.md
+/rihal-code .planning/dev-sessions/{story-id}-dev-prompt.md
 ```
 
 ---
@@ -383,7 +383,7 @@ Acceptance Criteria: {count}
 
 Context file: {path to dev-prompt.md}
 
-Next: /rihal:code {path to dev-prompt.md}
+Next: /rihal-code {path to dev-prompt.md}
 
 Or, continue the current session to:
   - Ask clarifying questions
@@ -397,7 +397,7 @@ If user says "start coding" or "let's build", spawn the code execution workflow:
 
 ```bash
 # User says "let's go" or "start", then:
-/rihal:code "$DEV_PROMPT_FILE"
+/rihal-code "$DEV_PROMPT_FILE"
 ```
 
 Otherwise, offer:
@@ -405,7 +405,7 @@ Otherwise, offer:
 ```
 Ready to code this story?
 
-/rihal:code {dev-prompt-file}
+/rihal-code {dev-prompt-file}
 ```
 
 Stop and wait for user to proceed. Do NOT auto-spawn.

package/rihal/workflows/diagnose-issues.md

@@ -1,7 +1,7 @@
-# Workflow: rihal:diagnose-issues
+# Workflow: rihal-diagnose-issues
 
 <purpose>
-Reusable diagnosis subroutine called from /rihal:verify-work when
+Reusable diagnosis subroutine called from /rihal-verify-work when
 verification fails. Walks symptom → hypothesis → evidence → minimal
 repro and returns a structured finding. Not a top-level command.
 </purpose>

package/rihal/workflows/diff.md

@@ -13,9 +13,9 @@ If invalid args: Show usage
 
 ```
 Usage:
-  /rihal:diff              # Diff HEAD~1 to HEAD
-  /rihal:diff --last       # Diff against last session
-  /rihal:diff abc123 def456  # Diff between commits
+  /rihal-diff              # Diff HEAD~1 to HEAD
+  /rihal-diff --last       # Diff against last session
+  /rihal-diff abc123 def456  # Diff between commits
 ```
 
 ## Step 1: Parse Arguments