@hanzlaa/rcode 3.2.1 → 3.3.1

package/rihal/commands/validate-phase.md

@@ -1,5 +1,5 @@
 ---
-name: rihal:validate-phase
+name: rihal-validate-phase
 description: Audit Nyquist validation gaps for a completed phase. Generate missing tests. Update VALIDATION.md.
 argument-hint: "<phase-number>"
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Agent

package/rihal/commands/verify-phase.md

@@ -1,6 +1,6 @@
 ---
-name: rihal:verify-phase
-description: "Goal-backward audit — does the codebase actually deliver what the phase promised? Produces VERIFICATION.md with pass/fail. Required before /rihal:ship. Run after /rihal:execute completes."
+name: rihal-verify-phase
+description: "Goal-backward audit — does the codebase actually deliver what the phase promised? Produces VERIFICATION.md with pass/fail. Required before /rihal-ship. Run after /rihal-execute completes."
 argument-hint: "<phase-number>"
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion, Agent
 ---

package/rihal/commands/verify-work.md

@@ -1,5 +1,5 @@
 ---
-name: rihal:verify-work
+name: rihal-verify-work
 description: Conversational acceptance testing — verify sprint stories against acceptance criteria
 argument-hint: "[--phase <NN>]"
 allowed-tools: Read, Bash, Grep, Glob, AskUserQuestion

package/rihal/commands/why.md

@@ -1,5 +1,5 @@
 ---
-name: rihal:why
+name: rihal-why
 description: Explain the reasoning behind a decision, classification, or panel selection
 argument-hint: <topic-or-question>
 allowed-tools:

package/rihal/commands/workstream.md

@@ -1,5 +1,5 @@
 ---
-name: rihal:workstream
+name: rihal-workstream
 description: Manage parallel workstreams (milestone tracks). Create, switch, list, or complete workstreams in state.json.
 argument-hint: "<subcommand> [--name <name>]"
 allowed-tools:

package/rihal/references/agent-shared-rules.md

@@ -54,7 +54,7 @@
 
 **Honest scope declaration.** When investigating, declare what you searched, what you skipped, and what you couldn't see. Empty blind-spot lists are usually a tell that the agent didn't honestly account for what it skipped.
 
-**Refuse out-of-lane work explicitly.** State which peer agent owns it and how to hand off. *"That's an architecture call — Waleed's lane. `/rihal:discuss waleed`."* Never silently take work that belongs to a peer.
+**Refuse out-of-lane work explicitly.** State which peer agent owns it and how to hand off. *"That's an architecture call — Waleed's lane. `/rihal-discuss waleed`."* Never silently take work that belongs to a peer.
 
 ---
 

package/rihal/references/command-redirect-format.md

@@ -4,14 +4,14 @@ Shared reference for all agents and workflows when they suggest the user run a d
 
 ## The rule
 
-**When suggesting a `/rihal:*` command, print it on a single line for copy-paste.**
+**When suggesting a `/rihal-*` command, print it on a single line for copy-paste.**
 
 The user's terminal-style interface benefits from one-line commands they can select and paste without touching line-wrap issues. Never split a suggested command across multiple lines, never bullet it, never break arguments onto separate rows.
 
 ## Good format
 
 ```
-Run: /rihal:council I'm in Pakistan, USD 1000 budget, want to dropship Gaming + Creator accessories to UAE. Should I build a Next.js custom app or use Shopify?
+Run: /rihal-council I'm in Pakistan, USD 1000 budget, want to dropship Gaming + Creator accessories to UAE. Should I build a Next.js custom app or use Shopify?
 ```
 
 One line. User selects the whole line, pastes, presses enter.
@@ -19,7 +19,7 @@ One line. User selects the whole line, pastes, presses enter.
 ## Bad format — do NOT do this
 
 ```
-Run /rihal:council with the new question:
+Run /rihal-council with the new question:
 "I'm in Pakistan, USD 1000 budget, want to dropship Gaming + Creator accessories to UAE. Should I build a Next.js custom app or use Shopify?"
 ```
 
