@hanzlaa/rcode 3.3.0 → 3.3.1

package/dist/rcode.js

@@ -16183,7 +16183,7 @@ _None._
 
 ## Next Action
 
-Say "plan a sprint" or run \`/rihal:sprint-planning\` to break Phase 01 into stories.
+Say "plan a sprint" or run \`/rihal-sprint-planning\` to break Phase 01 into stories.
 `
       );
       const rihalStateJson = path2.join(target, ".rihal", "state.json");
@@ -16985,7 +16985,7 @@ Say "plan a sprint" or run \`/rihal:sprint-planning\` to break Phase 01 into sto
           console.log("");
           console.log("  " + warn("config.yaml has validation errors:"));
           for (const e of validation.errors) console.log(pc.yellow(e));
-          console.log(dim("  \u2192 Edit .rihal/config.yaml to fix, then run /rihal:status"));
+          console.log(dim("  \u2192 Edit .rihal/config.yaml to fix, then run /rihal-status"));
         }
       } catch {
       }
@@ -17004,10 +17004,10 @@ Say "plan a sprint" or run \`/rihal:sprint-planning\` to break Phase 01 into sto
       const activeCtx = path2.join(contextDir, "active.md");
       const briefCtx = path2.join(contextDir, "project-brief.md");
       if (!fs2.existsSync(activeCtx)) {
-        fs2.writeFileSync(activeCtx, "# Active Context\n\n_Run `/rihal:init` inside your AI editor to populate this file._\n");
+        fs2.writeFileSync(activeCtx, "# Active Context\n\n_Run `/rihal-init` inside your AI editor to populate this file._\n");
       }
       if (!fs2.existsSync(briefCtx)) {
-        fs2.writeFileSync(briefCtx, "# Project Brief\n\n_Run `/rihal:init` inside your AI editor to populate this file._\n");
+        fs2.writeFileSync(briefCtx, "# Project Brief\n\n_Run `/rihal-init` inside your AI editor to populate this file._\n");
       }
       const globalAgentsDir = path2.join(os.homedir(), ".rihal", "agents");
       ensureDir(globalAgentsDir);
@@ -17124,13 +17124,13 @@ Say "plan a sprint" or run \`/rihal:sprint-planning\` to break Phase 01 into sto
       console.log(`  ${bold("Next:")}`);
       console.log(`    cd ${opts.target}`);
       console.log("    claude              # start Claude Code (reload window if already open)");
-      console.log("    /rihal:progress     # where you are, what's next");
-      console.log("    /rihal:do           # interactive command picker");
-      console.log("    /rihal:council <q>  # multi-agent strategic answer");
+      console.log("    /rihal-progress     # where you are, what's next");
+      console.log("    /rihal-do           # interactive command picker");
+      console.log("    /rihal-council <q>  # multi-agent strategic answer");
       console.log("");
       console.log(dim("  Refresh anytime:"));
       console.log(dim("    npx @hanzlaa/rcode@latest install   # pull the latest rcode + brain"));
-      console.log(dim(`    /rihal:update v${version}              # pin rcode to a specific version`));
+      console.log(dim(`    /rihal-update v${version}              # pin rcode to a specific version`));
       console.log("");
       console.log(dim("  Customize without losing changes on update:"));
       console.log(dim("    Create <name>.local.md siblings (e.g. .claude/agents/rihal-waleed.local.md)"));
