@hanzlaa/rcode 3.3.0 → 3.3.1

package/rihal/skills/actions/2-plan/rihal-create-milestone/steps/step-07-backlog.md

@@ -4,7 +4,7 @@
 
 ## STEP GOAL
 
-Capture everything that is **not** in M1..Mn but was considered. Use Rihal's `999.x` parking-lot convention so items can be promoted later via `/rihal:plant-seed` or `/rihal:review-backlog`.
+Capture everything that is **not** in M1..Mn but was considered. Use Rihal's `999.x` parking-lot convention so items can be promoted later via `/rihal-plant-seed` or `/rihal-review-backlog`.
 
 ## MANDATORY RULES
 
@@ -24,7 +24,7 @@ Sources:
 ### 2. Number using 999.x convention
 
 ```
-Backlog (999.x — promotable with /rihal:plant-seed):
+Backlog (999.x — promotable with /rihal-plant-seed):
 
   999.1  Cross-post to LinkedIn          — deferred: requires LinkedIn OAuth (M2+)
   999.2  Auto-DM feature                 — deferred: abuse risk, needs rate-limit design

package/rihal/skills/actions/2-plan/rihal-create-milestone/steps/step-09-state-sync.md

@@ -8,7 +8,7 @@ Call the state-sync CLI so `.rihal/state.json` reflects every milestone and phas
 
 ## MANDATORY RULES
 
-- 🛑 This step MUST run. Skipping it leaves `/rihal:status` and `/rihal:progress` showing stale data.
+- 🛑 This step MUST run. Skipping it leaves `/rihal-status` and `/rihal-progress` showing stale data.
 - 🛑 Report the sync result (pulled phases, existing phases updated, any errors) to the user.
 
 ## SEQUENCE
@@ -43,7 +43,7 @@ State sync complete:
   Milestones:       3
   Phases:          10
   Phases upserted: 10 (new)
-  Epics:            0 (none yet — run /rihal:create-epics-and-stories next)
+  Epics:            0 (none yet — run /rihal-create-epics-and-stories next)
 ```
 
 ### 3. Verify drift closed

package/rihal/skills/actions/2-plan/rihal-create-milestone/steps/step-10-complete.md

@@ -39,16 +39,16 @@ Hard deadline:  {deadline or "none specified"}
 What's next?
 
   [A] Decompose M1 into epics + stories
-      → /rihal:create-epics-and-stories
+      → /rihal-create-epics-and-stories
 
   [B] Plan the first phase in detail
-      → /rihal:plan-phase 01
+      → /rihal-plan-phase 01
 
   [C] Review the roadmap with the team
-      → /rihal:council "Is this roadmap realistic?"
+      → /rihal-council "Is this roadmap realistic?"
 
   [D] Park and review later