@@ -29,7 +29,7 @@ Two lines, with quotes, with a lead-in sentence. The user has to reconstruct the
 
 Agents and workflows redirect when:
 - An agent receives a question outside its domain (Sadiq gets a technical question → Waleed)
-- A workflow gets an input type it doesn't handle (`/rihal:plan` gets a decision question → `/rihal:council`)
+- A workflow gets an input type it doesn't handle (`/rihal-plan` gets a decision question → `/rihal-council`)
 - The user's intent would be better served by a different command
 
 ## Template
@@ -39,7 +39,7 @@ Agents and workflows redirect when:
 
 Copy-paste this instead:
 
-/rihal:<command> <exact arguments from user's original input>
+/rihal-<command> <exact arguments from user's original input>
 ```
 
 The third line — the full command — is a single physical line, regardless of length. No wrapping. No quotes around the arguments unless the command itself requires them.
@@ -55,8 +55,8 @@ If multiple commands could fit, list each on its own line as a complete single-l
 ```
 Could be either — pick one:
 
-/rihal:discuss waleed <your question>
-/rihal:council <your question>
+/rihal-discuss waleed <your question>
+/rihal-council <your question>
 ```
 
 Not with lead-in prose for each option.

package/rihal/references/context-budget.md

@@ -59,7 +59,7 @@ Estimation rule: **1 token ≈ 4 characters**. Use this to predict token cost of
 - 🚨 **Emergency mode**
 - 🛑 Read ONLY what's strictly required to unblock next action
 - 🛑 No exploratory reads, no documentation
-- 🛑 Suggest `/rihal:pause-work` if task requires more context
+- 🛑 Suggest `/rihal-pause-work` if task requires more context
 - 🛑 Warn user: **"Context critical ({percent}%). Resume work to continue."**
 
 **Behavior:** Survival — preserve tokens for final output only.
@@ -76,7 +76,7 @@ def check_budget(current_tokens, config):
     used_pct = (current_tokens / budget) * 100
     
     if used_pct >= 80:
-        return 'POOR', "Context critical. Suggest /rihal:pause-work"
+        return 'POOR', "Context critical. Suggest /rihal-pause-work"
     elif used_pct >= 60:
         return 'DEGRADING', "Context at {used_pct}%. Read frontmatter only."
     elif used_pct >= 30:

package/rihal/references/continuation-format.md

@@ -44,7 +44,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 
-`/rihal:execute-phase 2`
+`/rihal-execute-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -52,7 +52,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 **Also available:**
 - Review plan before executing
-- `/rihal:list-phase-assumptions 2` — check assumptions
+- `/rihal-list-phase-assumptions 2` — check assumptions
 
 ---
 ```
@@ -69,7 +69,7 @@ Add note that this is the last plan and what comes after:
 **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
 <sub>Final plan in Phase 2</sub>
 
-`/rihal:execute-phase 2`
+`/rihal-execute-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -91,15 +91,15 @@ Add note that this is the last plan and what comes after:
 
 **Phase 2: Authentication** — JWT login flow with refresh tokens
 
-`/rihal:plan-phase 2`
+`/rihal-plan-phase 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/rihal:discuss-phase 2` — gather context first
-- `/rihal:research-phase 2` — investigate unknowns
+- `/rihal-discuss-phase 2` — gather context first
+- `/rihal-research-phase 2` — investigate unknowns
 - Review roadmap
 
 ---
