@hanzlaa/rcode 3.4.3 → 3.4.5

package/rihal/commands/audit.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-audit
-description: Single audit entry point — asks what to audit (phase, milestone, UAT, code, fix, work) and dispatches to the right subroute. Honours .rihal/config.yaml mode.
-argument-hint: "[phase | milestone | uat | code | fix | work] [...subroute args]"
+description: Single audit entry point — asks what to audit (phase, milestone, UAT, code, fix, work, lens) and dispatches to the right subroute. Honours .rihal/config.yaml mode.
+argument-hint: "[phase | milestone | uat | code | fix | work | lens [<1-15> | all]] [...subroute args]"
 allowed-tools: Read, Write, Bash, AskUserQuestion
 ---
 

package/rihal/commands/capture.md

@@ -0,0 +1,12 @@
+---
+name: rihal-capture
+description: Capture a thought as todo (default), note, seed, or list pending — unified entry replacing /rihal-add-todo, /rihal-note, /rihal-plant-seed, /rihal-check-todos.
+argument-hint: "[text] [--note] [--seed] [--list]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+---
+
+@.rihal/workflows/capture.md

package/rihal/commands/diagnose-issues.md

@@ -0,0 +1,18 @@
+---
+name: rihal-diagnose-issues
+description: Reusable diagnosis subroutine. Walks symptom → hypothesis → evidence → minimal reproduction → fix recommendation. Called from verify-work when verification fails.
+argument-hint: "[symptom description]"
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+<objective>
+Diagnose systemic issues by walking through symptom, hypothesis, evidence, and minimal reproduction steps.
+</objective>
+
+<execution_context>
+@.rihal/workflows/diagnose-issues.md
+</execution_context>
+
+<process>
+Execute the diagnose-issues workflow from @.rihal/workflows/diagnose-issues.md end-to-end.
+</process>

package/rihal/commands/discuss-phase-power.md

@@ -0,0 +1,18 @@
+---
+name: rihal-discuss-phase-power
+description: Power user mode for discuss-phase. Generates all questions upfront into a JSON state file and HTML companion UI, then processes all answers in one pass to produce CONTEXT.md.
+argument-hint: "<phase-number>"
+allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
+---
+
+<objective>
+Power mode discuss-phase: batch all questions upfront, collect answers at user's pace, produce CONTEXT.md in one processing pass.
+</objective>
+
+<execution_context>
+@.rihal/workflows/discuss-phase-power.md
+</execution_context>
+
+<process>
+Execute the discuss-phase-power workflow from @.rihal/workflows/discuss-phase-power.md end-to-end.
+</process>

package/rihal/commands/feature-drift.md

@@ -0,0 +1,18 @@
+---
+name: rihal-feature-drift
+description: "Detect drift between PRD, epics, stories, and code. Severity-tagged report; --fix patches trivial items only. Reuses verifier-loop pattern from /rihal-docs-update."
+argument-hint: "[--fix] [--scope phase|project] [phase-number]"
+allowed-tools: Read, Write, Bash, Glob, Grep, Task, AskUserQuestion
+---
+
+<objective>
+Execute feature-drift workflow
+</objective>
+
+<execution_context>
+@.rihal/workflows/feature-drift.md
+</execution_context>
+
+<process>
+Execute the feature-drift workflow from @.rihal/workflows/feature-drift.md end-to-end.
+</process>

package/rihal/commands/karpathy-audit.md

@@ -0,0 +1,18 @@
+---
+name: rihal-karpathy-audit
+description: Audit source code changes against Andrej Karpathy's 4 LLM coding principles. Flags unclear assumptions, overengineering, surgical violations, and stubs.
+argument-hint: "[--files <glob>] [--since <commit>]"
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+<objective>
+Audit code changes against Karpathy's 4 principles and return structured findings with severity and fix guidance.
+</objective>
+
+<execution_context>
+@.rihal/workflows/karpathy-audit.md
+</execution_context>
+
+<process>
+Execute the karpathy-audit workflow from @.rihal/workflows/karpathy-audit.md end-to-end.
+</process>

