@hanzlaa/rcode 3.3.0 → 3.3.2

package/rihal/workflows/audit.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:audit
+# Workflow: rihal-audit
 
 <purpose>
 Single entry point for every kind of audit. Asks the user *what* to audit
@@ -17,20 +17,20 @@ and auto-picks the most-relevant target based on project state. In
 If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
-/rihal:audit                       # interactive — asks what to audit
-/rihal:audit phase [<NN>]          # → /rihal:verify-phase
-/rihal:audit milestone [--strict]  # → /rihal:audit-milestone (with synth fallback)
-/rihal:audit uat                   # → /rihal:audit-uat
-/rihal:audit code [--scope=...]    # → /rihal:code-review --karpathy
-/rihal:audit fix                   # → /rihal:audit-fix
-/rihal:audit work                  # → /rihal:verify-work
+/rihal-audit                       # interactive — asks what to audit
+/rihal-audit phase [<NN>]          # → /rihal-verify-phase
+/rihal-audit milestone [--strict]  # → /rihal-audit-milestone (with synth fallback)
+/rihal-audit uat                   # → /rihal-audit-uat
+/rihal-audit code [--scope=...]    # → /rihal-code-review --karpathy
+/rihal-audit fix                   # → /rihal-audit-fix
+/rihal-audit work                  # → /rihal-verify-work
 ```
 
 **Examples:**
 ```
-/rihal:audit
-/rihal:audit milestone --strict
-/rihal:audit phase 03
+/rihal-audit
+/rihal-audit milestone --strict
+/rihal-audit phase 03
 ```
 
 ## Step 1 — Resolve mode + arguments
@@ -94,11 +94,11 @@ sub-workflow.
 
 | target | precondition | failure message |
 |---|---|---|
-| phase | at least one `.planning/phases/*/PLAN.md` | `No PLAN.md found. Run /rihal:plan first.` |
-| milestone | ROADMAP.md exists | `No ROADMAP.md. Run /rihal:new-milestone first.` |
-| uat | at least one UAT*.md exists | `No UAT files yet. Run /rihal:execute on a phase first.` |
+| phase | at least one `.planning/phases/*/PLAN.md` | `No PLAN.md found. Run /rihal-plan first.` |
+| milestone | ROADMAP.md exists | `No ROADMAP.md. Run /rihal-new-milestone first.` |
+| uat | at least one UAT*.md exists | `No UAT files yet. Run /rihal-execute on a phase first.` |
 | code | git repo with at least one commit | `Empty repo — nothing to audit yet.` |
-| fix | a prior audit report exists OR a prior `--report` artefact | `No audit findings yet. Run /rihal:audit first.` |
+| fix | a prior audit report exists OR a prior `--report` artefact | `No audit findings yet. Run /rihal-audit first.` |
 | work | inside a git worktree | `Not in a git repo.` |
 
 For `milestone` specifically, check the **graceful-degrade** condition
@@ -112,7 +112,7 @@ if [ "$TARGET" = "milestone" ] && [ "$SUMMARIES" -eq 0 ] && [ "$PLANS" -gt 0 ];
   echo "  Phases were executed but never formally closed."
   # Offer (yolo: auto-pick 1; guided: ask):
   #   1. Synthesize SUMMARY.md per phase from PLAN.md + git log    [recommended]
-  #   2. Run /rihal:verify-phase per phase (manual close)
+  #   2. Run /rihal-verify-phase per phase (manual close)
   #   3. Continue audit anyway (will only assess what's documented)
   #   0. Cancel
 fi
@@ -135,12 +135,12 @@ Run the target's slash command, forwarding remaining args:
 
 | target | dispatch |
 |---|---|
-| phase | `/rihal:verify-phase $REST_ARGS` |
-| milestone | `/rihal:audit-milestone $REST_ARGS` |
-| uat | `/rihal:audit-uat $REST_ARGS` |
-| code | `/rihal:code-review $REST_ARGS --karpathy` |
-| fix | `/rihal:audit-fix $REST_ARGS` |
-| work | `/rihal:verify-work $REST_ARGS` |
+| phase | `/rihal-verify-phase $REST_ARGS` |
+| milestone | `/rihal-audit-milestone $REST_ARGS` |
+| uat | `/rihal-audit-uat $REST_ARGS` |
+| code | `/rihal-code-review $REST_ARGS --karpathy` |
+| fix | `/rihal-audit-fix $REST_ARGS` |
+| work | `/rihal-verify-work $REST_ARGS` |
 
 ## Step 6 — Closing summary
 
@@ -153,20 +153,20 @@ Report: {report_path or "(stdout only)"}
 Findings: {count}
 
 Next:
-  /rihal:audit fix         — auto-fix findings classified as auto-fixable
-  /rihal:audit code        — drill into code-quality issues
-  /rihal:settings show     — review which audit gates are enabled
+  /rihal-audit fix         — auto-fix findings classified as auto-fixable
+  /rihal-audit code        — drill into code-quality issues
+  /rihal-settings show     — review which audit gates are enabled
 ```
 
 ## Success Criteria
 