-      → Roadmap is saved; pick up with /rihal:progress anytime
+      → Roadmap is saved; pick up with /rihal-progress anytime
 ```
 
 ### 4. HALT

package/rihal/skills/actions/2-plan/rihal-create-milestone/workflow.md

@@ -33,7 +33,7 @@ This uses **step-file architecture** for disciplined execution:
 - 💾 **ALWAYS** update frontmatter of output files when writing
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - 📋 **NEVER** create mental todo lists from future steps
-- 🚷 **NEVER** invent an "autonomous mode" or self-declared bypass. The only sanctioned paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`. See `../../_shared/no-autonomous-bypass.md`.
+- 🚷 **NEVER** invent an "autonomous mode" or self-declared bypass. The only sanctioned paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`. See `../../_shared/no-autonomous-bypass.md`.
 - 🔗 **NEVER** cite external sources without `WebFetch`. See `../../_shared/research-citation-rule.md`.
 - 🗂️ **ALWAYS** sync every milestone/phase into `.rihal/state.json` after writing to ROADMAP.md. See `../../_shared/state-sync-rule.md`.
 
@@ -56,7 +56,7 @@ Load and read full config from `{main_config}` and resolve:
 
 Verify `{inputFile}` (PRD) exists and is non-empty. If missing:
 
-- Respond: *"I need an approved PRD first. Run `/rihal:create-prd` or point me at the existing brief."*
+- Respond: *"I need an approved PRD first. Run `/rihal-create-prd` or point me at the existing brief."*
 - HALT. Do not create ROADMAP.md.
 
 If PRD frontmatter shows `status: draft`, warn the user and ask whether to proceed.
@@ -80,7 +80,7 @@ Steps (loaded one at a time):
 7. `step-07-backlog.md` — Capture parking-lot items.
 8. `step-08-write-roadmap.md` — Append all milestones to ROADMAP.md.
 9. `step-09-state-sync.md` — Upsert milestones + phases into `.rihal/state.json`.
-10. `step-10-complete.md` — Summary, next-step hand-off (`/rihal:create-epics-and-stories` for M1).
+10. `step-10-complete.md` — Summary, next-step hand-off (`/rihal-create-epics-and-stories` for M1).
 
 Each step halts at a menu: [A]ccept / [P]ropose change / [C]ontinue. Only on `C` does the workflow advance.
 
@@ -89,5 +89,5 @@ Each step halts at a menu: [A]ccept / [P]ropose change / [C]ontinue. Only on `C`
 ## HAND-OFF
 
 On completion, recommend the user run:
-- `/rihal:create-epics-and-stories` to decompose M1 into epics + stories.
-- `/rihal:sprint-planning` once the first epic is scoped.
+- `/rihal-create-epics-and-stories` to decompose M1 into epics + stories.
+- `/rihal-sprint-planning` once the first epic is scoped.

package/rihal/skills/actions/2-plan/rihal-create-prd/SKILL.md

@@ -63,4 +63,4 @@ When fast-pathing: confirm detected fields in one line ("Got it — building {na
 
 ### Negative Example: Request to Bypass the Interview
 **Input:** "use research skills and create the best PRD ready to execute" / "skip the questions and write it autonomously" / "just generate the full PRD"
-**Expected behavior:** DO NOT invent an "autonomous mode". DO NOT generate a PRD without running discovery. Respond: "The discovery interview is mandatory unless `.rihal/config.yaml` has `mode: yolo` or you re-invoke via `/rihal:do --auto`. Here is the step-01 menu — I will drive each step concisely." Then present the step-01 menu. See `../../_shared/no-autonomous-bypass.md`.
+**Expected behavior:** DO NOT invent an "autonomous mode". DO NOT generate a PRD without running discovery. Respond: "The discovery interview is mandatory unless `.rihal/config.yaml` has `mode: yolo` or you re-invoke via `/rihal-do --auto`. Here is the step-01 menu — I will drive each step concisely." Then present the step-01 menu. See `../../_shared/no-autonomous-bypass.md`.

package/rihal/skills/actions/2-plan/rihal-create-prd/workflow.md

@@ -41,7 +41,7 @@ This uses **step-file architecture** for disciplined execution:
 - 🎯 **ALWAYS** follow the exact instructions in the step file
 - ⏸️ **ALWAYS** halt at menus and wait for user input
 - 📋 **NEVER** create mental todo lists from future steps
-- 🚷 **NEVER** invent an "autonomous mode", "research mode", or any self-declared bypass. The only sanctioned bypass paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`. See `../../_shared/no-autonomous-bypass.md` for the full rule and correct response pattern.
+- 🚷 **NEVER** invent an "autonomous mode", "research mode", or any self-declared bypass. The only sanctioned bypass paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`. See `../../_shared/no-autonomous-bypass.md` for the full rule and correct response pattern.
 - 🔗 **NEVER** cite an external source (competitor pricing, API limits, market numbers) without first `WebFetch`ing it in the same session. `WebSearch` snippets are not sufficient evidence. See `../../_shared/research-citation-rule.md`.
 
 ## INITIALIZATION SEQUENCE

package/rihal/skills/actions/2-plan/rihal-create-story/workflow.md

@@ -371,7 +371,7 @@ Load config from `{project-root}/.rihal/config.json` and resolve:
     1. Review the comprehensive story in {{story_file}}
     2. Run dev agents `dev-story` for optimized implementation
     3. Run `code-review` when complete (auto-marks done)
-    4. Optional: If Test Architect module installed, run `/rihal:tea:automate` after `dev-story` to generate guardrail tests
+    4. Optional: If Test Architect module installed, run `/rihal-tea:automate` after `dev-story` to generate guardrail tests
 
     **The developer now has everything needed for flawless implementation!**
   </output>

package/rihal/skills/actions/4-implementation/rihal-checkpoint-preview/SKILL.md

@@ -11,9 +11,9 @@ Checkpoint preview skill for Rihal Code.
 
 ## Do NOT use this skill for
 
-- **Automated code review without a human** — use `/rihal:code-review --karpathy` or a code-reviewer agent directly.
+- **Automated code review without a human** — use `/rihal-code-review --karpathy` or a code-reviewer agent directly.
 - **Approving a deploy or merge** — this skill explains a change; it does not authorize git push, deploys, or PR merges.
-- **Bug investigation** from scratch — use `/rihal:debug` or the diagnose-issues workflow.
+- **Bug investigation** from scratch — use `/rihal-debug` or the diagnose-issues workflow.
 - **Architecture review of an undelivered design** — this skill reviews delivered code/diffs, not specs.
 - **Sprint retros or milestone closure** — use `rihal-retrospective` or `rihal-complete-milestone`.
 
@@ -57,7 +57,7 @@ Read fully and follow `./step-01-orientation.md` to begin.
 ## Examples
 
 ### Happy Path
-**Input:** `/rihal:checkpoint-preview` after a feature branch is complete
+**Input:** `/rihal-checkpoint-preview` after a feature branch is complete
 **Expected:** 5-step human review session with clear focus on what matters, testing recommendations, wrapup decision.
 
 ### Edge Case: No changes to review

package/rihal/skills/actions/4-implementation/rihal-dev-story/workflow.md

@@ -437,7 +437,7 @@ Load config from `{project-root}/.rihal/config.json` and resolve:
       - Verify all acceptance criteria are met
       - Ensure deployment readiness if applicable
       - Run `code-review` workflow for peer review
-      - Optional: If Test Architect module installed, run `/rihal:tea:automate` to expand guardrail tests
+      - Optional: If Test Architect module installed, run `/rihal-tea:automate` to expand guardrail tests
     </action>
 
     <output>💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story.</output>

package/rihal/skills/actions/4-implementation/rihal-sprint-planning/SKILL.md

@@ -45,4 +45,4 @@ Follow the instructions in ./workflow.md.
 
 ### Negative Example: Fabricated Capacity
 **Input:** "Plan the sprint" (no prior capacity info, no `mode: yolo`, no `--auto`)
-**Expected behavior:** DO NOT assume "1 senior FT, 30 pts/week" or any other capacity. DO NOT write `sprint-N.md` until the user provides numeric answers for devs/PTO/velocity. If the user resists, point them at the two sanctioned bypass paths (`.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`). See `../../_shared/no-autonomous-bypass.md`.
+**Expected behavior:** DO NOT assume "1 senior FT, 30 pts/week" or any other capacity. DO NOT write `sprint-N.md` until the user provides numeric answers for devs/PTO/velocity. If the user resists, point them at the two sanctioned bypass paths (`.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`). See `../../_shared/no-autonomous-bypass.md`.

package/rihal/skills/actions/4-implementation/rihal-sprint-planning/checklist.md

@@ -8,7 +8,7 @@
 - [ ] Velocity is either (a) provided by the user, or (b) pulled from prior sprint retrospective
 - [ ] 20% buffer is applied to the resulting capacity
 
-If any of the above is missing and the session is NOT running with `.rihal/config.yaml` `mode: yolo` or `/rihal:do --auto`, the workflow MUST halt and ask the user — never fabricate numbers.
+If any of the above is missing and the session is NOT running with `.rihal/config.yaml` `mode: yolo` or `/rihal-do --auto`, the workflow MUST halt and ask the user — never fabricate numbers.
 
 ## Core Validation
 

package/rihal/skills/actions/4-implementation/rihal-sprint-planning/workflow.md

@@ -10,7 +10,7 @@
 
 - ⏸️ **ALWAYS** halt for capacity input (devs, PTO, meetings, velocity) before committing stories to the sprint. Per `SKILL.md` Edge Cases, the skill must ask: *"How many devs, any PTO, any known meetings? I need capacity numbers before committing to stories."*
 - 🚫 **NEVER** fabricate capacity numbers (e.g. *"1 senior FT, 30 pts/week"*) when the user has not provided them.
-- 🚷 **NEVER** invent an "autonomous mode" or any self-declared bypass. The only sanctioned bypass paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`. See `../../_shared/no-autonomous-bypass.md` for the full rule and correct response pattern.
+- 🚷 **NEVER** invent an "autonomous mode" or any self-declared bypass. The only sanctioned bypass paths are `.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`. See `../../_shared/no-autonomous-bypass.md` for the full rule and correct response pattern.
 
 ---
 