package/rihal/commands/lens-audit.md

@@ -0,0 +1,70 @@
+---
+name: rihal-lens-audit
+triggers:
+  - rihal-lens-audit
+  - lens audit
+  - lens audit karo
+  - run lens audit
+  - audit with lens
+  - audit lens
+  - specific lens audit
+  - run security lens
+  - run performance lens
+  - run testability lens
+  - run all lenses
+  - 15 lens audit
+not-for:
+  - phase audit (use /rihal-audit phase)
+  - milestone audit (use /rihal-audit milestone)
+  - karpathy audit without lens context (use /rihal-code-review --karpathy)
+description: Run a structured 15-lens code audit. Picks one lens or all 15 sequentially. Prints findings and ready-to-paste GitHub issue bodies. Never auto-fixes — audit-first.
+argument-hint: "[<1-15> | <lens-name> | all]"
+allowed-tools: Read, Write, Bash, AskUserQuestion
+---
+
+## Overview
+
+15-lens audit entry point. Each lens is an independent inspection angle:
+security, performance, testability, extensibility, dep-health, error-recovery,
+state-machine, i18n, documentation, cross-platform, karpathy, sxo,
+observability, naming, coverage.
+
+Runs the selected lens(es), prints labelled findings, outputs GH issue bodies
+for each lens with findings. Never modifies files — audit-first, fix-second.
+
+## Workflow
+
+@.rihal/workflows/lens-audit.md
+
+## Output Format
+
+Per-lens labelled finding blocks, then a summary banner with counts, then
+foldable GitHub issue bodies ready to copy-paste or pipe to `gh issue create`.
+
+## Examples
+
+**Happy path — interactive:**
+```
+/rihal-lens-audit
+→ shows lens picker, user selects 1 (security)
+→ runs security lens, prints findings, prints GH issue body
+```
+
+**Happy path — direct:**
+```
+/rihal-lens-audit security
+/rihal-lens-audit 3
+/rihal-lens-audit all
+```
+
+**Edge — no findings:**
+```
+/rihal-lens-audit 5
+→ ✓ Lens 5 (dep-health): no findings
+```
+
+**Negative — wrong lens number:**
+```
+/rihal-lens-audit 99
+→ Error: lens must be 1-15 or a lens name. Run /rihal-lens-audit --help.
+```

package/rihal/commands/new-project-research.md

@@ -0,0 +1,18 @@
+---
+name: rihal-new-project-research
+description: Research subcommand for new-project. Deep research phase producing artifacts that feed into requirements and roadmap generation.
+argument-hint: "[--deep] [--domain <domain>]"
+allowed-tools: Read, Write, Bash, Glob, Grep, WebSearch, WebFetch
+---
+
+<objective>
+Execute the research phase of new-project setup: produce research artifacts consumed by requirements and roadmap steps.
+</objective>
+
+<execution_context>
+@.rihal/workflows/new-project-research.md
+</execution_context>
+
+<process>
+Execute the new-project-research subworkflow from @.rihal/workflows/new-project-research.md end-to-end.
+</process>

package/rihal/commands/new-project-roadmap.md

@@ -0,0 +1,18 @@
+---
+name: rihal-new-project-roadmap
+description: Roadmap subcommand for new-project. Generates PROJECT.md requirements, ROADMAP.md, and the Done signoff after setup and optional research.
+argument-hint: "[--from-research]"
+allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
+---
+
+<objective>
+Execute the requirements + roadmap phase of new-project: produce PROJECT.md, REQUIREMENTS.md, and ROADMAP.md.
+</objective>
+
+<execution_context>
+@.rihal/workflows/new-project-roadmap.md
+</execution_context>
+
+<process>
+Execute the new-project-roadmap subworkflow from @.rihal/workflows/new-project-roadmap.md end-to-end.
+</process>

package/rihal/commands/phase.md