-- [ ] `/rihal:audit` (no args) presents menu in guided mode, auto-picks in yolo
-- [ ] `/rihal:audit milestone` short-circuits the menu
+- [ ] `/rihal-audit` (no args) presents menu in guided mode, auto-picks in yolo
+- [ ] `/rihal-audit milestone` short-circuits the menu
 - [ ] When SUMMARY.md absent but PLAN.md present, milestone offers synthesize/verify/skip — does not dead-halt
 - [ ] Sub-workflow's closing report is surfaced unchanged
 
 ## On Error
 
-- **Sub-workflow not installed** (slash file missing): `Audit subroute '/rihal:{target}' not found. Run: npx @hanzlaa/rcode install .`
+- **Sub-workflow not installed** (slash file missing): `Audit subroute '/rihal-{target}' not found. Run: npx @hanzlaa/rcode install .`
 - **Precondition failed**: print the message from Step 4's table, suggest the unblocking command, STOP.
 - **`.rihal/config.yaml` missing**: treat as `mode: guided`, continue.

package/rihal/workflows/autonomous.md

@@ -17,9 +17,9 @@ interpos audit (issue #221) — DO NOT regress.
 
 2. **NEVER skip the methodology chain on greenfield projects.** Before
    the phase loop runs, the prerequisite check (next step) MUST verify:
-   - `.planning/prd.md` exists (else halt → /rihal:create-prd)
-   - ROADMAP.md has milestone structure (else halt → /rihal:create-milestone)
-   - `.planning/epics.md` exists (else halt → /rihal:create-epics-and-stories)
+   - `.planning/prd.md` exists (else halt → /rihal-create-prd)
+   - ROADMAP.md has milestone structure (else halt → /rihal-create-milestone)
+   - `.planning/epics.md` exists (else halt → /rihal-create-epics-and-stories)
    See issue #219 + #229.
 
 3. **NEVER write SPRINT.md directly.** Sprint creation MUST go through
@@ -66,44 +66,67 @@ If `SKIP_FLAG=false` AND any prerequisite is missing, HALT with a clear message:
 ⚠ Cannot run autonomous: missing prerequisite — {what}.
 
 The autonomous flow assumes a project that has already gone through:
-  1. /rihal:create-prd               → produces .planning/prd.md
-  2. /rihal:create-milestone         → produces ROADMAP.md with M1..Mn
-  3. /rihal:create-epics-and-stories → produces .planning/epics.md
-  4. THEN /rihal:autonomous           ← you are here
+  1. /rihal-create-prd               → produces .planning/prd.md
+  2. /rihal-create-milestone         → produces ROADMAP.md with M1..Mn
+  3. /rihal-create-epics-and-stories → produces .planning/epics.md
+  4. THEN /rihal-autonomous           ← you are here
 
-Suggested first step: /rihal:{first-missing-command}
+Suggested first step: /rihal-{first-missing-command}
 
 If you genuinely want to skip these (rare — usually inverted methodology),
-re-invoke with: /rihal:autonomous --skip-prerequisites
+re-invoke with: /rihal-autonomous --skip-prerequisites
 ```
 
 If `SKIP_FLAG=true`: print a warning that downstream workflows may produce low-quality output without upstream artifacts, then proceed.
 
 </step>
 
-<output_format>
+<step name="prepare_branch">
 
-Open with banner:
+## 1b. Prepare Branch
 
+Autonomous mode MUST NOT run directly on `main` or `master` without explicit opt-in.
+This prevents accidental commits to the default branch during long autonomous runs.
+
+```bash
+CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "unknown")
+ALLOW_MAIN=""
+if echo "$ARGUMENTS" | grep -q '\-\-allow-main'; then
+  ALLOW_MAIN="true"
+fi
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- RIHAL ► AUTONOMOUS
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**If `CURRENT_BRANCH` is `main` or `master` AND `ALLOW_MAIN` is NOT set:**
+
+Create a working branch:
+
+```bash
+BRANCH_NAME="rihal/autonomous-${milestone_version}-$(date +%Y%m%d-%H%M%S)"
+git checkout -b "${BRANCH_NAME}"
 ```
 