@@ -18485,7 +18485,7 @@ var require_uninstall = __commonJS({
           console.log(`   - phases, decisions, progress, artifacts, context`);
           console.log(`   - ${plan.stateDir.files} files total`);
           console.log();
-          console.log(`   If you keep it: /rihal:init will report "already configured"`);
+          console.log(`   If you keep it: /rihal-init will report "already configured"`);
           console.log(`     and reuse your existing config + history on next install.`);
           console.log(`   If you delete it: next install starts fresh \u2014 no carry-over.`);
           console.log();
@@ -18528,7 +18528,7 @@ var require_uninstall = __commonJS({
       }
       if (plan.stateDir && fs2.existsSync(path2.join(cwd, ".rihal"))) {
         console.log();
-        console.log(`\u2139  .rihal/ state was preserved. /rihal:init will detect this on reinstall.`);
+        console.log(`\u2139  .rihal/ state was preserved. /rihal-init will detect this on reinstall.`);
         console.log(`   For a fully clean slate next time, use: rcode uninstall --purge`);
       }
       console.log(`
@@ -18816,7 +18816,7 @@ var require_memory_bank = __commonJS({
       if (!context_files.active && !context_files.brief) {
         return {
           status: "never",
-          reasons: ["memory bank has never been initialized \u2014 run /rihal:init"],
+          reasons: ["memory bank has never been initialized \u2014 run /rihal-init"],
           current,
           stored,
           context_files
@@ -18837,7 +18837,7 @@ var require_memory_bank = __commonJS({
       if (!stored) {
         return {
           status: "stale",
-          reasons: ["run /rihal:init in your editor to populate project context"],
+          reasons: ["run /rihal-init in your editor to populate project context"],
           current,
           stored,
           context_files
@@ -19041,7 +19041,7 @@ var require_doctor = __commonJS({
           checks.push({
             label: "Memory bank",
             status: "warn",
-            message: "never initialized (run /rihal:init to populate)"
+            message: "never initialized (run /rihal-init to populate)"
           });
         } else {
           checks.push({
@@ -19777,7 +19777,7 @@ var require_context = __commonJS({
       }
       console.log();
       if (report.status !== "fresh") {
-        console.log(`   \u27A1 Refresh with: /rihal:init (in your editor)`);
+        console.log(`   \u27A1 Refresh with: /rihal-init (in your editor)`);
         console.log();
       }
     }
@@ -19809,7 +19809,7 @@ if command -v rcode >/dev/null 2>&1; then
   output=$(rcode context --check 2>&1)
   if [ $? -ne 0 ]; then
     echo ""
-    echo "\u26A0 Rihal memory bank is stale \u2014 run /rihal:init in your editor to refresh."
+    echo "\u26A0 Rihal memory bank is stale \u2014 run /rihal-init in your editor to refresh."
     echo "   $(echo "$output" | grep '\u2022' | head -1 | sed 's/^ *//')"
   fi
 fi

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzlaa/rcode",
-  "version": "3.3.0",
+  "version": "3.3.1",
   "description": "rcode — the memory bank for AI-driven SaaS teams. Persistent project context, distinctive engineering personas, and phase-based workflows. Built by Rihal. Works in Claude Code, Cursor, Gemini, VS Code, and Antigravity.",
   "main": "cli/index.js",
   "bin": {

package/rihal/DOCS-AUDIT.md

@@ -1,6 +1,6 @@
 # DOCS-AUDIT.md (per-project artefact)
 
-This file is generated by `/rihal:document-project` into the project root
+This file is generated by `/rihal-document-project` into the project root
 as `DOCS-AUDIT.md`. The shipped reference here just defines the schema:
 
 - **Inventory:** every doc file (path, last-touched, owner, freshness).

package/rihal/agents/rihal-ahmed.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-ahmed
-description: Technology & Development Director — spawned by /rihal:council for delivery timelines, engineering standards, DORA metrics, cross-team coordination, RACI matrices, and tech debt prioritization. Bridges CTO vision (Waleed) to execution (Nasser). Defers to Waleed on architecture, Nasser on individual engineer management.
+description: Technology & Development Director — spawned by /rihal-council for delivery timelines, engineering standards, DORA metrics, cross-team coordination, RACI matrices, and tech debt prioritization. Bridges CTO vision (Waleed) to execution (Nasser). Defers to Waleed on architecture, Nasser on individual engineer management.
 tools: Read, Grep, Glob, Bash
 color: blue
 ---

package/rihal/agents/rihal-codebase-mapper.md

@@ -17,7 +17,7 @@ You are **Dalil (دليل) — Codebase Scout** 🧭. The name means "guide" in
 
 **Honesty about scope is the core of this role.** You are the agent users blame when a future plan rests on a falsehood like "no Sentry SDK in `backend/`" — when there was. Your Scan Scope section exists so that lie can never happen again. If you didn't search a directory, say so. If you found zero matches for a topic phrase, double-check with case-insensitive grep AND the canonical SDK name before claiming "not present."
 
-You are spawned by `/rihal:scan` and `/rihal:map-codebase` with one of four focus areas:
+You are spawned by `/rihal-scan` and `/rihal-map-codebase` with one of four focus areas:
 - **tech**: Analyze technology stack and external integrations → write STACK.md and INTEGRATIONS.md
 - **arch**: Analyze architecture and file structure → write ARCHITECTURE.md and STRUCTURE.md
 - **quality**: Analyze coding conventions and testing patterns → write CONVENTIONS.md and TESTING.md
@@ -32,7 +32,7 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 <why_this_matters>
 **These documents are consumed by other rihal commands:**
 
-**`/rihal:plan`** loads relevant codebase docs when creating implementation plans:
+**`/rihal-plan`** loads relevant codebase docs when creating implementation plans:
 | Phase Type | Documents Loaded |
 |------------|------------------|
 | UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
@@ -43,7 +43,7 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 | refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
 | setup, config | STACK.md, STRUCTURE.md |
 
-**`/rihal:execute`** references codebase docs to:
+**`/rihal-execute`** references codebase docs to:
 - Follow existing conventions when writing code
 - Know where to place new files (STRUCTURE.md)
 - Match testing patterns (TESTING.md)

package/rihal/agents/rihal-debugger.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-debugger
-description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /rihal:debug orchestrator.
+description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /rihal-debug orchestrator.
 tools: Read, Write, Edit, Bash, Grep, Glob
 color: orange
 ---
@@ -14,7 +14,7 @@ color: orange
 Rihal debugger. Investigate bugs using systematic scientific method, manage persistent debug sessions, handle checkpoints.
 
 **Spawned by:**
-- `/rihal:debug` command (interactive debugging)
+- `/rihal-debug` command (interactive debugging)
 - `diagnose-issues` workflow (parallel UAT diagnosis)
 
 **Mandatory Initial Read:** If prompt contains `<files_to_read>`, read every file listed before any other action.

package/rihal/agents/rihal-fatima.md

@@ -3,7 +3,7 @@ name: rihal-fatima
 description: |
   QA Lead — for test strategy, coverage gaps, release readiness, regression risk,
   flaky tests, "is this production-ready", quality gates, edge case enumeration.
-  Spawned by /rihal:council, sprint-checker, release-gate dispatch.
+  Spawned by /rihal-council, sprint-checker, release-gate dispatch.
   Activates: "what could break", quality gate, release go/no-go, soak window,
   rollback plan, post-mortem framing, "talk to Fatima", P0 sign-off.
   Do NOT use for: market / discovery (Mariam), architecture (Waleed), strategic
@@ -60,7 +60,7 @@ Always read on activation:
 
 If the question is market / discovery / research with no code, plan, or artifact:
 - **Council mode:** state once you'll wait for plan / code, then stay silent.
-- **Solo via /rihal:discuss:** suggest `/rihal:discuss mariam` for market questions. Otherwise state exactly what you need (code / plan / artifact) before contributing. Do not guess.
+- **Solo via /rihal-discuss:** suggest `/rihal-discuss mariam` for market questions. Otherwise state exactly what you need (code / plan / artifact) before contributing. Do not guess.
 
 ## Redirects
 

package/rihal/agents/rihal-haitham.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-haitham
 description: |
-  Senior Frontend Engineer — spawned by /rihal:council, /rihal:plan, frontend
+  Senior Frontend Engineer — spawned by /rihal-council, /rihal-plan, frontend
   story execution, and any UI/component dispatch.
   Activates for: React, Next.js App Router, component design, Tailwind / CSS,
   RTL / Arabic layouts, accessibility (a11y), keyboard navigation, screen-
@@ -118,7 +118,7 @@ Always read on activation:
 **Negative routing** — Out of scope
 > *"Should the Add Lead form be a modal or a side panel?"*
 >
-> 🎨 **Haitham:** UX flow decision — Layla's lane. I'll implement whichever pattern she picks. `/rihal:discuss layla`.
+> 🎨 **Haitham:** UX flow decision — Layla's lane. I'll implement whichever pattern she picks. `/rihal-discuss layla`.
 
 ## Redirects
 

package/rihal/agents/rihal-khalid.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-khalid
-description: DevOps & Infrastructure Engineer — spawned by /rihal:council for deployment pipelines, CI/CD, container orchestration, cloud infrastructure, monitoring, and release engineering questions. Defers to Waleed on architecture-level infra decisions, Fatima on release gates, Yousef on backend service configuration.
+description: DevOps & Infrastructure Engineer — spawned by /rihal-council for deployment pipelines, CI/CD, container orchestration, cloud infrastructure, monitoring, and release engineering questions. Defers to Waleed on architecture-level infra decisions, Fatima on release gates, Yousef on backend service configuration.
 tools: Read, Grep, Glob, Bash
 color: orange
 ---

package/rihal/agents/rihal-layla.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-layla
-description: UX Designer — spawned by /rihal:council for user experience design, interaction flows, design systems, accessibility audits, and usability reviews. Defers to Haitham on frontend implementation, Waleed on technical feasibility, Zahra on branding, Fatima on visual regression testing.
+description: UX Designer — spawned by /rihal-council for user experience design, interaction flows, design systems, accessibility audits, and usability reviews. Defers to Haitham on frontend implementation, Waleed on technical feasibility, Zahra on branding, Fatima on visual regression testing.
 tools: Read, Grep, Glob, WebFetch
 color: cyan
 ---

package/rihal/agents/rihal-nasser.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-nasser
-description: Software Engineering Manager — spawned by /rihal:council for people operations, 1:1 prep, hiring plans, growth conversations, team health, burnout detection, and squad composition questions. Defers to Ahmed Al Hassani on delivery timelines, Waleed on architecture, Hussain-SM on sprint ceremonies.
+description: Software Engineering Manager — spawned by /rihal-council for people operations, 1:1 prep, hiring plans, growth conversations, team health, burnout detection, and squad composition questions. Defers to Ahmed Al Hassani on delivery timelines, Waleed on architecture, Hussain-SM on sprint ceremonies.
 tools: Read, Grep, Glob, Bash
 color: yellow
 ---

package/rihal/agents/rihal-noor.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-noor
-description: Technical Writer & Presentation Lead — spawned by /rihal:council and /rihal:docs-update for README files, API docs, architecture diagrams (Mermaid), changelogs, migration guides, inline code comments, pitch decks, and blog posts. Defers to Hussain-PM on PRD content, Hanzla on code implementation details, Sadiq on strategic framing.
+description: Technical Writer & Presentation Lead — spawned by /rihal-council and /rihal-docs-update for README files, API docs, architecture diagrams (Mermaid), changelogs, migration guides, inline code comments, pitch decks, and blog posts. Defers to Hussain-PM on PRD content, Hanzla on code implementation details, Sadiq on strategic framing.
 tools: Read, Write, Edit, Grep, Glob, Bash, WebFetch
 color: teal
 ---

package/rihal/agents/rihal-nyquist-auditor.md

@@ -10,7 +10,7 @@ color: #8B5CF6
 @.rihal/references/no-unauthorized-git-ops.md
 
 <role>
-Rihal Nyquist auditor. Spawned by /rihal:validate-phase to fill validation gaps in completed phases.
+Rihal Nyquist auditor. Spawned by /rihal-validate-phase to fill validation gaps in completed phases.
 
 For each gap in `<gaps>`: generate minimal behavioral test, run it, debug if failing (max 3 iterations), report results.
 

package/rihal/agents/rihal-omar.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-omar
 description: |
-  Software Engineer (generalist) — spawned by /rihal:council, story execution
+  Software Engineer (generalist) — spawned by /rihal-council, story execution
   pairings, and any cross-stack implementation work.
   Activates for: implementing stories that span frontend + backend, picking
   up small subtasks delegated by Hanzla, bug-fix runs, regression tests,

package/rihal/agents/rihal-phase-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-phase-researcher
-description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by rihal-planner. Spawned by /rihal:plan orchestrator.
+description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by rihal-planner. Spawned by /rihal-plan orchestrator.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 color: cyan
 ---
@@ -13,7 +13,7 @@ color: cyan
 <role>
 You are a Rihal phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
 
-Spawned by `/rihal:plan` (integrated) or `/rihal:research` (standalone).
+Spawned by `/rihal-plan` (integrated) or `/rihal-research` (standalone).
 
 **CRITICAL: Mandatory Initial Read**
 If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
@@ -44,7 +44,7 @@ This ensures research aligns with project-specific conventions and libraries.
 </project_context>
 
 <upstream_input>
-**CONTEXT.md** (if exists) — User decisions from `/rihal:discuss-phase`
+**CONTEXT.md** (if exists) — User decisions from `/rihal-discuss-phase`
 
 | Section | How You Use It |
 |---------|----------------|

package/rihal/agents/rihal-planner.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-planner
-description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /rihal:plan orchestrator.
+description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /rihal-plan orchestrator.
 tools: Read, Write, Bash, Glob, Grep, WebFetch
 color: green
 ---

package/rihal/agents/rihal-project-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-project-researcher
-description: Researches domain ecosystem before roadmap creation. Produces files in .rihal/research/ consumed during roadmap creation. Spawned by /rihal:new-project or /rihal:new-milestone orchestrators.
+description: Researches domain ecosystem before roadmap creation. Produces files in .rihal/research/ consumed during roadmap creation. Spawned by /rihal-new-project or /rihal-new-milestone orchestrators.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 color: cyan
 ---
@@ -11,7 +11,7 @@ color: cyan
 
 
 <role>
-You are a rihal project researcher spawned by `/rihal:new-project` or `/rihal:new-milestone` (Phase 6: Research).
+You are a rihal project researcher spawned by `/rihal-new-project` or `/rihal-new-milestone` (Phase 6: Research).
 
 Answer "What does this domain ecosystem look like?" Write research files in `.rihal/research/` that inform roadmap creation.
 

package/rihal/agents/rihal-research-synthesizer.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-research-synthesizer
-description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /rihal:new-project after 4 researcher agents complete.
+description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /rihal-new-project after 4 researcher agents complete.
 tools: Read, Write, Bash
 color: purple
 ---
@@ -14,7 +14,7 @@ You are a Rihal research synthesizer. You read the outputs from 4 parallel resea
 
 You are spawned by:
 
-- `/rihal:new-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
+- `/rihal-new-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
 
 Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
 
@@ -110,7 +110,7 @@ This is the most important section. Based on combined research:
 - Which pitfalls it must avoid
 
 **Add research flags:**
-- Which phases likely need `/rihal:research` during planning?
+- Which phases likely need `/rihal-research` during planning?
 - Which phases have well-documented patterns (skip research)?
 
 ## Step 5: Assess Confidence

package/rihal/agents/rihal-roadmapper.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-roadmapper
-description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /rihal:new-project orchestrator.
+description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /rihal-new-project orchestrator.
 tools: Read, Write, Bash, Glob, Grep
 color: purple
 ---
@@ -15,7 +15,7 @@ You are a rihal roadmapper. You create project roadmaps that map requirements to
 
 You are spawned by:
 
-- `/rihal:new-project` orchestrator (unified project initialization)
+- `/rihal-new-project` orchestrator (unified project initialization)
 
 Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
 
@@ -32,7 +32,7 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 </role>
 
 <downstream_consumer>
-Your ROADMAP.md is consumed by `/rihal:plan` which uses it to:
+Your ROADMAP.md is consumed by `/rihal-plan` which uses it to:
 
 | Output | How Plan-Phase Uses It |
 |--------|------------------------|

package/rihal/agents/rihal-sadiq.md

@@ -3,7 +3,7 @@ name: rihal-sadiq
 description: |
   Director of Strategy — for "should we build this", priority, kill criteria,
   market timing, opportunity cost, portfolio thinking, GCC / Oman context.
-  Spawned by /rihal:council, /rihal:discuss, strategic dispatch.
+  Spawned by /rihal-council, /rihal-discuss, strategic dispatch.
   Activates: "should we build", "why now", "what NOT to do", "kill criterion",
   "should we sunset", "is this strategic", "talk to Sadiq", "strategy review".
   Do NOT use for: technical feasibility (Waleed), backend impl (Yousef),

package/rihal/agents/rihal-sprint-checker.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-sprint-checker
-description: Verifies sprints will achieve phase goal before execution. Goal-backward analysis of sprint quality. Spawned by /rihal:plan orchestrator.
+description: Verifies sprints will achieve phase goal before execution. Goal-backward analysis of sprint quality. Spawned by /rihal-plan orchestrator.
 tools: Read, Bash, Glob, Grep
 color: green
 ---
@@ -12,7 +12,7 @@ color: green
 <role>
 You are a Rihal sprint checker. Verify that sprints WILL achieve the phase goal, not just that they look complete.
 
-Spawned by `/rihal:plan` orchestrator (after planner creates SPRINT.md) or re-verification (after planner revises).
+Spawned by `/rihal-plan` orchestrator (after planner creates SPRINT.md) or re-verification (after planner revises).
 
 Goal-backward verification of PLANS before execution. Start from what the phase SHOULD deliver, verify sprints address it.
 
@@ -46,7 +46,7 @@ This ensures verification checks that sprints follow project-specific convention
 </project_context>
 
 <upstream_input>
-**CONTEXT.md** (if exists) — User decisions from `/rihal:discuss-phase`
+**CONTEXT.md** (if exists) — User decisions from `/rihal-discuss-phase`
 
 | Section | How You Use It |
 |---------|----------------|

package/rihal/agents/rihal-verifier.md

@@ -49,7 +49,7 @@ Before verifying, discover project context:
 10. **Behavioral spot-checks** — run 2-4 quick commands (<10s each) against runnable code. Skip if no runnable entry points.
 11. **Human verification needs** — visual, real-time, external service, uncertain wiring.
 12. **Determine status** — passed | gaps_found | human_needed. Score = verified_truths / total_truths.
-13. **Structure gap output** — YAML frontmatter for `/rihal:plan --gaps`.
+13. **Structure gap output** — YAML frontmatter for `/rihal-plan --gaps`.
 14. **Create VERIFICATION.md** — use Write tool (never heredoc). Return to orchestrator. DO NOT COMMIT.
 
 ## Final Status Tables
@@ -91,7 +91,7 @@ Read these ONLY when the current step needs them. Don't preemptively load.
 - **DO NOT trust SUMMARY claims** — verify the component actually renders messages, not a placeholder.
 - **DO NOT assume existence = implementation** — need level 2 (substantive), 3 (wired), and 4 (data flowing) for dynamic-data artifacts.
 - **DO NOT skip key link verification** — 80% of stubs hide in wiring.
-- **Structure gaps in YAML frontmatter** for `/rihal:plan --gaps`.
+- **Structure gaps in YAML frontmatter** for `/rihal-plan --gaps`.
 - **DO flag for human verification when uncertain** (visual, real-time, external service).
 - **Keep verification fast** — use grep/file checks, not running the app.
 - **DO NOT commit** — leave committing to the orchestrator.

package/rihal/agents/rihal-waleed.md

@@ -3,7 +3,7 @@ name: rihal-waleed
 description: |
   CTO and Chief Architect — for architecture decisions, stack selection,
   technical feasibility, ADR writing, scalability ceilings, security posture,
-  tech-debt prioritisation. Spawned by /rihal:council and technical dispatch.
+  tech-debt prioritisation. Spawned by /rihal-council and technical dispatch.
   Activates: "should we use X or Y", "can we scale to N", "is this feasible",
   "right architecture for", "ADR for", "talk to Waleed", "rewrite vs refactor",
   "monolith vs microservices", "which database / queue / cache".

package/rihal/agents/rihal-yousef.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-yousef
 description: |
-  Senior Backend Engineer — spawned by /rihal:council, /rihal:plan, and any
+  Senior Backend Engineer — spawned by /rihal-council, /rihal-plan, and any
   backend dispatch (API design, queries, services, queues, perf, integrations).
   Activates for: API design, schema design, query optimization, p50/p95/p99
   latency, throughput tuning, BullMQ / Celery / SQS / RabbitMQ, webhooks,
@@ -113,7 +113,7 @@ Always read on activation:
 **Negative routing** — Out of scope
 > *"What's the React component for the leads table?"*
 >
-> ⚙️ **Yousef:** Frontend — Haitham's lane. Hand off via `/rihal:discuss haitham`.
+> ⚙️ **Yousef:** Frontend — Haitham's lane. Hand off via `/rihal-discuss haitham`.
 
 ## Redirects
 

package/rihal/agents/rihal-zahra.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-zahra
-description: Branding & Creative Director — spawned by /rihal:council for brand identity, visual language, typography systems (Latin + Arabic), color systems, design tokens, and cross-touchpoint brand consistency. Defers to Layla on UX interaction design, Haitham on frontend implementation, Mariam on marketing copy.
+description: Branding & Creative Director — spawned by /rihal-council for brand identity, visual language, typography systems (Latin + Arabic), color systems, design tokens, and cross-touchpoint brand consistency. Defers to Layla on UX interaction design, Haitham on frontend implementation, Mariam on marketing copy.
 tools: Read, Grep, Glob, WebFetch
 color: magenta
 ---

package/rihal/agents/rihal-zayd.md

@@ -1,6 +1,6 @@
 ---
 name: rihal-zayd
-description: Senior ML Engineer — spawned by /rihal:council for machine learning, OCR, LLM integration, RAG/retrieval, vector search, reranking, embeddings, prompt engineering, and eval questions. Defers to Waleed on architecture, Yousef on integration points (queues, APIs), Fatima on eval methodology.
+description: Senior ML Engineer — spawned by /rihal-council for machine learning, OCR, LLM integration, RAG/retrieval, vector search, reranking, embeddings, prompt engineering, and eval questions. Defers to Waleed on architecture, Yousef on integration points (queues, APIs), Fatima on eval methodology.
 tools: Read, Grep, Glob, Bash, WebFetch
 color: purple
 ---

package/rihal/agents/rules/phase-researcher/detailed-guide.md

@@ -307,7 +307,7 @@ Verified patterns from official sources:
 ### Sampling Rate
 - **Per task commit:** `{quick run command}`
 - **Per wave merge:** `{full suite command}`
-- **Phase gate:** Full suite green before `/rihal:verify-work`
+- **Phase gate:** Full suite green before `/rihal-verify-work`
 
 ### Wave 0 Gaps
 - [ ] `{tests/test_file.py}` — covers REQ-{XX}

package/rihal/agents/rules/roadmapper/detailed-guide.md

@@ -522,7 +522,7 @@ After incorporating user feedback and updating files:
 
 ### Ready for Planning
 
-Next: `/rihal:plan 1`
+Next: `/rihal-plan 1`
 ```
 
 ## Roadmap Blocked

package/rihal/agents/rules/sprint-checker/dimensions.md

@@ -189,7 +189,7 @@ issue:
 
 ## Dimension 7: Context Compliance (if CONTEXT.md exists)
 
-**Question:** Do plans honor user decisions from /rihal:discuss-phase?
+**Question:** Do plans honor user decisions from /rihal-discuss-phase?
 
 **Only check if CONTEXT.md was provided in the verification context.**
 
@@ -244,7 +244,7 @@ Before running checks 8a-8d, verify VALIDATION.md exists:
 ls "${PHASE_DIR}"/*-VALIDATION.md 2>/dev/null
 ```
 
-**If missing:** **BLOCKING FAIL** — "VALIDATION.md not found for phase {N}. Re-run `/rihal:plan {N} --research` to regenerate."
+**If missing:** **BLOCKING FAIL** — "VALIDATION.md not found for phase {N}. Re-run `/rihal-plan {N} --research` to regenerate."
 Skip checks 8a-8d entirely. Report Dimension 8 as FAIL with this single issue.
 
 **If exists:** Proceed to checks 8a-8d.
@@ -406,7 +406,7 @@ issue:
   missing_symbols:
     - "imaginary_function"
   verified_ratio: 0.2
-  fix_hint: "Plan was built on hallucinated findings. Re-run /rihal:debug to verify actual code state before replanning."
+  fix_hint: "Plan was built on hallucinated findings. Re-run /rihal-debug to verify actual code state before replanning."
 ```
 
 </verification_dimensions>

package/rihal/agents/rules/sprint-checker/process.md

@@ -162,7 +162,7 @@ console.log(JSON.stringify(result, null, 2));
 
 Check result:
 - If `summary.ratio < 0.5`: **BLOCKER** — "Plan references files/symbols that don't exist. Plan was built on hallucinated findings."
-- If `summary.ratio >= 0.5 AND < 0.8`: **WARNING** — List missing files/symbols, suggest re-planning with /rihal:debug
+- If `summary.ratio >= 0.5 AND < 0.8`: **WARNING** — List missing files/symbols, suggest re-planning with /rihal-debug
 - If `summary.ratio >= 0.8`: **INFO** — Most references verified, proceed
 
 Append to verification output:
@@ -288,7 +288,7 @@ Return all issues as a structured `issues:` YAML list (see dimension examples fo
 | 01   | 3     | 5     | 1    | Valid  |
 | 02   | 2     | 4     | 2    | Valid  |
 
-Plans verified. Run `/rihal:execute {phase}` to proceed.
+Plans verified. Run `/rihal-execute {phase}` to proceed.
 ```
 
 ## ISSUES FOUND

package/rihal/agents/rules/verifier/gap-output.md

@@ -28,7 +28,7 @@
 
 ## Step 10: Structure Gap Output (If Gaps Found)
 
-Structure gaps in YAML frontmatter for `/rihal:plan --gaps`:
+Structure gaps in YAML frontmatter for `/rihal-plan --gaps`:
 
 ```yaml
 gaps:

package/rihal/agents/rules/verifier/verification-report.md

@@ -119,7 +119,7 @@ All must-haves verified. Phase goal achieved. Ready to proceed.
 1. **{Truth 1}** — {reason}
    - Missing: {what needs to be added}
 
-Structured gaps in VERIFICATION.md frontmatter for `/rihal:plan --gaps`.
+Structured gaps in VERIFICATION.md frontmatter for `/rihal-plan --gaps`.
 
 {If human_needed:}
 ### Human Verification Required

package/rihal/bin/rihal-hooks.cjs

@@ -4,7 +4,7 @@
  *
  * Subcommands:
  *   pre-edit    — verify file was Read before Edit/Write (exit 2 if not)
- *   pre-workflow — soft warning for rihal:* commands with suspicious args
+ *   pre-workflow — soft warning for rihal-* commands with suspicious args
  *   post-commit — verify commit format and no forbidden patterns
  *
  * All subcommands read stdin JSON from the hook execution context.
@@ -61,7 +61,7 @@ async function preEdit() {
 }
 
 /**
- * pre-workflow: Soft warning for rihal:* commands with suspicious args.
+ * pre-workflow: Soft warning for rihal-* commands with suspicious args.
  * Does not block (exit 0), but prints warning.
  */
 async function preWorkflow() {
@@ -70,8 +70,8 @@ async function preWorkflow() {
     const command = input.command || '';
     const args = input.args || '';
 
-    // Only check rihal:* commands
-    if (!command.startsWith('rihal:')) {
+    // Only check rihal-* commands
+    if (!command.startsWith('rihal-')) {
       process.exit(0);
     }
 
@@ -94,8 +94,8 @@ async function preWorkflow() {
       }
     }
 
-    if (hasSuspiciousPattern && (command === 'rihal:plan' || command === 'rihal:discuss')) {
-      console.warn(`⚠ "${command}" with args: "${args}". Did you mean /rihal:do or /rihal:council?`);
+    if (hasSuspiciousPattern && (command === 'rihal-plan' || command === 'rihal-discuss')) {
+      console.warn(`⚠ "${command}" with args: "${args}". Did you mean /rihal-do or /rihal-council?`);
     }
 
     process.exit(0);