@hanzlaa/rcode 3.3.0 → 3.3.2

package/CONTRIBUTING.md

@@ -30,7 +30,7 @@ A command file is tiny. It registers a slash command in Claude Code's UI and poi
 
 ```markdown
 ---
-name: rihal:prfaq
+name: rihal-prfaq
 description: Working Backwards PRFAQ challenge
 allowed-tools: [Read, Write, Agent, AskUserQuestion, WebSearch]
 ---
@@ -40,14 +40,14 @@ allowed-tools: [Read, Write, Agent, AskUserQuestion, WebSearch]
 
 That `@-include` line tells Claude to load the target file's contents as context. Without a command file, a skill is unreachable via `/` — it can only be triggered by describing the task in natural language.
 
-**Rule:** Every capability intended to be user-typed as `/rihal:something` needs a matching `rihal/commands/something.md`.
+**Rule:** Every capability intended to be user-typed as `/rihal-something` needs a matching `rihal/commands/something.md`.
 
 ### Workflows — orchestration logic
 
 Workflows are prose instructions — markdown files Claude reads as a script to follow. They handle control flow: read state, ask a question, dispatch to a sub-workflow, report results. Most slash commands point to a workflow:
 
 ```
-/rihal:audit  →  commands/audit.md  →  @workflows/audit.md
+/rihal-audit  →  commands/audit.md  →  @workflows/audit.md
 ```
 
 Workflows are the right tool when the task is a sequence of steps that Claude drives (check state → ask user → run something → report). They should not contain deep domain knowledge — that belongs in skills.
@@ -74,7 +74,7 @@ rihal/skills/actions/1-analysis/rihal-prfaq/
 Skills are the right tool when the task has multiple stages, needs sub-agent parallelism, or carries domain-specific coaching logic (e.g., how to run a PRFAQ gauntlet, how to do a Karpathy code review).
 
 Skills have **two activation paths**:
-1. **Via command** — `/rihal:prfaq` loads the SKILL.md directly
+1. **Via command** — `/rihal-prfaq` loads the SKILL.md directly
 2. **Phrase-activated** — when a user describes the task, Claude picks up the skill from its `description` field in the YAML frontmatter
 
 ### Agents — focused specialists
@@ -85,12 +85,12 @@ There are two kinds:
 
 **Sub-agents** live inside skill folders (`rihal/skills/agents/*/SKILL.md`). They're invoked by their parent skill, not by the user directly. Example: the PRFAQ skill spawns `artifact-analyzer` and `web-researcher` in parallel during Stage 1.
 
-**Council agents** live in `rihal/agents/*.md`. They're the named characters (Waleed, Hanzla, Fatima, Sadiq…) that `/rihal:council` assembles into a panel. These are installed to `.claude/agents/` and can be spawned from any workflow.
+**Council agents** live in `rihal/agents/*.md`. They're the named characters (Waleed, Hanzla, Fatima, Sadiq…) that `/rihal-council` assembles into a panel. These are installed to `.claude/agents/` and can be spawned from any workflow.
 
 ### How they chain for a real request
 
 ```
-User types:  /rihal:council "Should we use Redis?"
+User types:  /rihal-council "Should we use Redis?"
                    │
          commands/council.md          ← slash command entry
                    │ @-includes
@@ -108,7 +108,7 @@ User types:  /rihal:council "Should we use Redis?"
 A more complex chain involving a skill:
 
 ```
-User types:  /rihal:prfaq
+User types:  /rihal-prfaq
                    │
          commands/prfaq.md
                    │ @-includes
@@ -128,10 +128,10 @@ User types:  /rihal:prfaq
 
 | I want to… | Edit this |
 |-----------|-----------|
-| Add a new `/rihal:something` slash command | Create `rihal/commands/something.md` pointing to a workflow or skill |
+| Add a new `/rihal-something` slash command | Create `rihal/commands/something.md` pointing to a workflow or skill |
 | Change the steps in an existing command | Edit the workflow it points to |
 | Improve how a persona thinks (Hanzla, Waleed, etc.) | Edit `rihal/skills/agents/<name>/SKILL.md` or `rihal/agents/<name>.md` |
-| Add a new agent to `/rihal:council` | Edit `rihal/agents/team.yaml` + add agent file |
+| Add a new agent to `/rihal-council` | Edit `rihal/agents/team.yaml` + add agent file |
 | Improve a complex multi-stage task (PRFAQ, code review, etc.) | Edit the skill's stage reference files |
 | Add a new skill triggered by natural language | Create `rihal/skills/actions/<category>/<name>/SKILL.md` — no command file needed if slash is not required |
 | Fix a broken `@-include` reference | Check that the target file exists at `.rihal/<path>` after install |

package/README.md

@@ -44,7 +44,7 @@ Rihal Code packages a lot. To keep things approachable, everything is organized
 
 **Brand new?** Do the [Golden Path](docs/TIERS.md#-starter--the-golden-path): scaffold → PRD → stories → sprint → dev → review → status. Seven skills, one project, end-to-end.
 
-> **v2.0 — Rihal Brain.** v1 was a generic AI-engineering methodology. v2 keeps all of that and adds the Rihal context layer on top: standards, guides, and institutional knowledge pulled fresh from Rihal's own repos on install and on `/rihal:update`. See [`CHANGELOG.md`](CHANGELOG.md) and the [v2.0 milestone](https://github.com/hanzlahabib/rihal-code/milestone/4).
+> **v2.0 — Rihal Brain.** v1 was a generic AI-engineering methodology. v2 keeps all of that and adds the Rihal context layer on top: standards, guides, and institutional knowledge pulled fresh from Rihal's own repos on install and on `/rihal-update`. See [`CHANGELOG.md`](CHANGELOG.md) and the [v2.0 milestone](https://github.com/hanzlahabib/rihal-code/milestone/4).
 
 ---
 
@@ -56,7 +56,7 @@ Most AI tools give you one assistant pretending to be everything. **Rihal Code g
 - **95 slash commands** covering research, planning, execution, verification, and recovery
 - **80 skills** including Memory Bank primitives, 11 engineering-rigor skills (TDD, harden, perf, debug, trim, etc.), and 8 real-pain skills (auth-audit, mvp-graduate, deploy-unify, etc.)
 - **Persistent project memory** at `.rihal/memory/` — checked into git, visible in the Diwan dashboard, lossless distillates for fast LLM hydration
-- **3 execution modes**: parallel debate (`/rihal:council`), sequential pipelines (`/rihal:chain`), and quick-sync (`/rihal:discuss`)
+- **3 execution modes**: parallel debate (`/rihal-council`), sequential pipelines (`/rihal-chain`), and quick-sync (`/rihal-discuss`)
 - **File-based state** in `.rihal/` that every workflow reads and updates
 - **Intent guards** on every workflow — catch wrong commands early with copy-paste redirects
 - **Karpathy-inspired coding guidelines** wired into every code-writing agent
@@ -90,14 +90,14 @@ One unified installer. Pure file shipping, no runtime dependencies. Installs int
 - `rihal/brain/` — Rihal standards pulled from upstream (PR / commit / architecture docs)
 - `.planning/` — where your artifacts land (council sessions, plans, chains, summaries)
 
-Restart Claude Code (or your IDE), type `/`, and every `rihal:*` command appears.
+Restart Claude Code (or your IDE), type `/`, and every `rihal-*` command appears.
 
-Update anytime with `npx @hanzlaa/rcode update` (or `/rihal:update` inside a Claude session).
+Update anytime with `npx @hanzlaa/rcode update` (or `/rihal-update` inside a Claude session).
 
 ### Then begin the rihla
 
 ```
-/rihal:init
+/rihal-init
 ```
 
 Detects your project state (fresh / existing-with-no-rihal / returning), asks a few configuration questions, and routes you to the right first action.
@@ -123,14 +123,14 @@ npx @hanzlaa/rcode install --ide gemini
 ## 90-second tour
 
 ```
-/rihal:do                                    → interactive router
-/rihal:council should I rewrite auth?        → 5 agents debate in parallel, 2 rounds
-/rihal:discuss waleed what stack for saas?   → single expert, fast
-/rihal:chain research-plan dubai affiliate   → Mariam → Hussain-PM → Planner pipeline
-/rihal:plan --research build a rental app    → researcher grounds, plan-checker verifies
-/rihal:execute .planning/plans/01/PLAN.md    → atomic commits + post-gates
-/rihal:status                                → phases, decisions, blockers, sessions
-/rihal:code-review HEAD~5..HEAD --karpathy   → audit changes vs 4 coding principles
+/rihal-do                                    → interactive router
+/rihal-council should I rewrite auth?        → 5 agents debate in parallel, 2 rounds
+/rihal-discuss waleed what stack for saas?   → single expert, fast
+/rihal-chain research-plan dubai affiliate   → Mariam → Hussain-PM → Planner pipeline
+/rihal-plan --research build a rental app    → researcher grounds, plan-checker verifies
+/rihal-execute .planning/plans/01/PLAN.md    → atomic commits + post-gates
+/rihal-status                                → phases, decisions, blockers, sessions
+/rihal-code-review HEAD~5..HEAD --karpathy   → audit changes vs 4 coding principles
 ```
 
 ---
@@ -160,7 +160,7 @@ npx @hanzlaa/rcode install --ide gemini
   phases/01-name/PLAN.md       — plans organized by phase number (01, 02, 02.1, etc.)
   council-sessions/            — debate artifacts
   chains/                       — pipeline outputs (RESEARCH.md → SCOPE.md → PLAN.md)
-  notes/                        — quick notes from /rihal:note
+  notes/                        — quick notes from /rihal-note
   HANDOFF.json                  — pause-work checkpoint
   .continue-here.md            — human-readable handoff summary
 ```
@@ -193,38 +193,38 @@ npx @hanzlaa/rcode install --ide gemini
 
 ## Three modes, three mental models
 
-### 🏛️ `/rihal:council` — Parallel debate
+### 🏛️ `/rihal-council` — Parallel debate
 
 3-5 agents answer simultaneously in Round 1, then Round 2 lets each agent challenge the others' Round 1 responses. Result: one session artifact with all voices + orchestrator note flagging the sharpest disagreement.
 
 **Best for:** strategic decisions where you want disagreement, not consensus.
 
 ```
-/rihal:council should we migrate from monolith to microservices?
+/rihal-council should we migrate from monolith to microservices?
 ```
 
-### 🔗 `/rihal:chain` — Sequential pipeline
+### 🔗 `/rihal-chain` — Sequential pipeline
 
 Each agent runs after the previous one finishes, reading that agent's artifact as input. Result: a typed artifact per stage (RESEARCH.md → SCOPE.md → PLAN.md) in `.planning/chains/`.
 
 **Best for:** when you know roughly what you want and each specialist needs to do their part in order.
 
 ```
-/rihal:chain research-plan dubai affiliate site for mobile accessories
-/rihal:chain feasibility migrate postgres to neon serverless
-/rihal:chain gtm-to-build saas bookkeeping in oman
+/rihal-chain research-plan dubai affiliate site for mobile accessories
+/rihal-chain feasibility migrate postgres to neon serverless
+/rihal-chain gtm-to-build saas bookkeeping in oman
 ```
 
-Presets: `research-plan` · `feasibility` · `gtm-to-build` · `full-discovery`. Or custom: `/rihal:chain mariam,waleed,fatima "your topic"`.
+Presets: `research-plan` · `feasibility` · `gtm-to-build` · `full-discovery`. Or custom: `/rihal-chain mariam,waleed,fatima "your topic"`.
 
-### 💬 `/rihal:discuss` — Single agent, quick-sync
+### 💬 `/rihal-discuss` — Single agent, quick-sync
 
 One agent, one round, conversational tone, no mandatory artifact. Feels like texting one colleague.
 
 ```
-/rihal:discuss waleed can we use postgres jsonb for this?
-/rihal:discuss fatima is this release ready?
-/rihal:discuss what's the kill criterion for this project?
+/rihal-discuss waleed can we use postgres jsonb for this?
+/rihal-discuss fatima is this release ready?
+/rihal-discuss what's the kill criterion for this project?
 ```
 
 If no agent named, the panel scorer picks the top match.
@@ -238,10 +238,10 @@ If no agent named, the panel scorer picks the top match.
 Run the wrong command and you get a single-line copy-paste redirect — not a useless output.
 
 ```
-/rihal:plan should we use postgres or mongo?
+/rihal-plan should we use postgres or mongo?
 ⚠ That's a decision question, not a planning input.
 Copy-paste this to ask the council instead:
-/rihal:council should we use postgres or mongo?
+/rihal-council should we use postgres or mongo?
 ```
 
 Every workflow has a Step 0.5 intent detector.
@@ -251,19 +251,19 @@ Every workflow has a Step 0.5 intent detector.
 The classifier recognizes `dubai`, `affiliate`, `bnanai`, `karobar`, `site banana`, `دبئی`, `مارکیٹ`, `کاروبار` and many more. Mariam leads for GCC/MENA market questions.
 
 ```
-/rihal:council yar affiliate site bnanai hai dubai ma for quick bucks
+/rihal-council yar affiliate site bnanai hai dubai ma for quick bucks
 → panel: [mariam, hussain-pm, sadiq]
 ```
 
 ### PRFAQ — validate before you build
 
-Amazon's "Working Backwards" method: write the finished-product press release *before* writing a line of code. If you can't write a compelling press release, the product isn't ready. `/rihal:prfaq` runs a 5-stage coaching gauntlet — Ignition → Press Release → Customer FAQ → Internal FAQ → Verdict — and outputs a battle-hardened concept document plus a PRD distillate ready for `/rihal:create-prd`.
+Amazon's "Working Backwards" method: write the finished-product press release *before* writing a line of code. If you can't write a compelling press release, the product isn't ready. `/rihal-prfaq` runs a 5-stage coaching gauntlet — Ignition → Press Release → Customer FAQ → Internal FAQ → Verdict — and outputs a battle-hardened concept document plus a PRD distillate ready for `/rihal-create-prd`.
 
 **When to use it:** Any time a PM or engineer wants to validate whether an idea is worth building before committing sprint capacity. The skill challenges vague thinking, enforces customer-first framing, and gives a build/refine/kill verdict.
 
 ```
-/rihal:prfaq                                         → interactive gauntlet
-/rihal:prfaq --headless --customer "..." --problem "..." --solution "..."   → autonomous first draft
+/rihal-prfaq                                         → interactive gauntlet
+/rihal-prfaq --headless --customer "..." --problem "..." --solution "..."   → autonomous first draft
 ```
 
 ### Karpathy coding guidelines
@@ -275,23 +275,23 @@ Amazon's "Working Backwards" method: write the finished-product press release *b
 3. **Surgical changes** — touch only what's needed, match existing style
 4. **Goal-driven execution** — define verifiable success criteria
 
-`/rihal:code-review --karpathy` runs these 4 principles as a post-hoc audit against any diff or phase. Use it after implementation to catch bloated, over-engineered, or scope-creeping changes before they land in a PR.
+`/rihal-code-review --karpathy` runs these 4 principles as a post-hoc audit against any diff or phase. Use it after implementation to catch bloated, over-engineered, or scope-creeping changes before they land in a PR.
 
 ```
-/rihal:code-review HEAD~5..HEAD --karpathy
-/rihal:code-review 03 --files=src/auth/ --karpathy
+/rihal-code-review HEAD~5..HEAD --karpathy
+/rihal-code-review 03 --files=src/auth/ --karpathy
 ```
 
 ### Plan verification + post-execute gates
 
-`/rihal:plan` runs `rihal-plan-checker` after the planner writes PLAN.md. On failure, loops back to planner with feedback (max 2 retries).
+`/rihal-plan` runs `rihal-plan-checker` after the planner writes PLAN.md. On failure, loops back to planner with feedback (max 2 retries).
 
-`/rihal:execute` runs `rihal-integration-checker` (cross-phase E2E) and `rihal-nyquist-auditor` (test coverage) after completion. Both append to SUMMARY.md.
+`/rihal-execute` runs `rihal-integration-checker` (cross-phase E2E) and `rihal-nyquist-auditor` (test coverage) after completion. Both append to SUMMARY.md.
 
 ### Model profiles
 
 ```bash
-/rihal:settings       # interactive config
+/rihal-settings       # interactive config
 ```
 
 - **quality** — opus/sonnet-4.6 for reasoning agents
@@ -302,8 +302,8 @@ Amazon's "Working Backwards" method: write the finished-product press release *b
 ### Session handoff
 
 ```
-/rihal:pause-work    → writes .rihal/HANDOFF.json + .continue-here.md
-/rihal:resume-work   → reads HANDOFF, surfaces blocking constraints
+/rihal-pause-work    → writes .rihal/HANDOFF.json + .continue-here.md
+/rihal-resume-work   → reads HANDOFF, surfaces blocking constraints
 ```
 
 ---
@@ -315,16 +315,16 @@ Recent additions in this session:
 - **69 slash commands** across 3 modes and 3 modules (up from 64)
 - **Numeric ID system** — milestones (M1, M2), phases (01, 02, 02.1), plans (01.01, 02.03), tasks (01.01.01) with decimal insertion for urgent inserts
 - **Intent guards** (`Step 0.5`) — every workflow detects mismatched intent and redirects instead of failing
-- **Plan-checker loop** — `/rihal:plan` now verifies file existence and symbol definitions; loops back to planner on validation failure
-- **Post-execute gates** — `/rihal:execute` runs integration-checker (E2E) and nyquist-auditor (coverage) as hard gates
+- **Plan-checker loop** — `/rihal-plan` now verifies file existence and symbol definitions; loops back to planner on validation failure
+- **Post-execute gates** — `/rihal-execute` runs integration-checker (E2E) and nyquist-auditor (coverage) as hard gates
 - **Multilingual classifier** — Roman Urdu, Arabic, English with cultural signal routing (Mariam leads GCC/MENA)
 - **Karpathy guidelines enforcement** — 4 coding principles baked into every code-writing agent
 - **Global agents** — customize agents in `~/.rihal/agents/` without forking the repo
 - **Multi-IDE installer** — support for Claude Code, Cursor, Gemini CLI
 - **Hooks system** — opt-in pre-edit, pre-workflow, post-commit enforcement
-- **Session pause/resume** — `/rihal:pause-work` + `/rihal:resume-work` with HANDOFF.json
-- **Workspace isolation** — `/rihal:new-workspace` for parallel tracks
-- **Decimal phase insertion** — `/rihal:insert-phase` for urgent mid-cycle work
+- **Session pause/resume** — `/rihal-pause-work` + `/rihal-resume-work` with HANDOFF.json
+- **Workspace isolation** — `/rihal-new-workspace` for parallel tracks
+- **Decimal phase insertion** — `/rihal-insert-phase` for urgent mid-cycle work
 
 ---
 
@@ -370,7 +370,7 @@ Recent additions in this session:
 
 ## Configuration
 
-`.rihal/config.yaml` — edit directly or run `/rihal:settings`:
+`.rihal/config.yaml` — edit directly or run `/rihal-settings`:
 
 ```yaml
 user_name: "Hanzla"
@@ -402,7 +402,7 @@ View formatted:
 ```bash
 node .rihal/bin/rihal-tools.cjs state read
 # or
-/rihal:status
+/rihal-status
 ```
 
 ---
@@ -410,7 +410,7 @@ node .rihal/bin/rihal-tools.cjs state read
 ## Hooks (opt-in)
 
 ```bash
-/rihal:enable-hooks
+/rihal-enable-hooks
 ```
 
 Installs 3 opt-in hooks into `.claude/settings.json`:
@@ -424,9 +424,9 @@ Installs 3 opt-in hooks into `.claude/settings.json`:
 
 | Module | Contents |
 |--------|----------|
-| **core** | 5 council agents, `/rihal:council`, `/rihal:discuss`, `/rihal:status`, `/rihal:do`, `/rihal:help`, state management |
-| **execution** | Executor, planner, verifier + checker agents, `/rihal:execute`, `/rihal:plan`, `/rihal:quick`, `/rihal:debug`, `/rihal:audit-fix`, `/rihal:undo` |
-| **discovery** | Codebase-mapper, project-researcher, roadmapper, `/rihal:new-project`, `/rihal:map-codebase`, `/rihal:scan`, `/rihal:explore`, `/rihal:code-review`, `/rihal:docs-update` |
+| **core** | 5 council agents, `/rihal-council`, `/rihal-discuss`, `/rihal-status`, `/rihal-do`, `/rihal-help`, state management |
+| **execution** | Executor, planner, verifier + checker agents, `/rihal-execute`, `/rihal-plan`, `/rihal-quick`, `/rihal-debug`, `/rihal-audit-fix`, `/rihal-undo` |
+| **discovery** | Codebase-mapper, project-researcher, roadmapper, `/rihal-new-project`, `/rihal-map-codebase`, `/rihal-scan`, `/rihal-explore`, `/rihal-code-review`, `/rihal-docs-update` |
 
 Full install = all 3 modules = 201 files.
 

package/cli/context.js

@@ -13,7 +13,7 @@
  *                                         prints a warning when stale
  *
  * The refresh does NOT rewrite active.md or project-brief.md — that's
- * /rihal:init's job (the scan requires an LLM). --refresh just stores the
+ * /rihal-init's job (the scan requires an LLM). --refresh just stores the
  * current fingerprint so the next check sees things as fresh.
  */
 