-Per-phase banners:
-- `RIHAL ► AUTONOMOUS ▸ Phase {N}/{T}: {Name} [████░░░░] {P}%`
-- `RIHAL ► AUTONOMOUS ▸ LIFECYCLE`
-- `RIHAL ► AUTONOMOUS ▸ COMPLETE 🎉`
-- `RIHAL ► AUTONOMOUS ▸ STOPPED` on blocker
-- `RIHAL ► AUTONOMOUS ▸ --to ${TO_PHASE} REACHED` on range completion
-- `RIHAL ► AUTONOMOUS ▸ PHASE ${ONLY_PHASE} COMPLETE ✓` on --only
+Display:
 
-Use TaskCreate: one entry per phase in `todo_phases`. Mark in_progress one at a time; mark completed immediately after each phase finishes.
+```
+🔀 Created branch: ${BRANCH_NAME}
+   (autonomous mode does not run on main/master — use --allow-main to override)
+```
+
+**If `CURRENT_BRANCH` is `main` or `master` AND `ALLOW_MAIN` is set:**
+
+Display warning:
+
+```
+⚠ Running on ${CURRENT_BRANCH} — --allow-main override active
+```
 
-</output_format>
+Proceed without branch creation.
 
-<process>
+**If `CURRENT_BRANCH` is any other branch:** Proceed silently — user intentionally set up a working branch.
+
+Store `CURRENT_BRANCH` for the lifecycle step — if autonomous created the branch, it will suggest a PR at completion.
+
+</step>
 
 <step name="initialize" priority="first">
 
@@ -148,8 +171,8 @@ STATE=$(node .rihal/bin/rihal-tools.cjs state read 2>/dev/null || echo '{}')
 
 Parse JSON for: `milestone_version`, `milestone_name`, `phase_count`, `completed_phases`, `roadmap_exists`, `state_exists`, `commit_docs`.
 
-**If `roadmap_exists` is false:** Error — "No ROADMAP.md found. Run `/rihal:new-milestone` first."
-**If `state_exists` is false:** Error — "No STATE.md found. Run `/rihal:new-milestone` first."
+**If `roadmap_exists` is false:** Error — "No ROADMAP.md found. Run `/rihal-new-milestone` first."
+**If `state_exists` is false:** Error — "No STATE.md found. Run `/rihal-new-milestone` first."
 
 Display startup banner:
 
@@ -243,6 +266,16 @@ Use TaskCreate to register a task per incomplete phase.
 
 ## 3. Execute Phase
 
+**Before displaying the banner, re-derive T from disk** (compaction guard — same
+logic as iterate step 4.0):
+
+```bash
+PROGRESS_REFRESH=$(node .rihal/bin/rihal-tools.cjs progress init 2>/dev/null)
+```
+
+Update `phase_count` and `completed_phases` from the refresh. This ensures
+the banner always shows the correct total, even after context compaction.
+
 For the current phase, display the progress banner:
 
 ```
@@ -349,7 +382,7 @@ The discuss step in autonomous mode MUST NOT loop. If CONTEXT.md already exists
 **If `INTERACTIVE` is set:** Run the standard discuss-phase skill inline (asks interactive questions, waits for user answers):
 
 ```
-Skill(skill="rihal:discuss-phase", args="${PHASE_NUM}")
+Skill(skill="rihal-discuss-phase", args="${PHASE_NUM}")
 ```
 
 **If `INTERACTIVE` is NOT set:** Execute the smart_discuss step for this phase (batch table proposals, auto-optimized — see smart_discuss step below).
@@ -377,7 +410,7 @@ Phase ${PHASE_NUM}: Frontend phase detected — generating UI design contract...
 ```
 
 ```
-Skill(skill="rihal:ui-phase", args="${PHASE_NUM}")
+Skill(skill="rihal-ui-phase", args="${PHASE_NUM}")
 ```
 
 Verify UI-SPEC was created. If still empty after ui-phase, display a non-blocking warning and proceed to 3b.