@@ -0,0 +1,11 @@
+---
+name: rihal-phase
+description: Phase CRUD — add (default), insert decimal, or remove. Unified entry replacing /rihal-add-phase, /rihal-insert-phase, /rihal-remove-phase.
+argument-hint: "[name] [--insert <after>] [--remove <id>]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+@.rihal/workflows/phase.md

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 2`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -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 2`
 
 <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 2
 ```
 
 User has no idea what 02-03 is about.

package/rihal/references/output-format.md

@@ -1,5 +1,39 @@
 <ui_patterns>
 
+## Workflow Step Heading (canonical format)
+
+All workflows MUST use `## Step N — {Name}` for top-level steps. No other format.
+
+```
+## Step 1 — Parse arguments
+## Step 2 — Load state
+## Step 3 — Spawn agents
+```
+
+**Deprecated forms (do not use in new or updated workflows):**
+- `<step name="...">` — XML-tag format (legacy, still accepted by agents but not for new workflows)
+- `### Step N` — wrong heading level
+- `**Step N:**` — bold-text format
+
+When refactoring a workflow, convert its steps to `## Step N — {Name}` incrementally. Do not leave a mix of formats within the same workflow.
+
+---
+
+## Subagent Output Format Contract
+
+When spawning a subagent with `Task()`, the spawning prompt MUST include a brief expected output section so the sub-agent produces machine-parseable results. Minimal template:
+
+```
+## Expected output format
+{One of: JSON object / Markdown report / Plain text / VERIFICATION.md schema}
+Return exactly this format — no extra commentary before or after.
+```
+
+Workflows that omit this cause silent format mismatches where the orchestrator cannot parse the sub-agent's response.
+
+---
+
+
 Visual patterns for user-facing Rihal output. Orchestrators @-reference this file.
 
 ## Stage Banners
@@ -307,6 +341,50 @@ Use agent emoji + bilingual name prefix once per turn. No repeat in same respons
 
 ---
 
+## RTL / Arabic Output Safety
+
+When `response_language` is Arabic or another RTL language, bidi-unaware terminals
+corrupt fixed-width ASCII art (banners, progress bars) when Arabic text is embedded
+inside them. Follow these rules to avoid visual corruption:
+
+**Banner stage names:** Always keep stage names in **English** even when
+`response_language` is Arabic. The `━━━` border lines are width-sensitive; mixed
+RTL characters inside them break alignment. Place the Arabic description **below**
+the banner, not inside it.
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ RIHAL ► PLANNING SPRINT 01.1
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+التخطيط للسباق 01.1 — يرجى الانتظار
+```
+
+**Progress bars:** Keep the bar characters (`█░`) and percentages on their own line.
+Put the Arabic label on a separate preceding line:
+
+```
+التقدم:
+████████░░ 80%
+```
+
+Do **not** embed Arabic text inside the bar line — it reverses the order of `%` and digits in bidi terminals.
+
+**Checkpoint boxes:** The `╔ ═ ╚` box characters are LTR-anchored. Place Arabic
+content in the body paragraph below the box, not as the box heading:
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║  CHECKPOINT: Verification Required                           ║
+╚══════════════════════════════════════════════════════════════╝
+
+هل تمت المراجعة؟ اكتب "approved" للمتابعة.
+```
+
+**General rule:** ASCII-art structure (borders, bars, arrows) stays in LTR. All
+translated prose goes outside the art, on its own line(s).
+
+---
+
 ## Anti-Patterns
 
 - Varying box/banner widths within same output
@@ -315,5 +393,6 @@ Use agent emoji + bilingual name prefix once per turn. No repeat in same respons
 - Random emoji (`🚀`, `✨`, `💫`) outside the approved set
 - Missing Next Up block after workflow completions
 - Hardcoding references to other methodologies in rihal's UX
+- Embedding Arabic/RTL text inside fixed-width ASCII banners or progress bars
 
 </ui_patterns>

package/rihal/references/revision-loop.md

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

package/rihal/references/verb-dictionary.md

@@ -1,72 +1,102 @@
 # Verb Dictionary — multilingual intent matching
 
