@hanzlaa/rcode 3.2.1 → 3.3.1

package/rihal/references/workstream-flag.md

@@ -13,9 +13,9 @@ Use the standard planning pipeline (`.planning/phases/`) for:
 
 **Example:**
 ```
-/rihal:plan Build authentication system
-/rihal:plan Add user profile pages (depends on auth from Phase 1)
-/rihal:plan Write deployment guide (depends on both phases complete)
+/rihal-plan Build authentication system
+/rihal-plan Add user profile pages (depends on auth from Phase 1)
+/rihal-plan Write deployment guide (depends on both phases complete)
 ```
 
 These run sequentially, each depending on the previous phase's completion.
@@ -34,15 +34,15 @@ Use workspaces (`--workspace` flag) for:
 **Example:**
 ```
 # Main workspace (Q2 roadmap)
-/rihal:plan Build search feature
+/rihal-plan Build search feature
 
 # Parallel workspace (critical bug)
-/rihal:new-workspace Critical Hotfix
-/rihal:plan Fix data corruption --workspace=Critical Hotfix
+/rihal-new-workspace Critical Hotfix
+/rihal-plan Fix data corruption --workspace=Critical Hotfix
 
 # Both run independently
 # Query progress:
-/rihal:list-workspaces
+/rihal-list-workspaces
 ```
 
 ## Decision Matrix
@@ -78,29 +78,29 @@ Use workspaces (`--workspace` flag) for:
 
 ```bash
 # View current phase
-/rihal:status
+/rihal-status
 
 # Execute next phase
-/rihal:execute <phase>
+/rihal-execute <phase>
 
 # Switch to different task within same milestone
-/rihal:quick <small task>
+/rihal-quick <small task>
 ```
 
 ### Workspaces
 
 ```bash
 # List all workspaces
-/rihal:list-workspaces
+/rihal-list-workspaces
 
 # Work within a workspace
-/rihal:plan <task> --workspace=Hotfix
+/rihal-plan <task> --workspace=Hotfix
 
 # Switch to another workspace's context
-/rihal:workspace <name>
+/rihal-workspace <name>
 
 # Return to main planning
-/rihal:workspace main
+/rihal-workspace main
 ```
 
 ## Merging Workspaces Back
@@ -109,7 +109,7 @@ If you started a workspace but it should merge back into main planning:
 
 1. Complete the work in the workspace
 2. Create a phase in main planning that incorporates the workspace's findings
-3. Archive the workspace: `/rihal:remove-workspace <name> --archive`
+3. Archive the workspace: `/rihal-remove-workspace <name> --archive`
 4. Continue in main planning with unified context
 
 ## Common Patterns
@@ -118,27 +118,27 @@ If you started a workspace but it should merge back into main planning:
 
 ```bash
 # Main work (Q2 roadmap)
-/rihal:plan Implement real-time notifications
+/rihal-plan Implement real-time notifications
 
 # Critical bug emerges
-/rihal:new-workspace Critical
-/rihal:plan Fix payment processing --workspace=Critical
+/rihal-new-workspace Critical
+/rihal-plan Fix payment processing --workspace=Critical
 
 # Two parallel tracks
-/rihal:list-workspaces
+/rihal-list-workspaces
 
 # When bug is fixed
-/rihal:complete-workspace Critical
+/rihal-complete-workspace Critical
 # Resume main work
-/rihal:execute <Q2 phase>
+/rihal-execute <Q2 phase>
 ```
 
 ### Pattern: Research + implementation
 
 ```bash
 # Sequential phases (both parts of same feature)
-/rihal:plan Research WebSocket libraries and trade-offs
-/rihal:plan Implement chosen library with tests
+/rihal-plan Research WebSocket libraries and trade-offs
+/rihal-plan Implement chosen library with tests
 # Phase 2 reads Phase 1 findings
 ```
 