@@ -393,7 +426,7 @@ Task(
   description="Plan phase ${PHASE_NUM}: ${PHASE_NAME}",
   subagent_type="rihal-planner",
   run_in_background=true,
-  prompt="Run plan-phase for phase ${PHASE_NUM}: Skill(skill=\"rihal:plan\", args=\"${PHASE_NUM}\")"
+  prompt="Run plan-phase for phase ${PHASE_NUM}: Skill(skill=\"rihal-plan\", args=\"${PHASE_NUM}\")"
 )
 ```
 
@@ -402,7 +435,7 @@ Store the agent task_id. After discuss for the next phase completes (or if no ne
 **If `INTERACTIVE` is NOT set (default):** Run plan inline as before.
 
 ```
-Skill(skill="rihal:plan", args="${PHASE_NUM}")
+Skill(skill="rihal-plan", args="${PHASE_NUM}")
 ```
 
 Verify plan produced output — check `${PHASE_DIR}` for `*-PLAN.md` or `SPRINT.md`. If none → go to handle_blocker: "Plan phase ${PHASE_NUM} did not produce any plans."
@@ -416,7 +449,7 @@ Task(
   description="Execute phase ${PHASE_NUM}: ${PHASE_NAME}",
   subagent_type="rihal-executor",
   run_in_background=true,
-  prompt="Run execute-phase for phase ${PHASE_NUM}: Skill(skill=\"rihal:execute\", args=\"${PHASE_NUM} --no-transition\")"
+  prompt="Run execute-phase for phase ${PHASE_NUM}: Skill(skill=\"rihal-execute\", args=\"${PHASE_NUM} --no-transition\")"
 )
 ```
 
@@ -425,7 +458,7 @@ Store the agent task_id. The workflow can now start discussing the next phase wh
 **If `INTERACTIVE` is NOT set (default):** Run execute inline as before.
 
 ```
-Skill(skill="rihal:execute", args="${PHASE_NUM} --no-transition")
+Skill(skill="rihal-execute", args="${PHASE_NUM} --no-transition")
 ```
 
 ### 3c.5. Code Review and Fix