-**Purpose:** single source of truth for action verbs across all Rihal workflows that do intent matching. Without this, each workflow's matcher diverges and Roman Urdu / Hindi instructions silently miss.
+**Purpose:** single source of truth for action verbs across all Rihal workflows that do intent matching. Without this, each workflow's matcher diverges and Roman Urdu / Hindi / Arabic instructions silently miss.
 
 **How to use from a workflow:** include this file via `@.rihal/references/verb-dictionary.md` and reference categories by name (e.g. *"verbs from §Create"*) instead of restating English-only lists inline.
 
+**Arabic priority:** Rihal's primary user base operates in Arabic. Native Arabic script (المشروع, مرحلة, راجع) MUST be in every category — transliteration is a fallback for keyboard input only. When you see a new Arabic phrasing in user input, add the native script first, then the transliteration.
+
 ---
 
 ## §Create — make / start / new / open
 
 Match if `$QUESTION` contains any of these (case-insensitive):
 
-- **English:** `create`, `make`, `start`, `build`, `set up`, `setup`, `kick off`, `spin up`, `open`, `begin`, `draft`, `generate`, `produce`, `initialize`, `init`, `bootstrap`, `establish`, `form`
+- **English:** `create`, `make`, `start`, `build`, `set up`, `setup`, `kick off`, `spin up`, `open`, `begin`, `draft`, `generate`, `produce`, `initialize`, `init`, `bootstrap`, `establish`, `form`, `new`
 - **Roman Urdu / Hindi:** `bnao`, `banao`, `bana do`, `bnado`, `banaa`, `banade`, `banayein`, `banadijiye`, `shuru karo`, `shuro karo`, `start karo`, `create karo`, `naya banao`, `nya banao`, `draft karo`, `banalo`, `khol do`, `khol lo`, `kholiye`
-- **Arabic transliteration:** `ansha'`, `inshaa'`, `a3mal`, `ibda'`
+- **Arabic native:** `أنشئ`, `أنشأ`, `ابدأ`, `اعمل`, `افتح`, `كوّن`, `كون`, `أسس`, `اصنع`, `أوجد`, `سوّي`, `سوي`, `جديد`, `جديدة`, `ابني`, `ابن`, `هيّئ`
+- **Arabic transliteration:** `anshi'`, `inshaa'`, `ibda'`, `i3mal`, `iftah`, `kawwen`, `asses`, `isna3`, `awjid`, `sawwi`, `jadid`, `jadida`
 
 ## §Add — append / include / attach / extend
 
 - **English:** `add`, `append`, `include`, `attach`, `insert`, `extend`, `expand`, `register`
 - **Roman Urdu / Hindi:** `add karo`, `daal do`, `daalo`, `daal de`, `jor do`, `jor de`, `lagao`, `lagado`, `shamil karo`, `shaamil karo`, `barhao`
-- **Arabic transliteration:** `azif`, `dam'`
+- **Arabic native:** `أضف`, `زِد`, `ضمّ`, `أرفق`, `أدمج`, `ألحق`, `أدخل`, `أضِف`
+- **Arabic transliteration:** `adhif`, `azif`, `zid`, `dhomm`, `arfeq`, `admij`, `alheq`
 
 ## §Plan — design / scope / outline
 
 - **English:** `plan`, `design`, `draft`, `scope`, `outline`, `architect`, `lay out`, `schedule`
 - **Roman Urdu / Hindi:** `plan karo`, `design karo`, `sochlo`, `soch lo`, `layout banao`, `tarteeb do`, `tartib karo`
-- **Arabic transliteration:** `khattit`, `tasmim`
+- **Arabic native:** `خطّط`, `خطط`, `صمّم`, `صمم`, `رتّب`, `رتب`, `نظّم`, `حدّد`, `هيكلة`, `خطة`, `تصميم`
+- **Arabic transliteration:** `khattit`, `tasmim`, `sammim`, `rattib`, `nazzim`, `haddid`, `hayakla`
 
 ## §Execute — run / build / ship / implement / do
 
 - **English:** `execute`, `run`, `build`, `ship`, `complete`, `do`, `implement`, `deliver`, `finish`, `wrap up`, `compile`
 - **Roman Urdu / Hindi:** `chalao`, `chala do`, `run karo`, `kar do`, `kardo`, `kar lo`, `karlo`, `implement karo`, `mukammal karo`, `complete karo`, `khatam karo`, `pura karo`