@@ -120,15 +120,15 @@ Show completion status before next action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-`/rihal:plan-phase 3`
+`/rihal-plan-phase 3`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/rihal:discuss-phase 3` — gather context first
-- `/rihal:research-phase 3` — investigate unknowns
+- `/rihal-discuss-phase 3` — gather context first
+- `/rihal-research-phase 3` — investigate unknowns
 - Review what Phase 2 built
 
 ---
@@ -145,11 +145,11 @@ When there's no clear primary action:
 
 **Phase 3: Core Features** — User dashboard, settings, and data export
 
-**To plan directly:** `/rihal:plan-phase 3`
+**To plan directly:** `/rihal-plan-phase 3`
 
-**To discuss context first:** `/rihal:discuss-phase 3`
+**To discuss context first:** `/rihal-discuss-phase 3`
 
-**To research unknowns:** `/rihal:research-phase 3`
+**To research unknowns:** `/rihal-research-phase 3`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -169,7 +169,7 @@ All 4 phases shipped
 
 **Start v1.1** — questioning → research → requirements → roadmap
 
-`/rihal:new-milestone`
+`/rihal-new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -214,7 +214,7 @@ Extract: `**02-03: Refresh Token Rotation** — Add /api/auth/refresh with slidi
 ## To Continue
 
 Run `/clear`, then paste:
-/rihal:execute-phase 2
+/rihal-execute-phase 2
 ```
 
 User has no idea what 02-03 is about.
@@ -222,7 +222,7 @@ User has no idea what 02-03 is about.
 ### Don't: Missing /clear explanation
 
 ```
-`/rihal:plan-phase 3`
+`/rihal-plan-phase 3`
 
 Run /clear first.
 ```
@@ -242,7 +242,7 @@ Sounds like an afterthought. Use "Also available:" instead.
 
 ```
 ```
-/rihal:plan-phase 3
+/rihal-plan-phase 3
 ```
 ```
 

package/rihal/references/dispatch-banner.md

@@ -130,7 +130,7 @@ Then print a fresh DISPATCH banner.
 
 ## Concurrency: parallel dispatches
 
-If a workflow spawns multiple agents in parallel (e.g. `/rihal:council` summons 4 specialists), print ONE combined banner:
+If a workflow spawns multiple agents in parallel (e.g. `/rihal-council` summons 4 specialists), print ONE combined banner:
 
 ```
 ╭─────────────────────────────────────────────────────────╮

package/rihal/references/execution-protocol.md

@@ -79,14 +79,14 @@ Type: {human-verify | decision}
 {For human-verify:}
 Please verify: {what to check}
 URL/path: {where to look}
-Resume with: /rihal:execute {plan} --continue
+Resume with: /rihal-execute {plan} --continue
 
 {For decision:}
 Problem: {what the plan assumed that isn't true}
 Option A: {approach} — {trade-off}
 Option B: {approach} — {trade-off}
 Recommendation: {which one and why}
-Resume with: /rihal:execute {plan} --continue --option=A
+Resume with: /rihal-execute {plan} --continue --option=A
 ---
 ```
 

package/rihal/references/gates.md

@@ -18,7 +18,7 @@ Defines 4 gate types used in rihal workflows to control execution flow, validate
 **Example:** Phase execution gate
 ```
 Gate: Check phase.md exists and has required sections
-Block: "Phase {N} has no SPRINT.md. Create with /rihal:help"
+Block: "Phase {N} has no SPRINT.md. Create with /rihal-help"
 Warn: "Phase overdue by {days}. Review roadmap?"
 ```
 
@@ -77,14 +77,14 @@ Ask: "Pattern A is faster but less flexible. Pattern B is extensible but slower.
 - Exit cleanly without recovery attempt
 - Suggest manual recovery path
 
-**Recovery:** Manual repair via `/rihal:health` or `/rihal:forensics`
+**Recovery:** Manual repair via `/rihal-health` or `/rihal-forensics`
 
 **Example:** Corrupted state gate
 ```
 Gate: Validate state.json integrity
 Fail: "state.json corrupted (invalid JSON at line 42).
        Aborting to prevent further damage.
-       Recovery: /rihal:health --repair"
+       Recovery: /rihal-health --repair"
 ```
 
 ---

package/rihal/references/git-integration.md