@@ -117,7 +117,7 @@ function printReport(cwd) {
   console.log();
 
   if (report.status !== 'fresh') {
-    console.log(`   ➡ Refresh with: /rihal:init (in your editor)`);
+    console.log(`   ➡ Refresh with: /rihal-init (in your editor)`);
     console.log();
   }
 }
@@ -125,7 +125,7 @@ function printReport(cwd) {
 /**
  * --refresh: recompute and save the fingerprint to .rihal/state.json.
  * Only use this when you know the memory bank was actually refreshed
- * (e.g. by /rihal:init running end-to-end). Does NOT rewrite context files.
+ * (e.g. by /rihal-init running end-to-end). Does NOT rewrite context files.
  */
 function doRefresh(cwd) {
   ensureRihalDir(cwd);
@@ -161,7 +161,7 @@ if command -v rcode >/dev/null 2>&1; then
   output=$(rcode context --check 2>&1)
   if [ $? -ne 0 ]; then
     echo ""
-    echo "⚠ Rihal memory bank is stale — run /rihal:init in your editor to refresh."
+    echo "⚠ Rihal memory bank is stale — run /rihal-init in your editor to refresh."
     echo "   $(echo "$output" | grep '•' | head -1 | sed 's/^ *//')"
   fi
 fi

package/cli/doctor.js

@@ -190,7 +190,7 @@ function runPreflight(cwd, packageRoot) {
       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({

package/cli/generate-command-skills.cjs

@@ -78,18 +78,18 @@ function discoverRealSkills(packageRoot) {
 }
 
 function generateStub(cmdName, commandFm, version) {
-  const desc = commandFm.description || `Slash command shortcut for /rihal:${cmdName}.`;
+  const desc = commandFm.description || `Slash command shortcut for /rihal-${cmdName}.`;
   const triggers = [
     `rihal ${cmdName}`,
-    `rihal:${cmdName}`,
-    `/rihal:${cmdName}`,
+    `rihal-${cmdName}`,
+    `/rihal-${cmdName}`,
   ];
 
   return `---
 name: rihal-${cmdName}
 description: >
   ${desc.replace(/\n/g, ' ')}
-  Sidebar entry — invokes the same workflow as /rihal:${cmdName}.
+  Sidebar entry — invokes the same workflow as /rihal-${cmdName}.
 triggers:
 ${triggers.map((t) => `  - "${t}"`).join('\n')}
 user-invocable: true
@@ -105,27 +105,27 @@ install or update. To customise, create a sibling \`.local.md\` file (which
 is preserved across installs) or modify the source command at
 rihal/commands/${cmdName}.md.
 
-This stub exists so the slash command /rihal:${cmdName} appears in VS Code's
+This stub exists so the slash command /rihal-${cmdName} appears in VS Code's
 Claude Code sidebar (which lists skills only, not slash commands). The
-behaviour is identical to /rihal:${cmdName} — both invoke the workflow at
+behaviour is identical to /rihal-${cmdName} — both invoke the workflow at
 .rihal/workflows/${cmdName}.md.
 -->
 
 ## Overview
 
-Sidebar entry for the \`/rihal:${cmdName}\` slash command. Phrase-activated alternative invocation route.
+Sidebar entry for the \`/rihal-${cmdName}\` slash command. Phrase-activated alternative invocation route.
 
 ## Workflow
 
-Read and execute \`@.rihal/workflows/${cmdName}.md\` end-to-end. The behaviour is the same as invoking \`/rihal:${cmdName}\` directly.
+Read and execute \`@.rihal/workflows/${cmdName}.md\` end-to-end. The behaviour is the same as invoking \`/rihal-${cmdName}\` directly.
 
 ## Output Format
 
-Identical to \`/rihal:${cmdName}\`. See the workflow file for the canonical output spec.
+Identical to \`/rihal-${cmdName}\`. See the workflow file for the canonical output spec.
 
 ## Examples
 
-**Happy path** — say "rihal ${cmdName}" or "/rihal:${cmdName}" → workflow runs identically either way.
+**Happy path** — say "rihal ${cmdName}" or "/rihal-${cmdName}" → workflow runs identically either way.
 
 **Negative — looking for the canonical command file** — see \`rihal/commands/${cmdName}.md\` (the source of truth) and \`rihal/workflows/${cmdName}.md\` (the orchestration logic).
 

package/cli/install.js

@@ -498,7 +498,7 @@ function copyDirRecursive(source, dest) {
 
 /**
  * Seed .planning/ with starter ROADMAP.md + STATE.md + PROJECT.md so
- * workflows work immediately after install. User can /rihal:sprint-planning
+ * workflows work immediately after install. User can /rihal-sprint-planning
  * on a fresh install without manual setup.
  *
  * Only seeds if .planning/ROADMAP.md doesn't already exist (preserves user data).
@@ -548,7 +548,7 @@ function seedStarterPlanning(target, projectName) {
     `---\n\n` +
     `## Decisions\n\n_None yet._\n\n` +
     `## Blockers\n\n_None._\n\n` +
-    `## Next Action\n\nSay "plan a sprint" or run \`/rihal:sprint-planning\` to break Phase 01 into stories.\n`
+    `## Next Action\n\nSay "plan a sprint" or run \`/rihal-sprint-planning\` to break Phase 01 into stories.\n`
   );
 
   // Also pre-seed .rihal/state.json with Phase 01 so sprint tools work
@@ -845,7 +845,7 @@ function buildInstallPlan(ide = 'claude', target = process.cwd()) {
     plan.push({ src: f, rel: path.join(relBin, rel), executable: f.endsWith('.cjs') });
   }
 
-  // .rihal/templates/projects/  — starter templates consumed by /rihal:from-template
+  // .rihal/templates/projects/  — starter templates consumed by /rihal-from-template
   const projectTemplatesSrc = path.join(SOURCE_ROOT, 'templates', 'projects');
   const relProjectTemplates = path.relative(target, path.join(target, '.rihal', 'templates', 'projects'));
   for (const f of walkFiles(projectTemplatesSrc)) {
@@ -1572,7 +1572,7 @@ async function install(opts) {
       console.log('');
       console.log('  ' + warn('config.yaml has validation errors:'));
       for (const e of validation.errors) console.log(pc.yellow(e));
-      console.log(dim('  → Edit .rihal/config.yaml to fix, then run /rihal:status'));
+      console.log(dim('  → Edit .rihal/config.yaml to fix, then run /rihal-status'));
     }
   } catch { /* best-effort */ }
 
@@ -1593,16 +1593,16 @@ async function install(opts) {
   ensureDir(path.join(opts.target, '.planning', 'council-sessions'));
 
   // .rihal/context/ — seed stub files so doctor doesn't report "never initialized"
-  // The /rihal:init slash command populates these with real project content.
+  // The /rihal-init slash command populates these with real project content.
   const contextDir = path.join(opts.target, '.rihal', 'context');
   ensureDir(contextDir);
   const activeCtx = path.join(contextDir, 'active.md');
   const briefCtx = path.join(contextDir, 'project-brief.md');
   if (!fs.existsSync(activeCtx)) {
-    fs.writeFileSync(activeCtx, '# Active Context\n\n_Run `/rihal:init` inside your AI editor to populate this file._\n');
+    fs.writeFileSync(activeCtx, '# Active Context\n\n_Run `/rihal-init` inside your AI editor to populate this file._\n');
   }
   if (!fs.existsSync(briefCtx)) {
-    fs.writeFileSync(briefCtx, '# Project Brief\n\n_Run `/rihal:init` inside your AI editor to populate this file._\n');
+    fs.writeFileSync(briefCtx, '# Project Brief\n\n_Run `/rihal-init` inside your AI editor to populate this file._\n');
   }
 
   // ~/.rihal/agents/ global agents directory
@@ -1754,13 +1754,13 @@ async function install(opts) {
   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)'));

package/cli/lib/memory-bank.cjs

@@ -9,10 +9,10 @@
  *
  * This module detects staleness programmatically by comparing a project
  * fingerprint (git HEAD, package manifest hash, top-level structure hash)
- * against one stored in .rihal/state.json at the last /rihal:init run.
+ * against one stored in .rihal/state.json at the last /rihal-init run.
  *
  * It is intentionally READ-ONLY + write-fingerprint. The actual scan and
- * rewrite of the memory bank is done by Claude when /rihal:init runs —
+ * rewrite of the memory bank is done by Claude when /rihal-init runs —
  * this library only tells callers WHEN to refresh, not HOW.
  */
 
@@ -186,7 +186,7 @@ function readState(cwd) {
 
 /**
  * Persist the init fingerprint into .rihal/state.json under `memory_bank`.
- * Called by /rihal:init (via rihal-code context --refresh) after a scan
+ * Called by /rihal-init (via rihal-code context --refresh) after a scan
  * rewrites context/active.md + context/project-brief.md.
  */
 function writeFingerprint(cwd) {
@@ -238,7 +238,7 @@ function checkStaleness(cwd) {
   if (!context_files.active && !context_files.brief) {
     return {
       status: 'never',
-      reasons: ['memory bank has never been initialized — run /rihal:init'],
+      reasons: ['memory bank has never been initialized — run /rihal-init'],
       current,
       stored,
       context_files,
@@ -264,7 +264,7 @@ function checkStaleness(cwd) {
   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,

package/cli/set-mode.js

@@ -12,10 +12,10 @@
  *
  * Affects:
  *   - Workflow step files ("halt at menu" vs "pick default and continue")
- *   - /rihal:kickoff next-step menu (interactive vs auto-continue)
+ *   - /rihal-kickoff next-step menu (interactive vs auto-continue)
  *   - github-sync confirmation prompts (yolo still requires --force-yolo
  *     for github mutations — see docs/adr/0001-github-sync-as-cli.md)
- *   - /rihal:pause and /rihal:resume (yolo skips the confirmation prompt
+ *   - /rihal-pause and /rihal-resume (yolo skips the confirmation prompt
  *     on resume; guided always asks)
  *   - All agent skill files that read communication_mode from config
  */

package/cli/uninstall.js

@@ -19,7 +19,7 @@
  *   --delete-state                                    Also delete .rihal/ (skip prompt)
  *   --purge / --all                                   Wipe everything — editor files,
  *                                                       .rihal/, .planning/, gitignore block.
- *                                                       Use when you want /rihal:init to
+ *                                                       Use when you want /rihal-init to
  *                                                       report "fresh" on next install.
  *   --yes / -y                                        Skip the main confirmation
  */
@@ -49,7 +49,7 @@ function parseArgs(args) {
       opts.yes = true;
     } else if (arg === '--purge' || arg === '--all') {
       // --purge implies --delete-state and removes .planning/ + gitignore block.
-      // Use this when you want a clean slate so /rihal:init reports "fresh" next time.
+      // Use this when you want a clean slate so /rihal-init reports "fresh" next time.
       opts.purge = true;
       opts.deleteState = true;
     }
@@ -596,7 +596,7 @@ async function runUninstall(args) {
       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 — no carry-over.`);
       console.log();
@@ -652,10 +652,10 @@ async function runUninstall(args) {
   }
 
   // Hint about the purge flag if the user kept state — closes the user's
-  // most common confusion: "I uninstalled but /rihal:init still says configured."
+  // most common confusion: "I uninstalled but /rihal-init still says configured."
   if (plan.stateDir && fs.existsSync(path.join(cwd, '.rihal'))) {
     console.log();
-    console.log(`ℹ  .rihal/ state was preserved. /rihal:init will detect this on reinstall.`);
+    console.log(`ℹ  .rihal/ state was preserved. /rihal-init will detect this on reinstall.`);
     console.log(`   For a fully clean slate next time, use: rcode uninstall --purge`);
   }