@hanzlaa/rcode 3.2.1 → 3.3.1

package/rihal/workflows/help.md

@@ -17,7 +17,7 @@ Read `$ARGUMENTS` and resolve to one of: `basic`, `intermediate`, `advanced`, `a
 Usage block:
 
 ```
-Usage: /rihal:help [basic|intermediate|advanced|all]
+Usage: /rihal-help [basic|intermediate|advanced|all]
 
   basic         Show the 8 essentials (default)
   intermediate  Show real-project ops (council, review, ship, capture)
@@ -47,23 +47,23 @@ init → new-project → plan → execute → next → status → ship
 
 | Command | What it does |
 |---------|--------------|
-| `/rihal:init` | First-time setup in this repo. Detects state, asks config questions, writes `.rihal/RIHLA.md`. Run once per project. |
-| `/rihal:new-project` | Take an idea to a planned roadmap. Questioning → optional research → REQUIREMENTS → ROADMAP. |
-| `/rihal:plan <phase>` | Create executable plans for a phase. Produces `SPRINT.md` files. |
-| `/rihal:execute <phase>` | Run all plans in a phase in dependency waves. Updates STATE on completion. |
-| `/rihal:next` | Auto-route to the next logical step based on project state. Zero friction. |
-| `/rihal:status` | Where am I — current phase, plan progress, recent decisions, blockers. |
-| `/rihal:progress` | Visual progress + intelligent suggestion for next action. |
-| `/rihal:help [tier]` | This reference. Add `intermediate`, `advanced`, or `all` for more. |
+| `/rihal-init` | First-time setup in this repo. Detects state, asks config questions, writes `.rihal/RIHLA.md`. Run once per project. |
+| `/rihal-new-project` | Take an idea to a planned roadmap. Questioning → optional research → REQUIREMENTS → ROADMAP. |
+| `/rihal-plan <phase>` | Create executable plans for a phase. Produces `SPRINT.md` files. |
+| `/rihal-execute <phase>` | Run all plans in a phase in dependency waves. Updates STATE on completion. |
+| `/rihal-next` | Auto-route to the next logical step based on project state. Zero friction. |
+| `/rihal-status` | Where am I — current phase, plan progress, recent decisions, blockers. |
+| `/rihal-progress` | Visual progress + intelligent suggestion for next action. |
+| `/rihal-help [tier]` | This reference. Add `intermediate`, `advanced`, or `all` for more. |
 
 ## Minimal happy path
 
 ```
-/rihal:init
-/rihal:new-project
-/rihal:plan 1
-/rihal:execute 1
-/rihal:next
+/rihal-init
+/rihal-new-project
+/rihal-plan 1
+/rihal-execute 1
+/rihal-next
 ```
 
 ## Files Rihal creates