@@ -132,7 +132,7 @@ git commit -m "feat(...): description"
 ### Worktree-Isolation Strategy
 ```bash
 # Workflow commands
-/rihal:do --worktree phase/2-auth
+/rihal-do --worktree phase/2-auth
 # Internally:
 git worktree add .claude/worktrees/phase-2-auth phase/2-auth
 cd .claude/worktrees/phase-2-auth

package/rihal/references/output-format.md

@@ -29,7 +29,7 @@ Use for major workflow transitions.
 
 ---
 
-## Routing Output (for /rihal:do, /rihal:next, /rihal:progress)
+## Routing Output (for /rihal-do, /rihal-next, /rihal-progress)
 
 Use this when a router command dispatches to another command:
 
@@ -42,7 +42,7 @@ Input: {user's question or intent}
 Scope: {one-line summary of detected scope}
 {optional: Blocker: {any blockers detected}}
 
-Routing to: /rihal:{target-command}
+Routing to: /rihal-{target-command}
 Reason: {one-line why this command fits}
 
 Handing off to the workflow now.
@@ -253,8 +253,8 @@ Always at end of major completions.
 ───────────────────────────────────────────────────────────────
 
 **Also available:**
-- `/rihal:alternative-1` — description
-- `/rihal:alternative-2` — description
+- `/rihal-alternative-1` — description
+- `/rihal-alternative-2` — description
 
 ───────────────────────────────────────────────────────────────
 ```

package/rihal/references/output-realism.md

@@ -43,7 +43,7 @@ Keep the whole response under ~300 words. Tone: colleague-honest, not apologetic
 - **rihal-planner:** If `## Scope` from orchestrator implies > 8 tasks of real work, return a PLANS.md with *multiple* SPRINT.md files (waves) instead of one overloaded plan.
 - **rihal-executor:** If a SPRINT.md would require > 1500 lines of new/changed code to execute, stop at Step 2 (load plan) and return a "plan too large — suggest wave split" checkpoint instead of executing.
 - **rihal-roadmapper:** Phase size cap: one phase = one coherent batch that a solo developer + AI can reasonably ship in 1-3 focused sessions.
-- **/rihal:autonomous** and **/rihal:do --auto:** Even in auto mode, pause at the first batch boundary that exceeds output budget. "Don't stop until done" authorizes local commits, not output-budget violations.
+- **/rihal-autonomous** and **/rihal-do --auto:** Even in auto mode, pause at the first batch boundary that exceeds output budget. "Don't stop until done" authorizes local commits, not output-budget violations.
 
 ## The Core Philosophy
 

package/rihal/references/revision-loop.md

@@ -1,6 +1,6 @@
 # Plan Revision Loop
 
-When `workflow.plan_checker` is enabled (`/rihal:settings`), `/rihal:plan`
+When `workflow.plan_checker` is enabled (`/rihal-settings`), `/rihal-plan`
 runs the rihal-plan-checker after the planner. Findings drive a bounded
 revision loop:
 

package/rihal/references/state-schema.md

@@ -34,7 +34,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `version`
 **Type:** string  
 **Example:** `"1"`  
-**Written by:** `/rihal:install` (initialization)  
+**Written by:** `/rihal-install` (initialization)  
 **Purpose:** Schema version for compatibility checks. Change if fields added/removed.
 
 ---
@@ -42,7 +42,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `project`
 **Type:** string  
 **Example:** `"Rihal v2"`  
-**Written by:** `/rihal:install` (reads from config.yaml)  
+**Written by:** `/rihal-install` (reads from config.yaml)  
 **Purpose:** Project name for context and reports.
 
 ---
@@ -50,7 +50,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `created`
 **Type:** ISO date string  
 **Example:** `"2026-04-01T10:30:00Z"`  
-**Written by:** `/rihal:install` (first session)  
+**Written by:** `/rihal-install` (first session)  
 **Purpose:** Timestamp of project creation, never changes.
 
 ---