@@ -146,16 +146,16 @@ If you started a workspace but it should merge back into main planning:
 
 ```bash
 # Keep experiments separate
-/rihal:new-workspace Experiment: Dark Mode
-/rihal:plan Build dark mode UI --workspace=Experiment
-/rihal:plan Test across 10 browsers --workspace=Experiment
+/rihal-new-workspace Experiment: Dark Mode
+/rihal-plan Build dark mode UI --workspace=Experiment
+/rihal-plan Test across 10 browsers --workspace=Experiment
 
 # Main work continues unaffected
-/rihal:plan Improve search relevance
+/rihal-plan Improve search relevance
 
 # If experiment succeeds, merge into main
 # If it fails, just archive and delete
-/rihal:remove-workspace --archive Experiment
+/rihal-remove-workspace --archive Experiment
 ```
 
 ## Summary

package/rihal/skills/_shared/no-autonomous-bypass.md

@@ -13,7 +13,7 @@ Phrases like *"just write it autonomously"*, *"create the full thing ready to ex
 There are exactly two ways to legitimately run a skill without halting at menus:
 
 1. **Project-wide:** `.rihal/config.yaml` → `mode: yolo`. The config loader flags `yoloMode=true` in the runtime context; step files check this flag and may auto-advance.
-2. **Per-invocation:** `/rihal:do --auto <question>` on the router. The router sets `autoMode=true` and passes it to the dispatched skill.
+2. **Per-invocation:** `/rihal-do --auto <question>` on the router. The router sets `autoMode=true` and passes it to the dispatched skill.
 
 If **neither** flag is set, halt is mandatory regardless of what the user's prompt text says.
 
@@ -34,4 +34,4 @@ That response invents a mode that does not exist and violates the halt invariant
 
 ## Correct Response
 
-> ✅ Agent: *"I hear you want the PRD written end-to-end. The halt rule applies unless you set `mode: yolo` in `.rihal/config.yaml` or re-invoke via `/rihal:do --auto`. Here is the step-01 menu — pick Continue and I will drive each step concisely."*
+> ✅ Agent: *"I hear you want the PRD written end-to-end. The halt rule applies unless you set `mode: yolo` in `.rihal/config.yaml` or re-invoke via `/rihal-do --auto`. Here is the step-01 menu — pick Continue and I will drive each step concisely."*

package/rihal/skills/_shared/research-citation-rule.md

@@ -28,7 +28,7 @@ This pattern is forbidden. A citation block without `WebFetch` evidence is a lie
 
 ## If the User Is Running Autonomously
 
-`mode: yolo` and `/rihal:do --auto` bypass halt-at-menu, but they do **not** bypass this rule. A fully-autonomous run still has to fetch every cited URL before writing the claim.
+`mode: yolo` and `/rihal-do --auto` bypass halt-at-menu, but they do **not** bypass this rule. A fully-autonomous run still has to fetch every cited URL before writing the claim.
 
 ## Checklist Before Writing a Citation
 

package/rihal/skills/_shared/state-sync-rule.md

@@ -1,6 +1,6 @@
 # State Sync Rule
 
-Referenced by skills that write `ROADMAP.md`, `epics.md`, or sprint artifacts. These artifacts are not authoritative on their own — downstream workflows (`/rihal:status`, `/rihal:progress`, `/rihal:execute`) read `.rihal/state.json`. If you write a planning artifact and skip state sync, the project ends up with two divergent pictures.
+Referenced by skills that write `ROADMAP.md`, `epics.md`, or sprint artifacts. These artifacts are not authoritative on their own — downstream workflows (`/rihal-status`, `/rihal-progress`, `/rihal-execute`) read `.rihal/state.json`. If you write a planning artifact and skip state sync, the project ends up with two divergent pictures.
 
 ## The Rule
 