@@ -80,7 +80,7 @@ init → new-project → plan → execute → next → status → ship
         └── 01-01-SUMMARY.md  # what got done
 ```
 
-**Done with Tier 1?** → `/rihal:help intermediate` for council, review, ship, and capture.
+**Done with Tier 1?** → `/rihal-help intermediate` for council, review, ship, and capture.
 </tier-1>
 
 ---
@@ -95,46 +95,46 @@ init → new-project → plan → execute → next → status → ship
 
 | Command | When to use |
 |---------|-------------|
-| `/rihal:council <question>` | Strategic decision needing multiple perspectives — 3-5 agents debate in parallel, 2 rounds with cross-talk. |
-| `/rihal:discuss <agent> <q>` | Quick single-agent sync — fast, conversational, no artifact. |
-| `/rihal:discuss-phase <n>` | Gather context through adaptive questioning before planning. Produces CONTEXT.md. |
-| `/rihal:explore <topic>` | Socratic ideation — think through ideas before committing to plans. |
-| `/rihal:do <description>` | Smart router — natural language in, picks the right `/rihal:*` command. |
+| `/rihal-council <question>` | Strategic decision needing multiple perspectives — 3-5 agents debate in parallel, 2 rounds with cross-talk. |
+| `/rihal-discuss <agent> <q>` | Quick single-agent sync — fast, conversational, no artifact. |
+| `/rihal-discuss-phase <n>` | Gather context through adaptive questioning before planning. Produces CONTEXT.md. |
+| `/rihal-explore <topic>` | Socratic ideation — think through ideas before committing to plans. |
+| `/rihal-do <description>` | Smart router — natural language in, picks the right `/rihal-*` command. |
 
 ## Quality & shipping
 
 | Command | When to use |
 |---------|-------------|
-| `/rihal:code-review` | Adversarial code review of changed files — bugs, security, style. |
-| `/rihal:code-review-fix` | Auto-apply fixes from a code-review report. |
-| `/rihal:verify-phase <n>` | Goal-backward audit — does the codebase deliver what the phase promised? |
-| `/rihal:verify-work` | Conversational UAT against acceptance criteria. |
-| `/rihal:ship [phase] [--draft]` | Push feature branch + open PR with auto-generated body (goal, changes, requirements, verification status). Use AFTER `/rihal:verify-phase` passes. **Not for npm publish or tagging releases.** |
+| `/rihal-code-review` | Adversarial code review of changed files — bugs, security, style. |
+| `/rihal-code-review-fix` | Auto-apply fixes from a code-review report. |
+| `/rihal-verify-phase <n>` | Goal-backward audit — does the codebase deliver what the phase promised? |
+| `/rihal-verify-work` | Conversational UAT against acceptance criteria. |
+| `/rihal-ship [phase] [--draft]` | Push feature branch + open PR with auto-generated body (goal, changes, requirements, verification status). Use AFTER `/rihal-verify-phase` passes. **Not for npm publish or tagging releases.** |
 
 ## Phase & plan management
 
 | Command | When to use |
 |---------|-------------|
-| `/rihal:show <id>` | Print a phase or plan in full with execution status. |
-| `/rihal:add-phase <name>` | Append a new phase to the active milestone. |
-| `/rihal:insert-phase <after> <name>` | Insert urgent decimal phase (e.g. 7.1) without renumbering. |
-| `/rihal:remove-phase <n>` | Remove a future phase and renumber. |
-| `/rihal:quick [flags]` | Small ad-hoc tasks with Rihal guarantees but skip optional agents. Flags: `--discuss`, `--research`, `--full`. |
-| `/rihal:fast "<task>"` | Trivial inline task — typo, gitignore tweak, etc. No subagents, ≤3 file edits. |
+| `/rihal-show <id>` | Print a phase or plan in full with execution status. |
+| `/rihal-add-phase <name>` | Append a new phase to the active milestone. |
+| `/rihal-insert-phase <after> <name>` | Insert urgent decimal phase (e.g. 7.1) without renumbering. |
+| `/rihal-remove-phase <n>` | Remove a future phase and renumber. |
+| `/rihal-quick [flags]` | Small ad-hoc tasks with Rihal guarantees but skip optional agents. Flags: `--discuss`, `--research`, `--full`. |
+| `/rihal-fast "<task>"` | Trivial inline task — typo, gitignore tweak, etc. No subagents, ≤3 file edits. |
 
 ## Capture & session continuity
 
 | Command | When to use |
 |---------|-------------|
-| `/rihal:note "<text>"` | Zero-friction idea capture — appends to dated note file. |
-| `/rihal:add-todo [desc]` | Capture an idea or task as a todo (infers from conversation if no arg). |
-| `/rihal:check-todos [area]` | List pending todos and pick one to work on. |
-| `/rihal:plant-seed "<idea>"` | Capture a forward-looking idea with trigger conditions — surfaces at the right milestone. |
-| `/rihal:resume-work` | Restore project context after a break. |
-| `/rihal:pause-work` | Create HANDOFF.json and continue-here.md before stopping mid-phase. |
-| `/rihal:session-report` | Work summary, decisions, open blockers from this session. |
-
-**Done with Tier 2?** → `/rihal:help advanced` for audits, workspaces, milestone ops, and power variants.
+| `/rihal-note "<text>"` | Zero-friction idea capture — appends to dated note file. |
+| `/rihal-add-todo [desc]` | Capture an idea or task as a todo (infers from conversation if no arg). |
+| `/rihal-check-todos [area]` | List pending todos and pick one to work on. |
+| `/rihal-plant-seed "<idea>"` | Capture a forward-looking idea with trigger conditions — surfaces at the right milestone. |
+| `/rihal-resume-work` | Restore project context after a break. |
+| `/rihal-pause-work` | Create HANDOFF.json and continue-here.md before stopping mid-phase. |
+| `/rihal-session-report` | Work summary, decisions, open blockers from this session. |
+
+**Done with Tier 2?** → `/rihal-help advanced` for audits, workspaces, milestone ops, and power variants.
 </tier-2>
 
 ---
@@ -149,134 +149,134 @@ init → new-project → plan → execute → next → status → ship
 
 | Command | Use |
 |---------|-----|
-| `/rihal:new-milestone` | Start the next milestone — initializes ROADMAP, REQUIREMENTS, STATE. |
-| `/rihal:complete-milestone <ver>` | Archive milestone → move to `.planning/milestones/`. |
-| `/rihal:milestone-summary` | Human-readable summary of all phases, decisions, outcomes. |
-| `/rihal:audit-milestone` | Cross-phase audit — verify completion against original goals. |
-| `/rihal:plan-milestone-gaps` | Create phases to close gaps from the audit. |
-| `/rihal:cleanup` | Archive accumulated phase dirs from completed milestones. |
+| `/rihal-new-milestone` | Start the next milestone — initializes ROADMAP, REQUIREMENTS, STATE. |
+| `/rihal-complete-milestone <ver>` | Archive milestone → move to `.planning/milestones/`. |
+| `/rihal-milestone-summary` | Human-readable summary of all phases, decisions, outcomes. |
+| `/rihal-audit-milestone` | Cross-phase audit — verify completion against original goals. |
+| `/rihal-plan-milestone-gaps` | Create phases to close gaps from the audit. |
+| `/rihal-cleanup` | Archive accumulated phase dirs from completed milestones. |
 
 ## Workspaces & parallel work
 
 | Command | Use |
 |---------|-----|
-| `/rihal:new-workspace` | Isolated workspace with separate ROADMAP/STATE for parallel work. |
-| `/rihal:list-workspaces` | List all active workspaces. |
-| `/rihal:remove-workspace` | Delete a workspace and clean up artifacts. |
-| `/rihal:workstream` | Manage parallel workstreams (milestone tracks). |
+| `/rihal-new-workspace` | Isolated workspace with separate ROADMAP/STATE for parallel work. |
+| `/rihal-list-workspaces` | List all active workspaces. |
+| `/rihal-remove-workspace` | Delete a workspace and clean up artifacts. |
+| `/rihal-workstream` | Manage parallel workstreams (milestone tracks). |
 
 ## Audits & specialty review
 
 | Command | Use |
 |---------|-----|
-| `/rihal:secure-phase <n>` | Retroactively verify threat mitigations exist in code. |
-| `/rihal:validate-phase <n>` | Audit Nyquist validation gaps for a completed phase. |
-| `/rihal:add-tests <n>` | Generate unit + E2E tests based on SPRINT/SUMMARY/CONTEXT. |
-| `/rihal:audit-uat` | Cross-phase audit of all outstanding UAT items. |
-| `/rihal:audit-fix` | Autonomous audit-to-fix pipeline — find, classify, fix, test, commit. |
-| `/rihal:code-review --karpathy` | Audit recent code against Karpathy's 4 LLM coding principles. |
-| `/rihal:ui-phase <n>` | Generate UI design contract (UI-SPEC.md) for frontend phases. |
-| `/rihal:ui-review` | Retroactive 6-pillar visual audit of completed UI work. |
-| `/rihal:code-review --attack` | Hostile-perspective report — vulnerabilities, race conditions, abuse. |
-| `/rihal:code-review --edge-cases` | Enumerate edge cases by category and severity. |
-| `/rihal:review` | Cross-AI peer review — invoke external AI CLIs to review plans. |
+| `/rihal-secure-phase <n>` | Retroactively verify threat mitigations exist in code. |
+| `/rihal-validate-phase <n>` | Audit Nyquist validation gaps for a completed phase. |
+| `/rihal-add-tests <n>` | Generate unit + E2E tests based on SPRINT/SUMMARY/CONTEXT. |
+| `/rihal-audit-uat` | Cross-phase audit of all outstanding UAT items. |
+| `/rihal-audit-fix` | Autonomous audit-to-fix pipeline — find, classify, fix, test, commit. |
+| `/rihal-code-review --karpathy` | Audit recent code against Karpathy's 4 LLM coding principles. |
+| `/rihal-ui-phase <n>` | Generate UI design contract (UI-SPEC.md) for frontend phases. |
+| `/rihal-ui-review` | Retroactive 6-pillar visual audit of completed UI work. |
+| `/rihal-code-review --attack` | Hostile-perspective report — vulnerabilities, race conditions, abuse. |
+| `/rihal-code-review --edge-cases` | Enumerate edge cases by category and severity. |
+| `/rihal-review` | Cross-AI peer review — invoke external AI CLIs to review plans. |
 
 ## Council variants & strategy power tools
 
 | Command | Use |
 |---------|-----|
-| `/rihal:discuss-phase --power` | Bulk question generation with async UI for context-heavy phases. |
-| `/rihal:chain <preset> <topic>` | Sequential agent pipeline (research → scope → build), typed artifacts. |
-| `/rihal:brainstorm` | Guided brainstorming — pick a method, generate ideas systematically. |
-| `/rihal:why <decision>` | Explain reasoning behind a decision, classification, or panel pick. |
+| `/rihal-discuss-phase --power` | Bulk question generation with async UI for context-heavy phases. |
+| `/rihal-chain <preset> <topic>` | Sequential agent pipeline (research → scope → build), typed artifacts. |
+| `/rihal-brainstorm` | Guided brainstorming — pick a method, generate ideas systematically. |
+| `/rihal-why <decision>` | Explain reasoning behind a decision, classification, or panel pick. |
 
 ## Document, scaffold, integrate
 
 | Command | Use |
 |---------|-----|
-| `/rihal:map-codebase` | Brownfield: parallel Explore agents → 7 codebase docs. |
-| `/rihal:scan` | Rapid codebase assessment — lighter than map-codebase. |
-| `/rihal:document-project` | Audit missing/stale docs, file SPRINT tasks for each gap. |
-| `/rihal:docs-update` | Generate or update docs verified against codebase. |
-| `/rihal:install <module>` | Install a Rihal capability bundle into the project. |
-| `/rihal:enable-hooks` | Install optional Rihal hooks into `.claude/settings.json`. |
-| `/rihal:scaffold-project` | Scaffold a new project from the official Rihal template. |
-| `/rihal:bootstrap` | Bootstrap repo with Vercel-linked resources and integrations. |
+| `/rihal-map-codebase` | Brownfield: parallel Explore agents → 7 codebase docs. |
+| `/rihal-scan` | Rapid codebase assessment — lighter than map-codebase. |
+| `/rihal-document-project` | Audit missing/stale docs, file SPRINT tasks for each gap. |
+| `/rihal-docs-update` | Generate or update docs verified against codebase. |
+| `/rihal-install <module>` | Install a Rihal capability bundle into the project. |
+| `/rihal-enable-hooks` | Install optional Rihal hooks into `.claude/settings.json`. |
+| `/rihal-scaffold-project` | Scaffold a new project from the official Rihal template. |
+| `/rihal-bootstrap` | Bootstrap repo with Vercel-linked resources and integrations. |
 
 ## Story-level epics workflow
 
 | Command | Use |
 |---------|-----|
-| `/rihal:create-prd` | Create a PRD from scratch through guided facilitation. |
-| `/rihal:edit-prd` | Update an existing PRD with revisions or clarifications. |
-| `/rihal:validate-prd` | Validate an existing PRD for completeness and consistency. |
-| `/rihal:create-epics-and-stories` | Parse a PRD into numbered epic + story files. |
-| `/rihal:create-story` | Prepare a dev-ready STORY.md with full implementation context. |
-| `/rihal:dev-story <file>` | Execute an approved STORY by writing tests + code per AC. |
-| (internal) `check-implementation-readiness` | Guard called by `/rihal:plan` and `/rihal:execute` to verify PRD + architecture aligned before build. |
-| `/rihal:create-architecture` | Write an Architecture Decision Record (ADR). |
-| `/rihal:create-ux-design` | Realize a UX design that informs architecture and implementation. |
-| `/rihal:correct-course` | Course-correct mid-sprint when major change is discovered. |
-| `/rihal:sprint-planning` | Compute capacity, prioritize stories, create SPRINT.md. |
-| `/rihal:sprint-status` | Sprint progress — stories, points, velocity, burndown. |
-| `/rihal:list-plans` | Table of every SPRINT.md across phases — goal, stories, points, state. |
-| `/rihal:decisions` | Browse decisions across every Rihal project (~/.rihal/decisions.jsonl). |
-| `/rihal:replay <slug>` | Re-run a past council session with the same question — fresh panel round. |
-| `/rihal:export-to-github` | Push phases/stories/decisions to GitHub issues (wraps `rihal-code github-sync`). |
-| `/rihal:notify-test` | Verify Slack/Discord/MS Teams webhook wiring — posts a test message. |
-| `/rihal:from-template <type>` | Seed .planning/ from a starter template (saas-b2b, api-backend, mobile-app). |
-| `/rihal:retrospective` | Run an epic retrospective and produce owned action items. |
+| `/rihal-create-prd` | Create a PRD from scratch through guided facilitation. |
+| `/rihal-edit-prd` | Update an existing PRD with revisions or clarifications. |
+| `/rihal-validate-prd` | Validate an existing PRD for completeness and consistency. |
+| `/rihal-create-epics-and-stories` | Parse a PRD into numbered epic + story files. |
+| `/rihal-create-story` | Prepare a dev-ready STORY.md with full implementation context. |
+| `/rihal-dev-story <file>` | Execute an approved STORY by writing tests + code per AC. |
+| (internal) `check-implementation-readiness` | Guard called by `/rihal-plan` and `/rihal-execute` to verify PRD + architecture aligned before build. |
+| `/rihal-create-architecture` | Write an Architecture Decision Record (ADR). |
+| `/rihal-create-ux-design` | Realize a UX design that informs architecture and implementation. |
+| `/rihal-correct-course` | Course-correct mid-sprint when major change is discovered. |
+| `/rihal-sprint-planning` | Compute capacity, prioritize stories, create SPRINT.md. |
+| `/rihal-sprint-status` | Sprint progress — stories, points, velocity, burndown. |
+| `/rihal-list-plans` | Table of every SPRINT.md across phases — goal, stories, points, state. |
+| `/rihal-decisions` | Browse decisions across every Rihal project (~/.rihal/decisions.jsonl). |
+| `/rihal-replay <slug>` | Re-run a past council session with the same question — fresh panel round. |
+| `/rihal-export-to-github` | Push phases/stories/decisions to GitHub issues (wraps `rihal-code github-sync`). |
+| `/rihal-notify-test` | Verify Slack/Discord/MS Teams webhook wiring — posts a test message. |
+| `/rihal-from-template <type>` | Seed .planning/ from a starter template (saas-b2b, api-backend, mobile-app). |
+| `/rihal-retrospective` | Run an epic retrospective and produce owned action items. |
 
 ## Operational / rare
 
 | Command | Use |
 |---------|-----|
-| `/rihal:debug "<issue>"` | Systematic debugging with persistent state across `/clear`. |
-| `/rihal:forensics` | Diagnose incomplete executions — timeline of what broke. |
-| `/rihal:undo <id>` | Safe git revert for a phase or plan with dependency checks. |
-| `/rihal:rerun <id>` | Re-execute a phase or plan, resetting state, fresh commits. |
-| `/rihal:diff <a> <b>` | Show changes to plans and state between commits. |
-| `/rihal:import <path>` | Ingest external plans with conflict detection against decisions. |
-| `/rihal:inbox` | Triage incoming issues and PRs against contribution templates. |
-| `/rihal:pr-branch` | Create clean PR branch — filter out `.planning/` commits. |
-| `/rihal:autonomous` | Run remaining phases autonomously — plan → execute → verify cycles. |
-| `/rihal:research-phase <n>` | Standalone research (usually use `/rihal:plan` instead). |
-| `/rihal:analyze-dependencies` | Suggest "Depends on" entries for ROADMAP.md. |
-| `/rihal:list-phase-assumptions <n>` | Surface agent's intended approach before planning. |
-| `/rihal:profile-user` | Classify developer on 4 dimensions, produce profile artifact. |
-| `/rihal:dashboard` | Start the Diwan view-only dashboard (port 7717). |
-| `/rihal:health` | 6-point health check of the Rihal installation. |
-| `/rihal:stats` | Phases, plans, decisions, council sessions, timeline. |
-| `/rihal:settings` | Interactive config wizard — model profile, gates, branching. |
-| `/rihal:config` | View or edit Rihal configuration directly. |
-| `/rihal:update` | Update Rihal to latest version with changelog preview. |
-| `/rihal:note` | (also Tier 2) Inline note capture. |
+| `/rihal-debug "<issue>"` | Systematic debugging with persistent state across `/clear`. |
+| `/rihal-forensics` | Diagnose incomplete executions — timeline of what broke. |
+| `/rihal-undo <id>` | Safe git revert for a phase or plan with dependency checks. |
+| `/rihal-rerun <id>` | Re-execute a phase or plan, resetting state, fresh commits. |
+| `/rihal-diff <a> <b>` | Show changes to plans and state between commits. |
+| `/rihal-import <path>` | Ingest external plans with conflict detection against decisions. |
+| `/rihal-inbox` | Triage incoming issues and PRs against contribution templates. |
+| `/rihal-pr-branch` | Create clean PR branch — filter out `.planning/` commits. |
+| `/rihal-autonomous` | Run remaining phases autonomously — plan → execute → verify cycles. |
+| `/rihal-research-phase <n>` | Standalone research (usually use `/rihal-plan` instead). |
+| `/rihal-analyze-dependencies` | Suggest "Depends on" entries for ROADMAP.md. |
+| `/rihal-list-phase-assumptions <n>` | Surface agent's intended approach before planning. |
+| `/rihal-profile-user` | Classify developer on 4 dimensions, produce profile artifact. |
+| `/rihal-dashboard` | Start the Diwan view-only dashboard (port 7717). |
+| `/rihal-health` | 6-point health check of the Rihal installation. |
+| `/rihal-stats` | Phases, plans, decisions, council sessions, timeline. |
+| `/rihal-settings` | Interactive config wizard — model profile, gates, branching. |
+| `/rihal-config` | View or edit Rihal configuration directly. |
+| `/rihal-update` | Update Rihal to latest version with changelog preview. |
+| `/rihal-note` | (also Tier 2) Inline note capture. |
 
 ## Common compound flows
 
 **New project (full quality):**
 ```