@@ -66,7 +66,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `current_phase`
 **Type:** string or null  
 **Example:** `"Phase 2: Authentication"` or `null`  
-**Written by:** `/rihal:do`, `/rihal:next`, `/rihal:resume-work`  
+**Written by:** `/rihal-do`, `/rihal-next`, `/rihal-resume-work`  
 **Purpose:** Name of active phase, null if no phase active.
 
 ---
@@ -74,7 +74,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `current_plan`
 **Type:** number  
 **Example:** `2`  
-**Written by:** `/rihal:do --execute` (incremented after each phase completion)  
+**Written by:** `/rihal-do --execute` (incremented after each phase completion)  
 **Purpose:** Counter for plan versions. Increments 1→2→3 as phases complete.
 
 ---
@@ -120,7 +120,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:do --execute`, `/rihal:next`, sprint/story state tools  
+**Written by:** `/rihal-do --execute`, `/rihal-next`, sprint/story state tools  
 **Purpose:** Tracks phases with nested sprints and stories.
 
 **Sprint fields:**
@@ -176,7 +176,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:execute` (after each plan completes)  
+**Written by:** `/rihal-execute` (after each plan completes)  
 **Purpose:** Log of each plan execution. The `plan` field is the plan ID string (e.g., "01.02"), not a number.
 
 ---
@@ -194,7 +194,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:council`, `/rihal:discuss`  
+**Written by:** `/rihal-council`, `/rihal-discuss`  
 **Purpose:** Records architectural/strategic decisions for history.
 
 ---
@@ -213,7 +213,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:do`, `/rihal:health`  
+**Written by:** `/rihal-do`, `/rihal-health`  
 **Purpose:** Tracks blockers, when identified, which phase, and resolution time.
 
 ---
@@ -231,7 +231,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:council`  
+**Written by:** `/rihal-council`  
 **Purpose:** History of council deliberations, panelists, output artifacts.
 
 ---
@@ -249,7 +249,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:chain`  
+**Written by:** `/rihal-chain`  
 **Purpose:** History of multi-agent chains, participants, work artifacts.
 
 ---
@@ -258,7 +258,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 **Type:** ISO date string  
 **Example:** `"2026-04-12T15:45:30Z"`  
 **Written by:** Every subcommand that runs (updates at session end)  
-**Purpose:** Enables `/rihal:resume-work` to find context from last session.
+**Purpose:** Enables `/rihal-resume-work` to find context from last session.
 
 ---
 