@@ -439,12 +472,12 @@ CODE_REVIEW_ENABLED=$(node .rihal/bin/rihal-tools.cjs config 2>/dev/null | grep
 If `"false"`: display "Code review skipped (workflow.code_review=false)" and proceed to 3d.
 
 ```
-Skill(skill="rihal:code-review", args="${PHASE_NUM}")
+Skill(skill="rihal-code-review", args="${PHASE_NUM}")
 ```
 
 Parse status from REVIEW.md frontmatter. If "clean" or "skipped": proceed to 3d. If findings found: auto-invoke:
 ```
-Skill(skill="rihal:code-review-fix", args="${PHASE_NUM} --auto")
+Skill(skill="rihal-code-review-fix", args="${PHASE_NUM} --auto")
 ```
 
 **Error handling:** If either Skill fails, catch the error, display as non-blocking, and proceed to 3d.
@@ -505,14 +538,14 @@ Ask user via AskUserQuestion:
 On **"Run gap closure"**: Execute gap closure cycle (limit: 1 attempt):
 
 ```
-Skill(skill="rihal:plan", args="${PHASE_NUM} --gaps")
+Skill(skill="rihal-plan", args="${PHASE_NUM} --gaps")
 ```
 
 Verify gap plans were created. If none → go to handle_blocker: "Gap closure planning for phase ${PHASE_NUM} did not produce plans."
 
 Re-execute:
 ```
-Skill(skill="rihal:execute", args="${PHASE_NUM} --no-transition")
+Skill(skill="rihal-execute", args="${PHASE_NUM} --no-transition")
 ```
 
 Re-read verification status. If `passed` or `human_needed`: route normally. If still `gaps_found` after this retry: ask via AskUserQuestion:
@@ -542,7 +575,7 @@ Phase ${PHASE_NUM}: Frontend phase with UI-SPEC — running UI review audit...
 ```
 
 ```
-Skill(skill="rihal:ui-review", args="${PHASE_NUM}")
+Skill(skill="rihal-ui-review", args="${PHASE_NUM}")
 ```
 
 Display the review result summary (score from UI-REVIEW.md if produced). Continue to iterate step regardless of score — UI review is advisory, not blocking.
@@ -799,6 +832,37 @@ Decisions captured: {count} across {area_count} areas
 
 ## 4. Iterate
 
+### 4.0. Refresh Phase Count From Disk (MANDATORY — Compaction Guard)
+
+**This step is NON-NEGOTIABLE.** LLM context compaction loses in-memory
+variables. Re-derive `phase_count` and `completed_phases` from disk at the
+START of every iteration — never rely on values held from the initialize step.
+
+```bash
+# Re-read the authoritative progress snapshot from the CLI
+PROGRESS_REFRESH=$(node .rihal/bin/rihal-tools.cjs progress init 2>/dev/null)
+```
+
+Parse `PROGRESS_REFRESH` JSON and update:
+- `phase_count` ← `PROGRESS_REFRESH.phase_count`
+- `completed_phases` ← `PROGRESS_REFRESH.completed_count`
+- `T` (for banner display) ← `phase_count`
+
+If `PROGRESS_REFRESH` fails or is empty, fall back to direct ROADMAP.md parsing:
+
+```bash
+# Fallback: count phases directly from ROADMAP.md
+PHASE_COUNT_DISK=$(grep -cE '^\|\s*\d{1,3}' .planning/ROADMAP.md 2>/dev/null || echo "0")
+COMPLETED_DISK=$(find .planning/phases/ -name '*SUMMARY.md' 2>/dev/null | wc -l)
+```
+
+**Sanity check:** If `current_phase_number > phase_count`, this is a drift
+symptom. Log a warning and re-derive from disk:
+
+```
+⚠ Phase drift detected: current phase ${N} > total ${T}. Re-reading from ROADMAP.md.
+```
+
 **If `ONLY_PHASE` is set:** Do not iterate. Proceed directly to lifecycle step (which exits cleanly per single-phase mode).
 
 **If `TO_PHASE` is set and current phase number >= `TO_PHASE`:**
@@ -811,7 +875,7 @@ Decisions captured: {count} across {area_count} areas
  Completed through phase ${TO_PHASE} as requested.
  Remaining phases were not executed.
 
- Resume with: /rihal:autonomous --from ${next_incomplete_phase}
+ Resume with: /rihal-autonomous --from ${next_incomplete_phase}
 ```
 
 Proceed directly to lifecycle step (which handles partial completion). Exit cleanly.
@@ -860,7 +924,7 @@ If all phases complete, proceed to lifecycle step.
  Phase ${ONLY_PHASE}: ${PHASE_NAME} — Done
  Mode: Single phase (--only)
 
- Lifecycle skipped — run /rihal:autonomous without --only
+ Lifecycle skipped — run /rihal-autonomous without --only
  after all phases complete to trigger audit/complete/cleanup.
 ```
 
@@ -882,7 +946,7 @@ Display lifecycle transition banner:
 ### 5a. Audit
 
 ```
-Skill(skill="rihal:audit-milestone")
+Skill(skill="rihal-audit-milestone")
 ```
 
 After audit completes, detect the result:
@@ -930,7 +994,7 @@ On **"Stop"**: Go to handle_blocker.
 ### 5b. Complete Milestone
 
 ```
-Skill(skill="rihal:complete-milestone", args="${milestone_version}")
+Skill(skill="rihal-complete-milestone", args="${milestone_version}")
 ```
 
 After complete-milestone returns, verify archive output:
@@ -944,7 +1008,7 @@ If the archive file does not exist, go to handle_blocker: "Complete milestone di
 ### 5c. Cleanup
 
 ```
-Skill(skill="rihal:cleanup")
+Skill(skill="rihal-cleanup")
 ```
 
 Cleanup shows its own dry-run and asks user for approval internally — this is an acceptable pause since it's an explicit decision about file deletion.
@@ -963,6 +1027,17 @@ Cleanup shows its own dry-run and asks user for approval internally — this is
  Ship it! 🚀
 ```
 
+**If autonomous created a branch** (i.e., `BRANCH_NAME` was set in the prepare_branch step):
+
+Display:
+
+```
+🔀 Branch: ${BRANCH_NAME}
+   All work is on this branch. When ready, merge to main:
+     git checkout main && git merge ${BRANCH_NAME}
+   Or create a PR for review.
+```
+
 </step>
 
 <step name="handle_blocker">
@@ -999,7 +1074,7 @@ Proceed to iterate.
  Skipped: {list of skipped phases}
  Remaining: {list of remaining phases}
 
- Resume with: /rihal:autonomous ${ONLY_PHASE ? "--only " + ONLY_PHASE : "--from " + next_phase}${TO_PHASE ? " --to " + TO_PHASE : ""}
+ Resume with: /rihal-autonomous ${ONLY_PHASE ? "--only " + ONLY_PHASE : "--from " + next_phase}${TO_PHASE ? " --to " + TO_PHASE : ""}
 ```
 
 Record blocker in state:
@@ -1029,7 +1104,7 @@ node .rihal/bin/rihal-tools.cjs state add-blocker "Autonomous mode stopped at ph
 - [ ] Final completion or stop summary displayed
 - [ ] After all phases complete, lifecycle step is invoked (not manual suggestion)
 - [ ] Lifecycle transition banner displayed before audit
-- [ ] Audit invoked via Skill(skill="rihal:audit-milestone")
+- [ ] Audit invoked via Skill(skill="rihal-audit-milestone")
 - [ ] Audit result routing: passed → auto-continue, gaps_found → user decides, tech_debt → user decides
 - [ ] Complete-milestone invoked via Skill() with ${milestone_version} arg
 - [ ] Cleanup invoked via Skill() — internal confirmation is acceptable
@@ -1056,4 +1131,13 @@ node .rihal/bin/rihal-tools.cjs state add-blocker "Autonomous mode stopped at ph
 - [ ] `--interactive` waits for background agents before post-execution routing
 - [ ] `--interactive` compatible with `--only`, `--from`, and `--to` flags
 - [ ] No `git push` issued by the workflow (per AGENTS.md)
+- [ ] Branch created when on main/master (unless --allow-main override)
+- [ ] Branch name follows `rihal/autonomous-{version}-{timestamp}` pattern
+- [ ] --allow-main flag skips branch creation with warning
+- [ ] Non-main/master branches used as-is without branch creation
+- [ ] PR/merge suggestion displayed at lifecycle completion when branch was created
+- [ ] Phase count T re-derived from disk at start of every iteration (compaction guard)
+- [ ] Phase count T re-derived from disk before execute_phase banner display
+- [ ] Drift warning logged when current phase number exceeds total
+- [ ] Progress bar always accurate after LLM context compaction
 </success_criteria>

package/rihal/workflows/brainstorm.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:brainstorm
+# Workflow: rihal-brainstorm
 
 <purpose>
 Guided brainstorming session using structured methods. User provides a challenge; the workflow presents available methods, applies the selected one, and generates ideas in a structured format. Output is a brainstorm artifact stored in `.planning/brainstorms/` with the chosen method, raw ideas, and synthesis.
@@ -9,14 +9,14 @@ Guided brainstorming session using structured methods. User provides a challenge
 If `$ARGUMENTS` is empty or only contains `--help` or `-h`:
 
 ```
-/rihal:brainstorm <challenge> [--method=METHOD] [--people=N] [--personas=LIST]
+/rihal-brainstorm <challenge> [--method=METHOD] [--people=N] [--personas=LIST]
 ```
 
 **Examples:**
 ```
-/rihal:brainstorm how to improve user onboarding
-/rihal:brainstorm --method=SCAMPER reduce API latency
-/rihal:brainstorm --method=Rolestorming --personas=competitor,child reduce churn
+/rihal-brainstorm how to improve user onboarding
+/rihal-brainstorm --method=SCAMPER reduce API latency
+/rihal-brainstorm --method=Rolestorming --personas=competitor,child reduce churn
 ```
 
 STOP — do not proceed. Only proceed when the user provides a challenge.
@@ -182,8 +182,8 @@ After method execution:
 ## Next Steps
 
 To turn ideas into features/tickets:
-- `/rihal:plan <idea description>` — for detailed implementation plan
-- `/rihal:council is this idea worth pursuing?` — for strategic discussion
+- `/rihal-plan <idea description>` — for detailed implementation plan
+- `/rihal-council is this idea worth pursuing?` — for strategic discussion
 ```
 
 4. Print summary: "{N} ideas generated using {METHOD_NAME}"

package/rihal/workflows/chain.md

@@ -1,7 +1,7 @@
-# Workflow: rihal:chain
+# Workflow: rihal-chain
 
 <purpose>
-Run a sequential agent pipeline — each agent receives the previous agent's output as input. Unlike `/rihal:council` (parallel debate with cross-talk), chain is a one-way pipeline for "do research → hand to PM → hand to CTO" patterns. Each stage's output is saved as a first-class artifact the next stage reads.
+Run a sequential agent pipeline — each agent receives the previous agent's output as input. Unlike `/rihal-council` (parallel debate with cross-talk), chain is a one-way pipeline for "do research → hand to PM → hand to CTO" patterns. Each stage's output is saved as a first-class artifact the next stage reads.
 </purpose>
 
 ## Step 0 — Usage check
@@ -9,7 +9,7 @@ Run a sequential agent pipeline — each agent receives the previous agent's out
 If `$ARGUMENTS` is empty, print:
 
 ```
-Usage: /rihal:chain <preset|agent-list> <topic or question>
+Usage: /rihal-chain <preset|agent-list> <topic or question>
 
 Presets (common pipelines):
   research-plan      Mariam (research) → Hussain-PM (scope) → Planner (SPRINT.md)
@@ -18,12 +18,12 @@ Presets (common pipelines):
   full-discovery     Mariam → Sadiq (kill criteria) → Hussain-PM → Waleed → Planner
 
 Custom agents (comma-separated, in order):
-  /rihal:chain mariam,hussain-pm,waleed <topic>
+  /rihal-chain mariam,hussain-pm,waleed <topic>
 
 Examples:
-  /rihal:chain research-plan affiliate site in Dubai for mobile accessories
-  /rihal:chain feasibility migrate our Postgres to Neon serverless
-  /rihal:chain mariam,hussain-pm should we enter the SaaS bookkeeping market in Oman?
+  /rihal-chain research-plan affiliate site in Dubai for mobile accessories
+  /rihal-chain feasibility migrate our Postgres to Neon serverless
+  /rihal-chain mariam,hussain-pm should we enter the SaaS bookkeeping market in Oman?
 ```
 
 STOP here if no arguments.
@@ -33,11 +33,11 @@ STOP here if no arguments.
 If `$ARGUMENTS` is a pure decision question with no topic to work on (patterns like "should we", "A or B", "is X better than Y", "worth it") and does NOT contain a preset name or agent list:
 
 ```
-⚠ /rihal:chain produces deliverables (RESEARCH.md, SCOPE.md, SPRINT.md).
-For decisions only, /rihal:council is the right tool.
+⚠ /rihal-chain produces deliverables (RESEARCH.md, SCOPE.md, SPRINT.md).
+For decisions only, /rihal-council is the right tool.
 
-For a debate: /rihal:council $ARGUMENTS
-For a research-to-plan pipeline: /rihal:chain research-plan $ARGUMENTS
+For a debate: /rihal-council $ARGUMENTS
+For a research-to-plan pipeline: /rihal-chain research-plan $ARGUMENTS
 ```
 
 Only proceed past this step if the input is a topic or deliverable request (e.g., "research affiliate site", "scope mobile app migration", "plan e-commerce platform").
@@ -132,7 +132,7 @@ Artifacts in {chain_dir}/:
   3-planner-SPRINT.md          (Planner, stage 3)
 
 Next step:
-/rihal:execute {chain_dir}/3-planner-SPRINT.md
+/rihal-execute {chain_dir}/3-planner-SPRINT.md
 
 ─── ~5K tokens per stage · {duration}s · {stage-count} agents ───
 ```
@@ -167,14 +167,14 @@ Silent on failure — state tracking is optional.
 | `gtm-to-build` | mariam → hussain-pm → waleed | Market → scope → tech reality check |
 | `full-discovery` | mariam → sadiq → hussain-pm → waleed → planner | Full validation before committing |
 
-## Differences from /rihal:council
+## Differences from /rihal-council
 
-| | /rihal:council | /rihal:chain |
+| | /rihal-council | /rihal-chain |
 |--|--|--|
 | Execution | Parallel (Round 1 + cross-talk Round 2) | Sequential (one at a time) |
 | Output | One session artifact with all agent voices | One artifact per agent |
 | Best for | Debate, disagreement, multiple perspectives | Pipelines where each stage builds on the last |
-| Subsequent use | `/rihal:plan {session}` converts follow-ups to plans | Last stage often IS a SPRINT.md already |
+| Subsequent use | `/rihal-plan {session}` converts follow-ups to plans | Last stage often IS a SPRINT.md already |
 
 ## On Error
 
@@ -183,6 +183,6 @@ Silent on failure — state tracking is optional.
 - **Unknown preset:** list valid presets, stop.
 - **Agent not installed:** print installed agents, suggest closest match.
 - **state.json missing or corrupted:** continue without error — chain artifacts are mandatory, state tracking is optional.
-- **Stage fails to produce artifact:** print stage number, allow `/rihal:chain --continue` to resume.
+- **Stage fails to produce artifact:** print stage number, allow `/rihal-chain --continue` to resume.
 - **Agent returns empty output:** print "Agent produced no output. Check input and retry."
 - **`rihal-tools.cjs` missing:** tell user to run `npx @hanzlaa/rcode install` (or `rcode install` if installed globally).

package/rihal/workflows/check-implementation-readiness.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:check-implementation-readiness
+# Workflow: rihal-check-implementation-readiness
 
 <purpose>
 Pre-execution gate: verify PRD approved, architecture approved, external dependencies identified, and no blocking assumptions remain. Return pass/fail report. Used as guard in plan.md Step 0.8 and execute.md Step 0.
@@ -10,13 +10,13 @@ Pre-execution gate: verify PRD approved, architecture approved, external depende
 If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
 
 ```
-/rihal:check-implementation-readiness <argument-here>
+/rihal-check-implementation-readiness <argument-here>
 ```
 
 **Examples:**
 ```
-/rihal:check-implementation-readiness example 1
-/rihal:check-implementation-readiness example 2
+/rihal-check-implementation-readiness example 1
+/rihal-check-implementation-readiness example 2
 ```
 
 STOP — do not proceed.

package/rihal/workflows/check-todos.md

@@ -22,14 +22,14 @@ If `todo_count` is 0:
 ```
 No pending todos.
 
-Todos are captured during work sessions with /rihal:add-todo.
+Todos are captured during work sessions with /rihal-add-todo.
 
 ---
 
 Would you like to:
 
-1. Continue with current phase (/rihal:progress)
-2. Add a todo now (/rihal:add-todo)
+1. Continue with current phase (/rihal-progress)
+2. Add a todo now (/rihal-add-todo)
 ```
 
 Exit.
@@ -37,8 +37,8 @@ Exit.
 
 <step name="parse_filter">
 Check for area filter in arguments:
-- `/rihal:check-todos` → show all
-- `/rihal:check-todos api` → filter to area:api only
+- `/rihal-check-todos` → show all
+- `/rihal-check-todos api` → filter to area:api only
 </step>
 
 <step name="list_todos">
@@ -56,7 +56,7 @@ Pending Todos:
 ---
 
 Reply with a number to view details, or:
-- `/rihal:check-todos [area]` to filter by area
+- `/rihal-check-todos [area]` to filter by area
 - `q` to exit
 ```
 
@@ -118,7 +118,7 @@ Use AskUserQuestion:
 - question: "What would you like to do with this todo?"
 - options:
   - "Work on it now" — move to done, start working
-  - "Create a phase" — /rihal:add-phase with this scope
+  - "Create a phase" — /rihal-add-phase with this scope
   - "Brainstorm approach" — think through before deciding
   - "Put it back" — return to list
 </step>
@@ -134,7 +134,7 @@ Update STATE.md todo count. Present problem/solution context. Begin work or ask
 Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
 
 **Create a phase:**
-Display: `/rihal:add-phase [description from todo]`
+Display: `/rihal-add-phase [description from todo]`
 Keep in pending. User runs command in fresh context.
 
 **Brainstorm approach:**

package/rihal/workflows/checkpoint-preview.md

@@ -1,4 +1,4 @@
-# Workflow: rihal:checkpoint-preview
+# Workflow: rihal-checkpoint-preview
 
 <purpose>
 Human-in-the-loop change review. Make sense of a diff, focus attention where it matters, and walk through testing. Delegates to the rihal-checkpoint-preview skill for the full review protocol.