@@ -29,15 +29,15 @@ If `rihal-tools.cjs` does not yet expose the needed subcommand, fall back to `st
 ## Verification After Sync
 
 - `node .rihal/bin/rihal-tools.cjs state read` returns a phase count that matches the phase table in `ROADMAP.md`.
-- `/rihal:status` and `/rihal:progress`, run back-to-back, agree on the current milestone name and phase count.
+- `/rihal-status` and `/rihal-progress`, run back-to-back, agree on the current milestone name and phase count.
 
 ## Why This Matters
 
 Observed failure (rihal-code, social-poster-x install, Apr 2026):
 
-- User ran `/rihal:create-epics-and-stories`.
+- User ran `/rihal-create-epics-and-stories`.
 - `ROADMAP.md` gained 10 phases; `epics.md` gained 62 stories.
 - `.rihal/state.json` remained at the initial bootstrap with 1 phase.
-- `/rihal:status` showed 1 phase; `/rihal:progress` showed 10.
+- `/rihal-status` showed 1 phase; `/rihal-progress` showed 10.
 
 That divergence is what this rule exists to prevent.

package/rihal/skills/actions/1-analysis/rihal-prfaq/SKILL.md

@@ -124,7 +124,7 @@ When the user gets stuck, offer concrete suggestions based on what they've share
 **Expected:** Gauntlet mode questioning → press release → customer FAQ → internal FAQ → verdict + distillate. Saved to planning_artifacts/.
 
 ### Headless Mode
-**Input:** `/rihal:prfaq --headless --customer "{persona}" --problem "{problem}" --stakes "{why}" --solution "{concept}"`
+**Input:** `/rihal-prfaq --headless --customer "{persona}" --problem "{problem}" --stakes "{why}" --solution "{concept}"`
 **Expected:** First-draft PRFAQ generated autonomously via artifact-analyzer + web-researcher subagents.
 
 ### Negative Test

package/rihal/skills/actions/2-plan/rihal-create-epics-and-stories/workflow.md

@@ -36,7 +36,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.
 
 ---
 

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

@@ -48,7 +48,7 @@ Follow the instructions in ./workflow.md.
 
 ### Edge Case: No PRD Exists
 **Input:** "Create milestones for social-poster-x" (no prd.md)
-**Expected behavior:** DO NOT invent milestones. Respond: "I need an approved PRD first. Run `/rihal:create-prd` or point me at an existing brief."
+**Expected behavior:** DO NOT invent milestones. Respond: "I need an approved PRD first. Run `/rihal-create-prd` or point me at an existing brief."
 
 ### Edge Case: PRD Marked Draft
 **Input:** PRD exists but frontmatter shows `status: draft`
@@ -56,4 +56,4 @@ Follow the instructions in ./workflow.md.
 
 ### Negative Example: Request to Bypass the Interview
 **Input:** "just generate the full roadmap autonomously"
-**Expected behavior:** DO NOT invent an "autonomous mode". Point the user to the two sanctioned bypass paths (`.rihal/config.yaml` → `mode: yolo` or `/rihal:do --auto`) and present the step-01 menu. See `../../_shared/no-autonomous-bypass.md`.
+**Expected behavior:** DO NOT invent an "autonomous mode". Point the user to the two sanctioned bypass paths (`.rihal/config.yaml` → `mode: yolo` or `/rihal-do --auto`) and present the step-01 menu. See `../../_shared/no-autonomous-bypass.md`.

package/rihal/skills/actions/2-plan/rihal-create-milestone/steps/step-06-phase-stubs.md

@@ -4,12 +4,12 @@
 
 ## STEP GOAL
 
-For each milestone, list the phases it contains as **stubs** (number + name + one-line goal). No plan detail — phases get full plans via `/rihal:plan` later.
+For each milestone, list the phases it contains as **stubs** (number + name + one-line goal). No plan detail — phases get full plans via `/rihal-plan` later.
 
 ## MANDATORY RULES
 
 - 🛑 Phase numbers follow Rihal's NN convention (01, 02, ..., 99, then 999.x for parking lot).
-- 🛑 Do NOT generate plan content here. That's `/rihal:plan-phase`.
+- 🛑 Do NOT generate plan content here. That's `/rihal-plan-phase`.
 - 🛑 Each phase has one-sentence goal, max.
 - ⏸️ HALT at menu.
 

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`.)_