-/rihal:new-project → /clear → /rihal:plan 1 → /clear → /rihal:execute 1 → /rihal:verify-phase 1 → /rihal:ship
+/rihal-new-project → /clear → /rihal-plan 1 → /clear → /rihal-execute 1 → /rihal-verify-phase 1 → /rihal-ship
 ```
 
 **Mid-milestone urgent work:**
 ```
-/rihal:insert-phase 5 "Critical security fix" → /rihal:plan 5.1 → /rihal:execute 5.1
+/rihal-insert-phase 5 "Critical security fix" → /rihal-plan 5.1 → /rihal-execute 5.1
 ```
 
 **Resume after break:**
 ```
-/rihal:resume-work   # or just /rihal:next
+/rihal-resume-work   # or just /rihal-next
 ```
 
 **Debug across context resets:**
 ```
-/rihal:debug "form submission fails" → ...investigation... → /clear → /rihal:debug   # resumes
+/rihal-debug "form submission fails" → ...investigation... → /clear → /rihal-debug   # resumes
 ```
 
 **Complete + start next milestone:**
 ```
-/rihal:audit-milestone → /rihal:plan-milestone-gaps → /rihal:complete-milestone 1.0.0 → /rihal:new-milestone
+/rihal-audit-milestone → /rihal-plan-milestone-gaps → /rihal-complete-milestone 1.0.0 → /rihal-new-milestone
 ```
 
 ## Configuration reference

package/rihal/workflows/import.md

@@ -14,13 +14,13 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:import --from <path>
+/rihal-import --from <path>
 ```
 
 **Examples:**
 ```
-/rihal:import --from ./external-plan.md
-/rihal:import --from ../other-project/SPRINT.md
+/rihal-import --from ./external-plan.md
+/rihal-import --from ../other-project/SPRINT.md
 ```
 
 ---