package/rihal/skills/actions/4-implementation/rihal-sprint-status/workflow.md

@@ -59,7 +59,7 @@ Load config from `{project-root}/.rihal/config.json` and resolve:
   <action>Try {sprint_status_file}</action>
   <check if="file not found">
     <output>❌ sprint-status.yaml not found.
-Run `/rihal:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
+Run `/rihal-workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
     <action>Exit workflow</action>
   </check>
   <action>Continue to Step 2</action>
@@ -112,9 +112,9 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 <action>Detect risks:</action>
 
-- IF any story has status "review": suggest `/rihal:workflows:code-review`
+- IF any story has status "review": suggest `/rihal-workflows:code-review`
 - IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story
-- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/rihal:workflows:create-story`
+- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/rihal-workflows:create-story`
 - IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn "sprint-status.yaml may be stale"
 - IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected"
 - IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories"
@@ -144,7 +144,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 **Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}
 
-**Next Recommendation:** /rihal:workflows:{{next_workflow_id}} ({{next_story_id}})
+**Next Recommendation:** /rihal-workflows:{{next_workflow_id}} ({{next_story_id}})
 
 {{#if risks}}
 **Risks:**
@@ -166,7 +166,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 Choice:</ask>
 
   <check if="choice == 1">
-    <output>Run `/rihal:workflows:{{next_workflow_id}}`.
+    <output>Run `/rihal-workflows:{{next_workflow_id}}`.
 If the command targets a story, set `story_key={{next_story_id}}` when prompted.</output>
   </check>
 

package/rihal/skills/agents/dalil-scout/SKILL.md

@@ -8,8 +8,8 @@ description: >
   "map the codebase", "what's in this repo", "discover X across the
   project", "audit instrumentation", "find all callers of Y", "is there
   any Sentry / GraphQL / Redis usage", "explore the project structure",
-  "talk to Dalil", or "scout this repo". Also activates via /rihal:scan
-  and /rihal:map-codebase. Do NOT use for: plan execution (use executor),
+  "talk to Dalil", or "scout this repo". Also activates via /rihal-scan
+  and /rihal-map-codebase. Do NOT use for: plan execution (use executor),
   strategic decisions (use Sadiq / Waleed), test design (use Fatima), or
   code modification (use Hanzla / Omar).
 triggers:
@@ -39,10 +39,10 @@ First-person, calm, observational. Opens `Dalil here — starting the scan.`. Cl
 
 | Code | Description | Workflow |
 |---|---|---|
-| SC | Lightweight focused scan — one focus area, single document set | `rihal:scan` |
-| MC | Comprehensive 4-area parallel scan | `rihal:map-codebase` |
-| RF | Memory-bank refresh — diff against last scan, update `CHANGELOG.md` | `rihal:scan --refresh` |
-| TS | Topic-phrase sweep across all source roots with grounded file list | `rihal:scan --focus <area> --topic "<phrase>"` |
+| SC | Lightweight focused scan — one focus area, single document set | `rihal-scan` |
+| MC | Comprehensive 4-area parallel scan | `rihal-map-codebase` |
+| RF | Memory-bank refresh — diff against last scan, update `CHANGELOG.md` | `rihal-scan --refresh` |
+| TS | Topic-phrase sweep across all source roots with grounded file list | `rihal-scan --focus <area> --topic "<phrase>"` |
 
 ## Workflow (every invocation)
 
@@ -90,7 +90,7 @@ The `Brief:` line is verbatim-extracted by the orchestrator into `.planning/code
 ## Examples
 
 **Happy path — topic sweep on a polyglot monorepo**
-`/rihal:scan --focus concerns --topic "Sentry instrumentation"` → discover `web/ backend/ ml/ deployments/` → detect Python + TS → topic sweep finds 47 files including `backend/onyx/server/exception_handlers.py` → write `CONCERNS.md` with full Scan Scope → close `— Dalil`.
+`/rihal-scan --focus concerns --topic "Sentry instrumentation"` → discover `web/ backend/ ml/ deployments/` → detect Python + TS → topic sweep finds 47 files including `backend/onyx/server/exception_handlers.py` → write `CONCERNS.md` with full Scan Scope → close `— Dalil`.
 
 **Edge case — topic phrase returns zero matches**
 Re-grep with `-i`. Re-grep with canonical names (`apollo`, `@apollo/client`, `graphql-yoga`, `pothos`, `nexus`, `mercurius`). Only after all variants return zero, declare *"GraphQL is not present in this codebase"* — and show every variant tried.

package/rihal/skills/core/rihal-brainstorming/SKILL.md

@@ -95,7 +95,7 @@ Follow the instructions in ./workflow.md.
 
 ### Negative boundary
 **User:** "brainstorm which tech stack to use"
-**Result:** Redirects to `/rihal:council` or Waleed (CTO) — architecture decisions need structured ADR evaluation, not open ideation.
+**Result:** Redirects to `/rihal-council` or Waleed (CTO) — architecture decisions need structured ADR evaluation, not open ideation.
 
 ## Memory Bank Hooks
 

package/rihal/skills/core/rihal-init/SKILL.md

@@ -124,7 +124,7 @@ JSON config vars returned to the calling skill. When init path runs, interactive
 
 ### Negative boundary
 **User:** "initialize my project"
-**Result:** rihal-init is internal — user should use `rihal-scaffold-project` or `/rihal:install` instead
+**Result:** rihal-init is internal — user should use `rihal-scaffold-project` or `/rihal-install` instead
 
 ## Memory Bank Hooks
 

package/rihal/skills/core/rihal-party-mode/SKILL.md

@@ -88,7 +88,7 @@ Each party mode turn follows this pattern:
 
 ### Negative boundary
 **User:** "party mode — approve this PR"
-**Result:** Redirects to `/rihal:code-review` — code review needs structured evaluation, not open discussion.
+**Result:** Redirects to `/rihal-code-review` — code review needs structured evaluation, not open discussion.
 
 ## Memory Bank Hooks
 

package/rihal/templates/milestone.md

@@ -2,7 +2,7 @@
 
 <!-- P2: Omit any section with nothing substantive. Empty sections are noise. Omit STATE.md blockers/workstreams if none active. Omit REQUIREMENTS.md out-of-scope if it doesn't constrain execution. -->
 
-Use this template when starting a new milestone with `/rihal:new-milestone`.
+Use this template when starting a new milestone with `/rihal-new-milestone`.
 
 ## ROADMAP.md
 

package/rihal/templates/projects/api-backend/PROJECT.md

@@ -34,4 +34,4 @@ A headless API for {{use_case}}. Consumers are other services, internal apps, or
 - Early API shape locks in; expensive to change once consumers integrate
 
 ## Evolution
-_(Updated after each phase completion by `/rihal:execute`.)_
+_(Updated after each phase completion by `/rihal-execute`.)_

package/rihal/templates/projects/mobile-app/PROJECT.md

@@ -34,4 +34,4 @@ _(Describe the repeatable loop — 2-4 steps — that drives retention.)_
 - **Push opt-in rate:** <30% is common; design core loop to work without push
 
 ## Evolution
-_(Updated after each phase completion by `/rihal:execute`.)_
+_(Updated after each phase completion by `/rihal-execute`.)_

package/rihal/templates/projects/saas-b2b/PROJECT.md

@@ -37,4 +37,4 @@ _(Market timing, regulatory shift, technology enabler, etc.)_
 - **Regulatory:** PII/data-residency constraints depending on target market
 
 ## Evolution
-_(Updated after each phase completion by `/rihal:execute`.)_
+_(Updated after each phase completion by `/rihal-execute`.)_

package/rihal/workflows/add-phase.md

@@ -11,15 +11,15 @@ Read all files referenced by the invoking prompt's execution_context before star
 <step name="parse_arguments">
 Parse the command arguments:
 - All arguments become the phase description
-- Example: `/rihal:add-phase Add authentication` → description = "Add authentication"
-- Example: `/rihal:add-phase Fix critical performance issues` → description = "Fix critical performance issues"
+- Example: `/rihal-add-phase Add authentication` → description = "Add authentication"
+- Example: `/rihal-add-phase Fix critical performance issues` → description = "Fix critical performance issues"
 
 If no arguments provided:
 
 ```
 ERROR: Phase description required
-Usage: /rihal:add-phase <description>
-Example: /rihal:add-phase Add authentication system
+Usage: /rihal-add-phase <description>
+Example: /rihal-add-phase Add authentication system
 ```
 
 Exit.
@@ -36,13 +36,13 @@ if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
 Check `roadmap_exists` from init JSON. If false:
 ```
 ERROR: No roadmap found (.planning/ROADMAP.md)
-Run /rihal:new-project to initialize.
+Run /rihal-new-project to initialize.
 ```
 Exit.
 </step>
 
 <step name="detect_task_list">
-**Detect bulk-task input** — when /rihal:quick or /rihal:do auto-routes a multi-task input here, the entire bug list arrives as `${description}`. Don't put it all in the phase title; extract structure.
+**Detect bulk-task input** — when /rihal-quick or /rihal-do auto-routes a multi-task input here, the entire bug list arrives as `${description}`. Don't put it all in the phase title; extract structure.
 
 Match if `${description}` contains ANY of:
 - 5+ numbered list items (`/^\s*\d+\.\s/m` ≥ 5)
@@ -59,12 +59,12 @@ If matched:
    ```markdown
    # Phase {N} — {phase name} — Tasks
 
-   *Auto-extracted from /rihal:quick or /rihal:do bulk auto-route on {ISO date}.*
+   *Auto-extracted from /rihal-quick or /rihal-do bulk auto-route on {ISO date}.*
 
    {original body, preserved verbatim}
    ```
 
-4. Note in the completion message: "TASKS.md written with N tasks". The downstream /rihal:plan workflow consumes TASKS.md as the input to SPRINT.md generation — no manual re-paste needed.
+4. Note in the completion message: "TASKS.md written with N tasks". The downstream /rihal-plan workflow consumes TASKS.md as the input to SPRINT.md generation — no manual re-paste needed.
 
 If NOT matched (single task), proceed normally — `${description}` is the phase name as-is.
 
@@ -123,12 +123,12 @@ Roadmap updated: .planning/ROADMAP.md
 
 `/clear` then:
 
-`/rihal:plan {N}`
+`/rihal-plan {N}`
 
 ---
 
 **Also available:**
-- `/rihal:add-phase <description>` — add another phase
+- `/rihal-add-phase <description>` — add another phase
 - Review roadmap
 
 ---

package/rihal/workflows/add-tests.md

@@ -1,7 +1,7 @@
 <purpose>
 Generate unit and E2E tests for a completed phase based on its SUMMARY.md, CONTEXT.md, and implementation. Classifies each changed file into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
 
-Users currently hand-craft `/rihal:quick` prompts for test generation after each phase. This workflow standardizes the process with proper classification, quality gates, and gap reporting.
+Users currently hand-craft `/rihal-quick` prompts for test generation after each phase. This workflow standardizes the process with proper classification, quality gates, and gap reporting.
 </purpose>
 
 <required_reading>
@@ -15,15 +15,15 @@ Parse `$ARGUMENTS` for:
 - Phase number (integer, decimal, or letter-suffix) → store as `$PHASE_ARG`
 - Remaining text after phase number → store as `$EXTRA_INSTRUCTIONS` (optional)
 
-Example: `/rihal:add-tests 12 focus on edge cases` → `$PHASE_ARG=12`, `$EXTRA_INSTRUCTIONS="focus on edge cases"`
+Example: `/rihal-add-tests 12 focus on edge cases` → `$PHASE_ARG=12`, `$EXTRA_INSTRUCTIONS="focus on edge cases"`
 
 If no phase argument provided:
 
 ```
 ERROR: Phase number required
-Usage: /rihal:add-tests <phase> [additional instructions]
-Example: /rihal:add-tests 12
-Example: /rihal:add-tests 12 focus on edge cases in the pricing module
+Usage: /rihal-add-tests <phase> [additional instructions]
+Example: /rihal-add-tests 12
+Example: /rihal-add-tests 12 focus on edge cases in the pricing module
 ```
 
 Exit.
@@ -54,7 +54,7 @@ Read the phase artifacts (in order of priority):
 If no SUMMARY.md exists:
 ```
 ERROR: No SUMMARY.md found for phase ${PHASE_ARG}
-This command works on completed phases. Run /rihal:execute-phase first.
+This command works on completed phases. Run /rihal-execute-phase first.
 ```
 Exit.
 
@@ -315,7 +315,7 @@ Present next steps:
 ## ▶ Next Up
 
 {if bugs discovered:}
-**Fix discovered bugs:** `/rihal:quick fix the {N} test failures discovered in phase ${phase_number}`
+**Fix discovered bugs:** `/rihal-quick fix the {N} test failures discovered in phase ${phase_number}`
 
 {if blocked tests:}
 **Resolve test blockers:** {description of what's needed}
@@ -326,8 +326,8 @@ Present next steps:
 ---
 
 **Also available:**
-- `/rihal:add-tests {next_phase}` — test another phase
-- `/rihal:verify-work {phase_number}` — run UAT verification
+- `/rihal-add-tests {next_phase}` — test another phase
+- `/rihal-verify-work {phase_number}` — run UAT verification
 
 ---
 ```

package/rihal/workflows/add-todo.md

@@ -8,13 +8,13 @@ Capture an idea, task, or issue that surfaces during a Rihal session as a struct
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:add-todo <argument-here>
+/rihal-add-todo <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:add-todo example 1
-/rihal:add-todo example 2
+/rihal-add-todo example 1
+/rihal-add-todo example 2
 ```
 
 STOP — do not proceed.
@@ -37,7 +37,7 @@ Ensure directories exist for organized todo capture.
 
 <step name="extract_content">
 **With arguments:** Use as the title/focus.
-- `/rihal:add-todo Add auth token refresh` → title = "Add auth token refresh"
+- `/rihal-add-todo Add auth token refresh` → title = "Add auth token refresh"
 
 **Without arguments:** Analyze recent conversation to extract:
 - The specific problem, idea, or task discussed
@@ -148,7 +148,7 @@ Would you like to:
 
 1. Continue with current work
 2. Add another todo
-3. View all todos (/rihal:add-todo --list)
+3. View all todos (/rihal-add-todo --list)
 ```
 </step>
 

package/rihal/workflows/analyze-dependencies.md

@@ -1,7 +1,7 @@
-# Workflow: rihal:analyze-dependencies
+# Workflow: rihal-analyze-dependencies
 
 <purpose>
-Analyze ROADMAP.md phases for dependency relationships before execution. Detect file overlap between phases, semantic API/data-flow dependencies, and suggest `Depends on` entries to prevent merge conflicts during parallel execution by `/rihal:manager`.
+Analyze ROADMAP.md phases for dependency relationships before execution. Detect file overlap between phases, semantic API/data-flow dependencies, and suggest `Depends on` entries to prevent merge conflicts during parallel execution by `/rihal-manager`.
 </purpose>
 
 
@@ -10,13 +10,13 @@ Analyze ROADMAP.md phases for dependency relationships before execution. Detect
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:analyze-dependencies <argument-here>
+/rihal-analyze-dependencies <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:analyze-dependencies example 1
-/rihal:analyze-dependencies example 2
+/rihal-analyze-dependencies example 1
+/rihal-analyze-dependencies example 2
 ```
 
 STOP — do not proceed.
@@ -26,7 +26,7 @@ STOP — do not proceed.
 **Action:** Read `.planning/ROADMAP.md` and extract all phases.
 
 ```bash
-test -f .planning/ROADMAP.md || echo "No ROADMAP.md found — run /rihal:new-project first."
+test -f .planning/ROADMAP.md || echo "No ROADMAP.md found — run /rihal-new-project first."
 ```
 
 For each phase, capture:
@@ -119,7 +119,7 @@ When writing:
 - Preserve all other phase content unchanged
 - Do not reorder phases
 
-After applying: "ROADMAP.md updated. Run `/rihal:manager` to execute phases in the correct order."
+After applying: "ROADMAP.md updated. Run `/rihal-manager` to execute phases in the correct order."
 
 ## Success Criteria
 

package/rihal/workflows/audit-fix.md

@@ -16,14 +16,14 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:audit-fix [--max N] [--severity high|medium|all] [--dry-run] [--source audit]
+/rihal-audit-fix [--max N] [--severity high|medium|all] [--dry-run] [--source audit]
 ```
 
 **Examples:**
 ```
-/rihal:audit-fix
-/rihal:audit-fix --max 10 --severity high
-/rihal:audit-fix --dry-run
+/rihal-audit-fix
+/rihal-audit-fix --max 10 --severity high
+/rihal-audit-fix --dry-run
 ```
 
 <process>

package/rihal/workflows/audit-milestone.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:audit-milestone
+# Workflow: rihal-audit-milestone
 
 <purpose>
 Cross-phase audit of milestone completion. Reads all SUMMARY.md files from completed phases, compares their outcomes to the original ROADMAP goals, flags gaps, and generates an audit report showing completion percentage and decision traceability.
@@ -9,13 +9,13 @@ Cross-phase audit of milestone completion. Reads all SUMMARY.md files from compl
 If `$ARGUMENTS` contains only `--help` or `-h`:
 
 ```
-/rihal:audit-milestone [--strict] [--report]
+/rihal-audit-milestone [--strict] [--report]
 ```
 
 **Examples:**
 ```
-/rihal:audit-milestone
-/rihal:audit-milestone --strict --report
+/rihal-audit-milestone
+/rihal-audit-milestone --strict --report
 ```
 
 STOP — do not proceed.
@@ -32,7 +32,7 @@ If neither exists:
 ```
 ⚠ No active milestone found. Start a new one:
 
-/rihal:new-milestone <name>
+/rihal-new-milestone <name>
 ```
 
 STOP.
@@ -159,7 +159,7 @@ If `PLANS > 0` AND (`GIT_FEAT > 0` OR `APPS > 0`):
     1. Synthesize SUMMARY.md per phase from PLAN.md + git log [recommended]
        (groups commits by phase tag like "feat(03-1):", writes a
         first-pass SUMMARY.md the user can edit)
-    2. Run /rihal:verify-phase NN per phase (manual close path)
+    2. Run /rihal-verify-phase NN per phase (manual close path)
     3. Continue audit anyway (only assesses what is documented — likely
        reports 0% goal coverage)
     0. Cancel
@@ -174,7 +174,7 @@ If `PLANS == 0`:
 ```
 ⚠ No phase summaries and no plans found. Have phases been executed?
   Check: {MILESTONE_DIR}/phases/
-  Start one: /rihal:plan
+  Start one: /rihal-plan
 ```
 
 STOP.
@@ -183,5 +183,5 @@ If ROADMAP missing:
 
 ```
 ⚠ ROADMAP.md missing. Cannot audit without original goals.
-  Create one: /rihal:new-milestone
+  Create one: /rihal-new-milestone
 ```

package/rihal/workflows/audit-uat.md

@@ -76,9 +76,9 @@ Present the audit report:
 
 ## Recommended Actions
 
-1. **Close stale items:** `/rihal:verify-work {phase}` — mark stale tests as resolved
+1. **Close stale items:** `/rihal-verify-work {phase}` — mark stale tests as resolved
 2. **Run active tests:** Human UAT test plan below
-3. **When prerequisites met:** Retest blocked items with `/rihal:verify-work {phase}`
+3. **When prerequisites met:** Retest blocked items with `/rihal-verify-work {phase}`
 ```
 </step>