-- **Arabic transliteration:** `naffidh`, `aakmel`, `nafidh`
+- **Arabic native:** `نفّذ`, `نفذ`, `أكمل`, `اكمل`, `أنجز`, `شغّل`, `شغل`, `حقّق`, `سلّم`, `بنّ`, `ابنِ`, `أنهِ`, `جهّز`
+- **Arabic transliteration:** `naffidh`, `nafidh`, `aakmel`, `akmil`, `anjiz`, `shaghghil`, `haqqiq`, `sallim`, `jahhiz`
 
 ## §Review — audit / check / inspect / verify / validate
 
-- **English:** `review`, `audit`, `check`, `inspect`, `verify`, `validate`, `examine`, `assess`, `evaluate`
+- **English:** `review`, `audit`, `check`, `inspect`, `verify`, `validate`, `examine`, `assess`, `evaluate`, `look over`, `go over`, `spot check`
 - **Roman Urdu / Hindi:** `dekho`, `dekh lo`, `dekhlo`, `check karo`, `audit karo`, `verify karo`, `validate karo`, `parkho`, `parakhh`, `mulahiza karo`, `nazar dalo`, `jaiza lo`
-- **Arabic transliteration:** `raji'`, `tahaqqaq`, `dakhq`
+- **Arabic native:** `راجع`, `تحقّق`, `تحقق`, `افحص`, `دقّق`, `دقق`, `تأكّد`, `تأكد`, `فتّش`, `فتش`, `قيّم`, `قيم`, `تفقّد`, `مراجعة`, `فحص`, `تدقيق`
+- **Arabic transliteration:** `raji3`, `tahaqqaq`, `ifhas`, `daqqaq`, `ta'akkad`, `fattish`, `qayyim`, `tafaqqad`
 
 ## §Show — list / display / get / fetch / see
 
 - **English:** `show`, `list`, `display`, `get`, `fetch`, `see`, `view`, `print`, `output`, `summarize`
 - **Roman Urdu / Hindi:** `dikhao`, `dikha do`, `dikhado`, `dikha de`, `list karo`, `batao`, `bata do`, `bata de`, `kholo`, `khol do`
-- **Arabic transliteration:** `azhir`, `arini`, `aktub`
+- **Arabic native:** `أظهر`, `أرني`, `اعرض`, `اعرضها`, `شاهد`, `اطبع`, `لخّص`, `لخص`, `بيّن`, `بين`, `قائمة`, `اعرض القائمة`
+- **Arabic transliteration:** `azhir`, `arini`, `i3rid`, `shahid`, `itba3`, `lakhkhis`, `bayyin`, `qa'ima`
 
 ## §Remove — delete / drop / undo / revert / kill
 
 - **English:** `remove`, `delete`, `drop`, `undo`, `revert`, `rollback`, `kill`, `purge`, `uninstall`, `clear`, `wipe`, `erase`
 - **Roman Urdu / Hindi:** `hatao`, `hata do`, `hatado`, `mita do`, `mita lo`, `mitao`, `delete karo`, `ulto`, `revert karo`, `nikalo`, `nikal do`, `khaali karo`
-- **Arabic transliteration:** `ihdhif`, `azhil`, `imhu`
+- **Arabic native:** `احذف`, `أزل`, `ألغِ`, `الغ`, `امسح`, `أبطل`, `تراجع`, `أرجع`, `أزِل`, `حذف`
+- **Arabic transliteration:** `ihdhif`, `azil`, `alghi`, `imsah`, `ibtil`, `taraja3`, `arji3`
 
 ## §Update — modify / change / edit / refresh / fix
 
 - **English:** `update`, `modify`, `change`, `edit`, `refresh`, `fix`, `patch`, `tweak`, `adjust`, `correct`, `repair`
 - **Roman Urdu / Hindi:** `update karo`, `badlo`, `badal do`, `badal de`, `change karo`, `edit karo`, `theek karo`, `theek kar do`, `thiek karo`, `fix karo`, `behtar karo`, `behter karo`, `improve karo`