@@ -49,7 +49,7 @@ Parse `$ARGUMENTS` to determine the execution mode:
 - If neither flag is found: display usage and exit:
 
 ```
-Usage: /rihal:import --from <path>
+Usage: /rihal-import --from <path>
 
   --from <path>   Import an external plan file into Rihal format
 ```

package/rihal/workflows/inbox.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:inbox
+# Workflow: rihal-inbox
 
 <purpose>
 Triage and review all open GitHub issues and PRs against project contribution templates.
@@ -12,13 +12,13 @@ required fields, identifies label gaps, and optionally takes action (label, comm
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:inbox <argument-here>
+/rihal-inbox <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:inbox example 1
-/rihal:inbox example 2
+/rihal-inbox example 1
+/rihal-inbox example 2
 ```
 
 STOP — do not proceed.
@@ -386,10 +386,10 @@ Next steps:
 <offer_next>
 After triage:
 
-- /rihal:review — Run cross-AI peer review on a specific phase plan
-- /rihal:ship — Create a PR from completed work
-- /rihal:progress — See overall project state
-- /rihal:inbox --label — Re-run with auto-labeling enabled
+- /rihal-review — Run cross-AI peer review on a specific phase plan
+- /rihal-ship — Create a PR from completed work
+- /rihal-progress — See overall project state
+- /rihal-inbox --label — Re-run with auto-labeling enabled
 </offer_next>
 
 <success_criteria>

package/rihal/workflows/init.md

@@ -1,9 +1,9 @@
-# Workflow: rihal:init
+# Workflow: rihal-init
 
 <purpose>
 Begin the rihla. This is the first command a user runs after dropping Rihal files into a project. It detects project state, asks a handful of configuration questions, scans existing context (if any), writes `.rihal/RIHLA.md` as the journey baseline, and routes to the right next command.
 
-This replaces the older `/rihal:generate-project-context` workflow — init is the single entry point for configuring Rihal in a project.
+This replaces the older `/rihal-generate-project-context` workflow — init is the single entry point for configuring Rihal in a project.
 </purpose>
 
 ## Step 0 — Usage check
@@ -11,15 +11,15 @@ This replaces the older `/rihal:generate-project-context` workflow — init is t
 If `$ARGUMENTS` contains only `--help` or `-h`:
 
 ```
-Usage: /rihal:init [--reset] [--skip-scan]
+Usage: /rihal-init [--reset] [--skip-scan]
 
   --reset        overwrite existing .rihal/config.yaml and RIHLA.md
   --skip-scan    skip the codebase scan step
 
 Examples:
-  /rihal:init                  # first-time setup for this project
-  /rihal:init --reset          # reconfigure from scratch
-  /rihal:init --skip-scan      # config only, no codebase read
+  /rihal-init                  # first-time setup for this project
+  /rihal-init --reset          # reconfigure from scratch
+  /rihal-init --skip-scan      # config only, no codebase read
 ```
 
 STOP here if just help was requested.
@@ -56,9 +56,9 @@ Classify project into one of four states:
 
 | State | Signal | Suggested next step |
 |-------|--------|---------------------|
-| `fresh` | No code, no git, no rihal | `/rihal:new-project` — let's design it |
-| `existing-new-rihal` | Has code + git, no rihal | `/rihal:scan` or `/rihal:council` — understand before changing |
-| `returning` | Rihal already configured | `/rihal:resume-work` or `/rihal:next` |
+| `fresh` | No code, no git, no rihal | `/rihal-new-project` — let's design it |
+| `existing-new-rihal` | Has code + git, no rihal | `/rihal-scan` or `/rihal-council` — understand before changing |
+| `returning` | Rihal already configured | `/rihal-resume-work` or `/rihal-next` |
 | `reset` | User passed `--reset` flag | Proceed with full reconfigure |
 
 Print one-line state summary:
@@ -73,9 +73,9 @@ If `state === "returning"` and `--reset` not passed:
 ✓ Rihal is already configured here.
 
 What next?
-  /rihal:resume-work    — pick up where you left off
-  /rihal:status         — see the dashboard
-  /rihal:next           — suggested next action
+  /rihal-resume-work    — pick up where you left off
+  /rihal-status         — see the dashboard
+  /rihal-next           — suggested next action
 
 Or run with --reset to reconfigure.
 ```
@@ -126,9 +126,9 @@ test -f .rihal/state.json || node .rihal/bin/rihal-tools.cjs state init --projec
 
 ## Step 4 — Scan existing context (skip if `--skip-scan`)
 
-If the project has code (from Step 1 detection), produce `.rihal/RIHLA.md`. This is the journey baseline — a lightweight snapshot, not a full audit. Use `/rihal:map-codebase` or `/rihal:scan` later for deep analysis.
+If the project has code (from Step 1 detection), produce `.rihal/RIHLA.md`. This is the journey baseline — a lightweight snapshot, not a full audit. Use `/rihal-map-codebase` or `/rihal-scan` later for deep analysis.
 
-**Memory-bank refresh on `--reset`.** When `--reset` is passed AND `.planning/codebase/` already contains docs from a previous scan, also chain to `/rihal:scan --refresh --focus tech+arch` immediately after writing RIHLA.md. The refresh path:
+**Memory-bank refresh on `--reset`.** When `--reset` is passed AND `.planning/codebase/` already contains docs from a previous scan, also chain to `/rihal-scan --refresh --focus tech+arch` immediately after writing RIHLA.md. The refresh path:
 
 - Captures pre-state (commits since last doc mtime, manifest hashes, top-level dirs).
 - Briefs the user on what changed since the last scan.
@@ -160,7 +160,7 @@ Write `.rihal/RIHLA.md` following this template (don't over-interpret — just r
 <!-- RIHLA (رحلة) = "the journey". Not a typo of RIHAL (رحّال) = "the traveler" / the tool itself. Same root, different word. This file documents your project's journey; Rihal is the tool that walks it with you. -->
 # RIHLA — Project journey baseline
 
-**Written by:** /rihal:init
+**Written by:** /rihal-init
 **Date:** {ISO date}
 **Project:** {project_name}
 **Detected state:** {fresh | existing-new-rihal | returning}
@@ -187,9 +187,9 @@ Write `.rihal/RIHLA.md` following this template (don't over-interpret — just r
 ## Not scanned
 
 This file is a journey baseline — intentionally shallow. For deep analysis run:
-- `/rihal:map-codebase` — structured codebase documents per focus area
-- `/rihal:scan` — rapid codebase assessment
-- `/rihal:explore` — socratic ideation against the codebase
+- `/rihal-map-codebase` — structured codebase documents per focus area
+- `/rihal-scan` — rapid codebase assessment
+- `/rihal-explore` — socratic ideation against the codebase
 ```
 
 If no code detected, write a minimal RIHLA.md with just the header and a "fresh project — no code yet" note.
@@ -204,11 +204,11 @@ Print a contextual recommendation, **one line of copy-paste per suggestion** (pe
 
 Ready to design a new project? Try:
 
-/rihal:new-project {your-project-name}
+/rihal-new-project {your-project-name}
 
 Or think through an idea first:
 
-/rihal:explore what should I build?
+/rihal-explore what should I build?
 ```
 
 **If `existing-new-rihal`:**
@@ -217,11 +217,11 @@ Or think through an idea first:
 
 Recommended first move — understand before changing:
 
-/rihal:scan
+/rihal-scan
 
 Or strategic question about the codebase:
 
-/rihal:council {your question}
+/rihal-council {your question}
 ```
 
 **If `returning` with `--reset`:**
@@ -230,7 +230,7 @@ Or strategic question about the codebase:
 
 Pick up where you left off:
 
-/rihal:resume-work
+/rihal-resume-work
 ```
 
 ## Step 6 — Update state

package/rihal/workflows/insert-phase.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:insert-phase
+# Workflow: rihal-insert-phase
 
 <purpose>
 Insert a decimal phase for urgent work discovered mid-milestone between existing integer phases. Uses decimal numbering (2.1, 2.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions without renumbering subsequent phases. Maintains phase array in `.rihal/state.json` in sort order.
@@ -12,14 +12,14 @@ If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 **Usage:**
 ```
-/rihal:insert-phase <N.M> <name>
+/rihal-insert-phase <N.M> <name>
 ```
 
 **Examples:**
 ```
-/rihal:insert-phase 2.1 urgent-fix
-/rihal:insert-phase 3.2 critical-security-patch
-/rihal:insert-phase 1.1 blocking-issue
+/rihal-insert-phase 2.1 urgent-fix
+/rihal-insert-phase 3.2 critical-security-patch
+/rihal-insert-phase 1.1 blocking-issue
 ```
 
 Only after the user provides arguments, proceed to Step 0.5.
@@ -33,7 +33,7 @@ Validate using regex: `^\d+\.\d+$`
 If validation fails:
 ```
 ERROR: Phase number must be in N.M format (e.g., 2.1, 3.2)
-Usage: /rihal:insert-phase <N.M> <name>
+Usage: /rihal-insert-phase <N.M> <name>
 ```
 
 Exit.
@@ -77,8 +77,8 @@ Present completion summary:
   Status: Ready for planning
 
 Next steps:
-  /rihal:discuss-phase {phase_number}   — gather context
-  /rihal:plan {phase_number}            — create detailed plan
+  /rihal-discuss-phase {phase_number}   — gather context
+  /rihal-plan {phase_number}            — create detailed plan
 
 Or continue with current work and return to this phase later.
 ```
@@ -87,7 +87,7 @@ Or continue with current work and return to this phase later.
 
 - Don't insert before Phase 1 (decimal 0.1 makes no sense)
 - Don't renumber existing phases
-- Don't create plans yet (that's `/rihal:plan`)
+- Don't create plans yet (that's `/rihal-plan`)
 - Don't commit changes (user decides when to commit)
 - Don't duplicate phase numbers (state insert-phase prevents this)
 

package/rihal/workflows/install.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:install
+# Workflow: rihal-install
 
 <purpose>
 Install a Rihal module into the current project. Modules are capability bundles (agents + workflows + commands + references). This workflow validates the module exists, checks dependencies, runs the installer, and updates the manifest.
@@ -38,7 +38,7 @@ CHECK=$(node .rihal/bin/rihal-tools.cjs module check-requires {name})
 If `ok` is false:
 ```
 Module '{name}' requires '{missing_module}' to be installed first.
-Run: /rihal:install {missing_module}
+Run: /rihal-install {missing_module}
 ```
 And stop.
 
@@ -65,7 +65,7 @@ fi
    {description from module manifest}
 
 New commands available:
-  /rihal:{command} — {description}
+  /rihal-{command} — {description}
 ```
 
 ## Success Criteria