@@ -283,7 +283,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
   }
 ]
 ```
-**Written by:** `/rihal:workstream --create`, `/rihal:do --execute`  
+**Written by:** `/rihal-workstream --create`, `/rihal-do --execute`  
 **Purpose:** Tracks parallel workstreams, which phases belong to each.
 
 ---
@@ -291,7 +291,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `active_workstream`
 **Type:** string or null  
 **Example:** `"Frontend"` or `null`  
-**Written by:** `/rihal:workstream --activate`, `/rihal:do`  
+**Written by:** `/rihal-workstream --activate`, `/rihal-do`  
 **Purpose:** Currently active workstream; null if no workstream focus.
 
 ---
@@ -299,7 +299,7 @@ Documents every top-level field in `state.json`, used by rihal workflows for ses
 ### `model_profile`
 **Type:** string  
 **Example:** `"balanced"` (options: `quality`, `balanced`, `budget`, `inherit`)  
-**Written by:** `/rihal:set-profile`  
+**Written by:** `/rihal-set-profile`  
 **Purpose:** Model selection for council agents. Affects token spend and quality.
 
 ---

package/rihal/references/ui-brand.md

@@ -1,6 +1,6 @@
 # UI/Brand Questions
 
-When exploring the UI design phase (/rihal:ui-phase), ask structured questions across these eight dimensions: **color palette**, **typography**, **voice/tone**, **accessibility**, **component inventory**, **responsive behavior**, **interaction patterns**, and **visual hierarchy**. These questions build the design contract.
+When exploring the UI design phase (/rihal-ui-phase), ask structured questions across these eight dimensions: **color palette**, **typography**, **voice/tone**, **accessibility**, **component inventory**, **responsive behavior**, **interaction patterns**, and **visual hierarchy**. These questions build the design contract.
 
 ---
 

package/rihal/references/verb-dictionary.md

@@ -76,19 +76,19 @@ These are matched alongside §Create / §Add / §Plan verbs to determine the dis
 
 | Scope noun | Aliases (English + Urdu) | Maps to (workflow) |
 |---|---|---|
-| milestone | `milestone`, `milestones`, `release`, `version`, `cycle` | `/rihal:new-milestone` |
-| phase | `phase`, `phases` (singular intent — "add a phase") | `/rihal:add-phase` |
-| story | `story`, `stories`, `user story`, `kahani` | `/rihal:create-story` |
-| epic | `epic`, `epics`, `epics and stories` | `/rihal:create-epics-and-stories` |
-| sprint | `sprint`, `iteration` | `/rihal:sprint-planning` |
-| PRD | `PRD`, `requirements doc`, `product requirements` | `/rihal:create-prd` |
-| roadmap | `roadmap`, `plan` (top-level) | `/rihal:create-milestone` |
-| council | `council`, `majlis`, `panel`, `mashwara`, `salah` | `/rihal:council` |
-| plan (verb form — "plan phase N") | `plan` | `/rihal:plan` |
-| story (impl) | `dev story`, `implement story`, `build story` | `/rihal:dev-story` |
-| brainstorm | `brainstorm`, `ideas`, `sochain`, `sochna` | `/rihal:brainstorm` |
-| review (code) | `code review`, `karpathy`, `check my diff` | `/rihal:code-review [--karpathy]` |
-| debug | `debug`, `fix`, `bug`, `error`, `crash`, `kharab`, `theek` | `/rihal:debug` |
+| milestone | `milestone`, `milestones`, `release`, `version`, `cycle` | `/rihal-new-milestone` |
+| phase | `phase`, `phases` (singular intent — "add a phase") | `/rihal-add-phase` |
+| story | `story`, `stories`, `user story`, `kahani` | `/rihal-create-story` |
+| epic | `epic`, `epics`, `epics and stories` | `/rihal-create-epics-and-stories` |
+| sprint | `sprint`, `iteration` | `/rihal-sprint-planning` |
+| PRD | `PRD`, `requirements doc`, `product requirements` | `/rihal-create-prd` |
+| roadmap | `roadmap`, `plan` (top-level) | `/rihal-create-milestone` |
+| council | `council`, `majlis`, `panel`, `mashwara`, `salah` | `/rihal-council` |
+| plan (verb form — "plan phase N") | `plan` | `/rihal-plan` |
+| story (impl) | `dev story`, `implement story`, `build story` | `/rihal-dev-story` |
+| brainstorm | `brainstorm`, `ideas`, `sochain`, `sochna` | `/rihal-brainstorm` |
+| review (code) | `code review`, `karpathy`, `check my diff` | `/rihal-code-review [--karpathy]` |
+| debug | `debug`, `fix`, `bug`, `error`, `crash`, `kharab`, `theek` | `/rihal-debug` |
 
 ---
 
@@ -106,8 +106,8 @@ table above, dispatch directly to the mapped workflow without an
 ambiguity prompt.
 
 Example: "milestone bnao" → §Create matches "bnao", scope matches
-"milestone" → /rihal:new-milestone (with state-aware redirect to
-/rihal:add-phase if a milestone is already active).
+"milestone" → /rihal-new-milestone (with state-aware redirect to
+/rihal-add-phase if a milestone is already active).
 ```
 
 **From an agent file (e.g. `rihal-codebase-mapper.md`) when interpreting the orchestrator prompt:**