-- **Arabic transliteration:** `ghair`, `aslih`, `hadith`
+- **Arabic native:** `غيّر`, `غير`, `عدّل`, `عدل`, `أصلح`, `اصلح`, `حدّث`, `حدث`, `رقّع`, `صحّح`, `صحح`, `حسّن`, `حسن`, `تحديث`, `تعديل`
+- **Arabic transliteration:** `ghayyir`, `aslih`, `haddith`, `raqqi3`, `sahheh`, `hassen`, `ta3deel`, `tahdeeth`
 
 ## §Pause — stop / wait / hold / cancel
 
 - **English:** `pause`, `stop`, `wait`, `hold`, `cancel`, `abort`, `halt`, `freeze`, `defer`
 - **Roman Urdu / Hindi:** `ruko`, `ruk jao`, `band karo`, `band kardo`, `cancel karo`, `roko`, `rok do`, `rok de`, `pause karo`, `wapas karo`
-- **Arabic transliteration:** `tawaqaf`, `intazir`
+- **Arabic native:** `توقّف`, `توقف`, `انتظر`, `أوقف`, `علّق`, `علق`, `إلغاء`, `أجّل`, `أجل`
+- **Arabic transliteration:** `tawaqqaf`, `intazir`, `awqif`, `3alliq`, `ajjil`, `ilgha'`
 
 ## §Resume — continue / pick up / restart
 
 - **English:** `resume`, `continue`, `pick up`, `restart`, `re-run`, `replay`, `re-do`, `keep going`, `proceed`
 - **Roman Urdu / Hindi:** `phir se shuru karo`, `aage barho`, `aage chalao`, `continue karo`, `wapas chalao`, `dobara chalao`, `dobara karo`
-- **Arabic transliteration:** `astamir`, `i'ad`
+- **Arabic native:** `استمرّ`, `استمر`, `أعد`, `تابع`, `أكمل`, `ارجع`, `استأنف`, `كمّل`, `واصل`
+- **Arabic transliteration:** `astamir`, `i'ad`, `tabi3`, `akmil`, `arji3`, `ista'naf`, `kammil`, `wasel`
+
+## §Find — search / locate / discover / hunt
+
+(New category — captures "find edge cases", "find bugs", "look for", which the original dictionary missed.)
+
+- **English:** `find`, `search`, `locate`, `discover`, `hunt`, `surface`, `uncover`, `look for`, `identify`, `detect`
+- **Roman Urdu / Hindi:** `dhoondo`, `dhoondh do`, `talash karo`, `khojo`, `dekho kahan`, `pata karo`, `find karo`, `search karo`
+- **Arabic native:** `ابحث`, `جِد`, `اكتشف`, `استكشف`, `حدّد`, `بيّن`, `اعثر`, `استخرج`, `بحث`
+- **Arabic transliteration:** `ibhath`, `jid`, `iktashif`, `i3thar`, `istakhrij`, `bahath`
+
+## §Quality — bad code / smell / issues / problems
+
+(New category — captures "bad code practices", "code smells", "issues" used in audit-style requests.)
+
+- **English:** `bad code`, `code smell`, `smells`, `issues`, `problems`, `bugs`, `gotchas`, `pitfalls`, `anti-patterns`, `bad practices`, `tech debt`, `quality gaps`, `lint issues`
+- **Roman Urdu / Hindi:** `kharab code`, `bad code`, `mistakes`, `ghaltiyan`, `masail`, `bug bug karo`, `quality check`
+- **Arabic native:** `كود سيّئ`, `كود سيء`, `أخطاء`, `مشاكل`, `عيوب`, `ثغرات`, `جودة الكود`, `أنماط سيّئة`
+- **Arabic transliteration:** `code sayyi'`, `akhta'`, `mashakil`, `3uyub`, `thaghrat`, `jawdat al-code`
 
 ---
 
@@ -74,21 +104,23 @@ Match if `$QUESTION` contains any of these (case-insensitive):
 
 These are matched alongside §Create / §Add / §Plan verbs to determine the dispatch route.
 
-| Scope noun | Aliases (English + Urdu) | Maps to (workflow) |
+| Scope noun | Aliases (English + Urdu + Arabic) | 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`, **AR:** `معلم`, `إصدار`, `دورة`, `مرحلة كبرى` | `/rihal-new-milestone` |
+| phase | `phase`, `phases`, **AR:** `مرحلة`, `مراحل`, `طور`, `فاز` | `/rihal-add-phase` |
+| story | `story`, `stories`, `user story`, `kahani`, **AR:** `قصة`, `قصص`, `قصة مستخدم` | `/rihal-create-story` |
+| epic | `epic`, `epics`, `epics and stories`, **AR:** `ملحمة`, `ملاحم`, `فصل`, `فصول` | `/rihal-create-epics-and-stories` |
+| sprint | `sprint`, `iteration`, **AR:** `سباق`, `جولة`, `دورة عمل`, `سبرنت` | `/rihal-sprint-planning` |
+| PRD | `PRD`, `requirements doc`, `product requirements`, **AR:** `وثيقة المتطلبات`, `متطلبات المنتج`, `وثيقة المنتج` | `/rihal-create-prd` |
+| roadmap | `roadmap`, `plan` (top-level), **AR:** `خارطة طريق`, `خريطة الطريق`, `خطة عامة` | `/rihal-create-milestone` |
+| council | `council`, `majlis`, `panel`, `mashwara`, `salah`, **AR:** `مجلس`, `شورى`, `لجنة`, `استشارة` | `/rihal-council` |
+| plan (verb form — "plan phase N") | `plan`, **AR:** `خطّط`, `خطة` | `/rihal-plan` |
+| story (impl) | `dev story`, `implement story`, `build story`, **AR:** `نفذ القصة`, `طبّق القصة` | `/rihal-dev-story` |
+| brainstorm | `brainstorm`, `ideas`, `sochain`, `sochna`, **AR:** `عصف ذهني`, `أفكار`, `تفكير` | `/rihal-brainstorm` |
+| review (code) | `code review`, `karpathy`, `check my diff`, **AR:** `مراجعة الكود`, `راجع الكود`, `فحص الكود` | `/rihal-code-review [--karpathy]` |
+| edge cases | `edge cases`, `edge case hunt`, `find edge cases`, `corner cases`, **AR:** `حالات استثنائية`, `حالات حدية`, `حالات نادرة` | `/rihal-review-edge-case-hunter` |
+| debug | `debug`, `fix`, `bug`, `error`, `crash`, `kharab`, `theek`, **AR:** `صحّح`, `أصلح`, `خطأ`, `مشكلة`, `عطل` | `/rihal-debug` |
+| audit | `audit`, `quality audit`, `health check`, **AR:** `تدقيق`, `مراجعة شاملة`, `فحص الجودة`, `جودة` | `/rihal-audit` |
 
 ---
 
@@ -108,6 +140,9 @@ 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).
+
+Example: "ابدأ مرحلة جديدة" (Arabic — "start a new phase") → §Create
+matches `ابدأ` + scope `مرحلة` + intensifier `جديدة` → /rihal-add-phase.
 ```
 
 **From an agent file (e.g. `rihal-codebase-mapper.md`) when interpreting the orchestrator prompt:**
@@ -119,11 +154,33 @@ Example: "milestone bnao" → §Create matches "bnao", scope matches
 
 Recognize §Show / §Review / §Update verbs against the codebase. Honor
 multilingual phrasing — never silently fall through because a Roman
-Urdu instruction was the verb form.
+Urdu, Hindi, or Arabic instruction was the verb form.
+```
+
+**From a SKILL.md `triggers:` array** — DO NOT restate the dictionary inline. Instead, copy the most-likely surface phrases per language so Claude Code's literal trigger matcher fires:
+
+```yaml
+triggers:
+  # English
+  - "review the code"
+  - "code review"
+  - "check the diff"
+  - "find bad practices"
+  # Roman Urdu / Hindi
+  - "code check karo"
+  - "review karo"
+  # Arabic native
+  - "راجع الكود"
+  - "مراجعة الكود"
+  - "افحص الكود"
 ```
 
+5-12 triggers per skill is the spec. Always include English + Roman Urdu + Arabic for skills used in user-facing dispatch (council, do, add-phase, create-*, review-*).
+
 ---
 
 ## Maintenance
 
 Every entry must be a verb actually observed in user input — not invented. When you discover a new phrasing that broke matching, add it to the relevant category here rather than to the consuming workflow's local list. Single source of truth.
+
+**Arabic verbs:** add native script first (e.g. `أنشئ`), transliteration second (e.g. `anshi'`). Native script is what users actually type; transliteration is a keyboard fallback.

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

@@ -1,6 +1,6 @@
 ---
 name: rihal-prfaq
-description: Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
+description: Working Backwards PRFAQ challenge to forge product concepts.
 triggers:
   - "prfaq"
 ---

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

@@ -7,13 +7,23 @@ description: >
   "create the backlog". Do NOT use to prepare a single story for dev (use
   rihal-create-story).
 triggers:
+  # English
   - "create epics"
   - "break this into stories"
-  - "generate
-  the epic list"
+  - "generate the epic list"
   - "epic and story breakdown"
   - "decompose the PRD"
   - "create the backlog"
+  # Roman Urdu / Hindi
+  - "epics banao"
+  - "stories banao"
+  - "backlog banao"
+  # Arabic native
+  - "أنشئ ملاحم"
+  - "أنشئ القصص"
+  - "قسّم المتطلبات"
+  - "ابني القائمة"
+  - "تحليل وثيقة المتطلبات"
 ---
 @.rihal/references/karpathy-guidelines.md
 

package/rihal/skills/actions/2-plan/rihal-create-epics-and-stories/steps/step-04-final-validation.md

@@ -119,6 +119,18 @@ If all validations pass:
 - Ensure proper formatting
 - Save the final epics.md
 
+### 7. State Sync (MANDATORY — closes #126)
+
+After saving `.planning/epics.md`, you MUST sync state so `.rihal/state.json` reflects the new epics. Without this, downstream workflows (`/rihal-status`, `/rihal-progress`, `/rihal-execute`) see a divergent picture.
+
+Per `@rihal/skills/_shared/state-sync-rule.md`:
+
+```bash
+node .rihal/bin/rihal-tools.cjs state sync --from-disk
+```
+
+Confirm output reports the epic and story count matching what `epics.md` shows. If counts diverge, surface a warning and inspect the markdown for malformation.
+
 **Present Final Menu:**
 **All validations complete!** [C] Complete Workflow
 

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

@@ -8,14 +8,24 @@ description: >
   for updating an existing PRD (use rihal-edit-prd), or validating an
   existing PRD (use rihal-validate-prd).
 triggers:
+  # English
   - "create a PRD"
-  - "write product
-  requirements document"
+  - "write product requirements document"
   - "lets make a PRD"
   - "I want to create a new PRD"
   - "draft requirements for"
   - "new product spec"
   - "start a PRD"
+  # Roman Urdu / Hindi
+  - "PRD banao"
+  - "requirements likh do"
+  - "spec banao"
+  # Arabic native
+  - "أنشئ وثيقة المتطلبات"
+  - "اكتب متطلبات المنتج"
+  - "وثيقة المتطلبات"
+  - "ابدأ PRD"
+  - "صمم المتطلبات"
 ---
 @.rihal/references/karpathy-guidelines.md