@hanzlaa/rcode 2.8.0 → 3.1.0

package/AGENTS.md

@@ -24,7 +24,7 @@ If a user says "just keep going" or "don't stop until done", that authorization
 
 - Follow [Conventional Commits](https://www.conventionalcommits.org/) format: `type(scope): subject`
 - Types allowed: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `perf`, `revert`
-- Scopes allowed: `agents`, `skills`, `workflows`, `templates`, `dashboard`, `docs`, `config`, `github`
+- Scopes allowed: `agents`, `skills`, `workflows`, `templates`, `dashboard`, `docs`, `config`, `github`, `commands`, `memory`, `brand`, `cli`, `ci`, `release`, `meta`, `tasks`, `migrations`, `refs`
 - Subject: lowercase first letter, imperative mood, no trailing period, under 72 chars
 - **NEVER add Claude/AI attribution to commit messages.** No "Generated with Claude Code", no "Co-Authored-By: Claude", no "🤖 Generated". The user does not want this.
 - **NEVER use `--no-verify`** to bypass hooks. If hooks fail, fix the underlying issue.
@@ -46,6 +46,16 @@ If a user says "just keep going" or "don't stop until done", that authorization
 
 ---
 
+## Naming & Branding (per `BRAND.md`)
+
+- **Skill names** in frontmatter: `rihal-<verb>-<noun>` for legacy skills; new branded skills use `rcode-<verb>-<noun>` ONLY in slash command surface (`/rcode:<name>`); folder names stay `rihal-*` because `cli/install.js` hardcodes that prefix.
+- **Persona IDs** in `team.yaml` stay `rihal-<name>` (dashboard scanner reads them by id; renaming breaks rendering).
+- **Persona display names** keep Arabic alongside Latin: `Sadiq (صادق)`, `Dalil (دليل)`, etc.
+- **Concept primitives** (Memory Bank, Distillate, Majlis, Diwan) are named tooling — capitalised, used consistently in user-facing copy.
+- **Plain English over jargon in flags.** Prefer `--attack` over `--adversarial`, `--edge-cases` over `--edge-case-hunter`. Audience includes non-native English speakers.
+
+---
+
 ## File Modification Rules
 
 - **Maximum file size: 1000 lines** — refactor before exceeding

package/CONTRIBUTING.md

@@ -2,6 +2,13 @@
 
 Thank you for contributing. These guidelines exist to keep the module maintainable and impressive when demoed.
 
+> **Before you contribute, also read:**
+> - [`BRAND.md`](BRAND.md) — voice, naming conventions, persona glossary
+> - [`AGENTS.md`](AGENTS.md) — non-negotiable rules for AI coding agents (commit policy, push policy, off-limits files)
+> - [`MIGRATIONS.md`](MIGRATIONS.md) — every renamed/dropped surface in the rcode improvement programme
+> - [`MEMORY_BANK.md`](MEMORY_BANK.md) — Memory Bank specification
+> - [`TASKS.md`](TASKS.md) — master task tracker driving GitHub issues
+
 ---
 
 ## Architecture overview — what are all these files?

package/README.md

@@ -1,16 +1,31 @@
-# Rihal Code
+# Rihal Code (rcode)
 
 <div dir="rtl">طريقة رحال</div>
 
-> **Install Rihal's brain into your project in one command.** Every Rihalian — engineer, PM, designer, CTO, QA — gets an AI assistant that already knows how Rihal builds: PR standards, commit conventions, architecture patterns, sprint cadence, the Rihal team's agent personas. No onboarding. No prompting. Works in Claude Code, Cursor, and any compatible AI IDE.
+> **rcode is the memory bank for AI-driven SaaS teams — your project's context, structured, visible, and never lost.**
+>
+> Built by Rihal. Designed for solo devs, startup teams, and SaaS builders. Install once, and your AI assistant gets a persistent project brain: structured memory, decisions log, distinctive personas, and phase-based workflows. Works in Claude Code, Cursor, and any compatible AI IDE.
+
+---
+
+## Who is rcode for
+
+You'll feel rcode pay off if you've lived any of these:
+
+- **AI agents lose context mid-project.** Three sessions in, the assistant has forgotten the architectural decision you made on day one.
+- **Onboarding a teammate** means a 30-minute archaeology dig through Slack, Notion, and review comments to explain "why we did it this way".
+- **Late client requirements** keep shifting the goal posts, and there's no record of what was decided when.
+- **MVPs that work but can't be revamped** without rewriting from scratch — the original context is lost.
+
+rcode addresses these with a checked-in **Memory Bank** (`.rihal/memory/`), distinctive engineering personas, and a phased workflow that survives session resets. **For everything in one place, read [`DOCS.md`](DOCS.md).** See [`MEMORY_BANK.md`](MEMORY_BANK.md) for the spec, and [`BRAND.md`](BRAND.md) for naming and voice conventions.
 
 ---
 
 ## Why this exists
 
-Every Rihal project carries unwritten context — how we review PRs, what "done" means, how we sequence milestones, how PRDs travel from Product into Engineering. That context sits in people's heads, Slack, Notion, senior engineers' review comments. AI assistants pick it up never, because every new chat session starts knowing nothing about how Rihal works.
+Every project carries unwritten context — how the team reviews PRs, what "done" means, how milestones sequence, how PRDs travel from Product into Engineering. That context sits in people's heads, Slack, Notion, and senior engineers' review comments. AI assistants pick it up never, because every new chat session starts knowing nothing about how this project actually works.
 
-**Rihal Code fixes that.** One install, and the AI knows. Every session. Every repo. Every Rihalian.
+**rcode fixes that.** One install, and the AI knows. Every session. Every repo. Every contributor.
 
 See [`docs/what-is-rihal-code.md`](docs/what-is-rihal-code.md) for the full story, and [`docs/ROADMAP.md`](docs/ROADMAP.md) for where this is going (next: live MCP server in v3.0).
 
@@ -37,8 +52,10 @@ Rihal Code packages a lot. To keep things approachable, everything is organized
 
 Most AI tools give you one assistant pretending to be everything. **Rihal Code gives you Rihal's team — and Rihal's brain — inside every project.**
 
-- **43 agents** with clear roles, cultural identity (Arabic names), and hard scope boundaries
-- **99 slash commands** covering research, planning, execution, verification, and recovery
+- **45 agents** with clear roles, cultural identity (Arabic names), and hard scope boundaries
+- **95 slash commands** covering research, planning, execution, verification, and recovery
+- **80 skills** including Memory Bank primitives, 11 engineering-rigor skills (TDD, harden, perf, debug, trim, etc.), and 8 real-pain skills (auth-audit, mvp-graduate, deploy-unify, etc.)
+- **Persistent project memory** at `.rihal/memory/` — checked into git, visible in the Diwan dashboard, lossless distillates for fast LLM hydration
 - **3 execution modes**: parallel debate (`/rihal:council`), sequential pipelines (`/rihal:chain`), and quick-sync (`/rihal:discuss`)
 - **File-based state** in `.rihal/` that every workflow reads and updates
 - **Intent guards** on every workflow — catch wrong commands early with copy-paste redirects
@@ -48,6 +65,8 @@ Most AI tools give you one assistant pretending to be everything. **Rihal Code g
 - **Post-execute gates** (integration-checker, nyquist-auditor) verify completeness
 - **Global agents** at `~/.rihal/agents/` — customize without forking
 
+See [`MIGRATIONS.md`](MIGRATIONS.md) if you're upgrading from a pre-Memory-Bank install.
+
 It's not a chatbot. It's a methodology.
 
 ---
@@ -65,9 +84,9 @@ npx @hanzlaa/rcode install
 One unified installer. Pure file shipping, no runtime dependencies. Installs into:
 
 - `.rihal/` — config, workflows, references, bin (Rihal infrastructure)
-- `.claude/agents/` — 43 first-class subagents
-- `.claude/commands/rihal/` — 99 slash commands
-- `.claude/skills/` — 56 phrase-activated skills (scaffold-project, create-prd, prfaq, retrospective, etc.)
+- `.claude/agents/` — 45 first-class subagents
+- `.claude/commands/rihal/` — 95 slash commands
+- `.claude/skills/` — 80 phrase-activated skills (scaffold-project, create-prd, prfaq, memory-init, retrospective, etc.)
 - `rihal/brain/` — Rihal standards pulled from upstream (PR / commit / architecture docs)
 - `.planning/` — where your artifacts land (council sessions, plans, chains, summaries)
 
@@ -111,7 +130,7 @@ npx @hanzlaa/rcode install --ide gemini
 /rihal:plan --research build a rental app    → researcher grounds, plan-checker verifies
 /rihal:execute .planning/plans/01/PLAN.md    → atomic commits + post-gates
 /rihal:status                                → phases, decisions, blockers, sessions
-/rihal:karpathy-audit HEAD~5..HEAD           → audit changes vs 4 coding principles
+/rihal:code-review HEAD~5..HEAD --karpathy   → audit changes vs 4 coding principles
 ```
 
 ---
@@ -165,7 +184,7 @@ npx @hanzlaa/rcode install --ide gemini
 - **Execution**: rihal-executor, rihal-planner, rihal-verifier, rihal-plan-checker, rihal-debugger
 - **Discovery**: rihal-codebase-mapper, rihal-project-researcher, rihal-roadmapper, rihal-phase-researcher, rihal-advisor-researcher, rihal-assumptions-analyzer, rihal-research-synthesizer
 - **Verification**: rihal-integration-checker, rihal-nyquist-auditor
-- **Quality**: rihal-tech-writer, rihal-ux-designer, rihal-architect, rihal-code-reviewer, rihal-code-fixer, rihal-edge-case-hunter, rihal-deviation-analyzer
+- **Quality**: rihal-noor, rihal-ux-designer, rihal-code-reviewer, rihal-code-fixer, rihal-edge-case-hunter, rihal-deviation-analyzer
 - **And more**: rihal-docs-auditor, rihal-doc-verifier, rihal-doc-writer, rihal-repo-metrics, rihal-security-auditor, etc.
 
 **Customize globally:** Define reusable agents in `~/.rihal/agents/rihal-<name>.md`. They appear in every project alongside project-local agents, without forking the repo.
@@ -256,11 +275,11 @@ Amazon's "Working Backwards" method: write the finished-product press release *b
 3. **Surgical changes** — touch only what's needed, match existing style
 4. **Goal-driven execution** — define verifiable success criteria
 
-`/rihal:karpathy-audit` runs these 4 principles as a post-hoc audit against any diff or phase. Use it after implementation to catch bloated, over-engineered, or scope-creeping changes before they land in a PR.
+`/rihal:code-review --karpathy` runs these 4 principles as a post-hoc audit against any diff or phase. Use it after implementation to catch bloated, over-engineered, or scope-creeping changes before they land in a PR.
 
 ```
-/rihal:karpathy-audit HEAD~5..HEAD
-/rihal:karpathy-audit 03 --files=src/auth/
+/rihal:code-review HEAD~5..HEAD --karpathy
+/rihal:code-review 03 --files=src/auth/ --karpathy
 ```
 
 ### Plan verification + post-execute gates
@@ -309,13 +328,13 @@ Recent additions in this session:
 
 ---
 
-## Full command surface (99 commands)
+## Full command surface (95 commands)
 
 ### Router + lifecycle
 `init` · `do` · `help` · `status` · `stats` · `health` · `forensics` · `update`
 
 ### Discovery + research
-`new-project` · `map-codebase` · `scan` · `explore` · `document-project` · `analyze-dependencies` · `discuss-phase-power`
+`new-project` · `map-codebase` · `scan` · `explore` · `document-project` · `analyze-dependencies`
 
 ### Discovery + validation
 `prfaq` · `brainstorm` · `market-research` · `domain-research` · `technical-research` · `product-brief`
@@ -324,10 +343,10 @@ Recent additions in this session:
 `plan` · `chain` · `create-epics-and-stories` · `create-story` · `dev-story` · `sprint-planning`
 
 ### Execution
-`execute` · `quick` · `autonomous` · `audit-fix` · `undo` · `check-implementation-readiness`
+`execute` · `quick` · `autonomous` · `audit-fix` · `undo`
 
 ### Observability + review
-`code-review` · `code-review-fix` · `review-adversarial` · `review-edge-case-hunter` · `karpathy-audit` · `checkpoint-preview` · `secure-phase` · `show` · `why` · `rerun` · `diff`
+`code-review` · `code-review-fix` · `checkpoint-preview` · `secure-phase` · `show` · `why` · `rerun` · `diff`
 
 ### Recovery + correction
 `pause-work` · `resume-work` · `correct-course` · `next` · `config`
@@ -446,8 +465,8 @@ Every install runs 5 automated smoke tests before exiting:
     ✓ rihal-tools.cjs runs — syntax ok
     ✓ .rihal/config.yaml present — 412 bytes
     ✓ .rihal/state.json parses — valid JSON
-    ✓ agents installed — 43
-    ✓ skills + commands installed — 56 skills + 99 commands
+    ✓ agents installed — 45
+    ✓ skills + commands installed — 80 skills + 95 commands
 ```
 
 A failed check prints the debug command and returns exit code 1 so CI catches broken installs.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@hanzlaa/rcode",
-  "version": "2.8.0",
-  "description": "Rihal Code (rcode) — installable context-brain for Rihalians. 43 agents, 99 slash commands, 56 skills, pullable Rihal standards. Unified install for Claude Code, Cursor, and Gemini.",
+  "version": "3.1.0",
+  "description": "rcode — the memory bank for AI-driven SaaS teams. Persistent project context, distinctive engineering personas, and phase-based workflows. Built by Rihal. Works in Claude Code, Cursor, and Gemini.",
   "main": "cli/index.js",
   "bin": {
     "rcode": "dist/rcode.js",

package/rihal/agents/rihal-advisor-researcher.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-advisor-researcher
 description: Researches a single gray area decision and returns a structured comparison table with rationale. Spawned by discuss-phase advisor mode.
-tools: read_file, run_shell_command, search_file_content, glob, google_web_search, web_fetch
+tools: Read, Bash, Grep, Glob, WebSearch, WebFetch
 color: cyan
 ---
 

package/rihal/agents/rihal-assumptions-analyzer.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-assumptions-analyzer
 description: Deeply analyzes codebase for a phase and returns structured assumptions with evidence. Spawned by discuss-phase assumptions mode.
-tools: read_file, run_shell_command, search_file_content, glob
+tools: Read, Bash, Grep, Glob
 color: cyan
 ---
 

package/rihal/agents/rihal-codebase-mapper.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-codebase-mapper
 description: Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents directly to reduce orchestrator context load.
-tools: read_file, run_shell_command, search_file_content, glob, write_file
+tools: Read, Bash, Grep, Glob, Write
 color: cyan
 ---
 

package/rihal/agents/rihal-docs-auditor.md

@@ -15,7 +15,7 @@ You are the **Documentation Auditor** at Rihal. You are spawned to audit documen
 
 ## Who you are
 
-Documentation quality specialist. You assess whether critical documentation exists, is accurate, and is discoverable. You identify gaps: missing README sections, undocumented APIs, outdated examples, broken links. You defer to rihal-tech-writer for content creation and Waleed (CTO) for technical accuracy disputes.
+Documentation quality specialist. You assess whether critical documentation exists, is accurate, and is discoverable. You identify gaps: missing README sections, undocumented APIs, outdated examples, broken links. You defer to rihal-noor for content creation and Waleed (CTO) for technical accuracy disputes.
 
 You do not write documentation. You audit and flag issues.
 
@@ -63,9 +63,9 @@ Structured: Coverage summary → Missing docs → Accuracy gaps → Quality issu
 
 Use command-redirect-format.md. One reason, then command.
 
-- Documentation writing → rihal-tech-writer
+- Documentation writing → rihal-noor
 - Technical accuracy verification → Waleed (CTO)
-- Content updates → rihal-tech-writer
+- Content updates → rihal-noor
 
 ## Constraints
 

package/rihal/agents/rihal-executor.md

@@ -17,6 +17,16 @@ Rihal sprint executor. Execute SPRINT.md files atomically, commit each story, ha
 **Mandatory Initial Read:** If prompt contains `<files_to_read>`, read every file listed before any other action.
 </role>
 
+## Project-specific constraints to load (every invocation)
+
+Before executing any commits, load these constraints — they're what new executors get wrong on day one (see #444 for the original incident):
+
+- **`.planning/` may be gitignored.** Many Rihal-style projects gitignore the planning directory. To commit SUMMARY.md, VERIFICATION.md, or any other artefact under `.planning/`, you must use `git add -f <path>`. Without `-f`, the file is silently not staged and your commit doesn't include it.
+- **Read `.rihal/config.yaml`** — if `workflow.commit_planning: true`, planning artefacts SHOULD be committed; use `git add -f` for each file under `.planning/`. If `commit_planning: false`, skip the commit step for those files entirely.
+- **Read `.rihal/context/active.md`** — the user may have logged additional project-specific constraints there (deploy gates, secret-handling rules, branch-naming overrides). Honour them.
+
+If you commit a file under `.planning/` and `git status` afterwards still shows it as modified or untracked, you forgot the `-f` flag. Re-stage with `git add -f` and amend the commit (a NEW commit; never `git commit --amend` on a pushed commit).
+
 ## Execution Flow (Slim)
 
 1. **Load state** — Extract executor config, phase info, sprint list. Read STATE.md for position/blockers.

package/rihal/agents/rihal-integration-checker.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-integration-checker
 description: Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
-tools: read_file, run_shell_command, search_file_content, glob
+tools: Read, Bash, Grep, Glob
 color: blue
 ---
 

package/rihal/agents/rihal-noor.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-noor
-description: Technical Writer & Presentation Lead — spawned by /rihal:council for documentation, README files, API docs, architecture diagrams (Mermaid), changelogs, pitch decks, and blog posts. Defers to Hussain-PM on PRD content, Hanzla on code implementation details, Sadiq on strategic framing.
-tools: Read, Grep, Glob, Bash, WebFetch
+description: Technical Writer & Presentation Lead — spawned by /rihal:council and /rihal:docs-update for README files, API docs, architecture diagrams (Mermaid), changelogs, migration guides, inline code comments, pitch decks, and blog posts. Defers to Hussain-PM on PRD content, Hanzla on code implementation details, Sadiq on strategic framing.
+tools: Read, Write, Edit, Grep, Glob, Bash, WebFetch
 color: teal
 ---
 

package/rihal/agents/rihal-phase-researcher.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-phase-researcher
 description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by rihal-planner. Spawned by /rihal:plan orchestrator.
-tools: read_file, write_file, run_shell_command, search_file_content, glob, google_web_search, web_fetch
+tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 color: cyan
 ---
 

package/rihal/agents/rihal-planner.md

@@ -116,6 +116,31 @@ else: wave = max(waves of dependencies) + 1
 
 **File ownership:** No overlap in files_modified → can run parallel. Overlap → later depends on earlier.
 
+## File-existence verification (BLOCKER — added in v3.1.0 after #441)
+
+Before writing each entry into `files_modified`, you MUST verify the file actually exists in the project. Plans with fictional file names cause executors to scramble at runtime.
+
+For every candidate path:
+
+```bash
+# Try the exact name first
+test -f "<candidate>" && echo "OK" && exit 0
+
+# Then try a fuzzy match for renamed/moved files
+find . -type f \( -name "<basename>" -o -iname "*$<short-slug>*" \) \
+  -not -path './node_modules/*' -not -path './.git/*' 2>/dev/null
+```
+
+Apply these rules to every path you put in `files_modified`:
+
+- **Exact match exists** → use the verified path verbatim
+- **No exact match, fuzzy match found** → use the fuzzy match's path AND log a note in the SPRINT.md frontmatter (`renamed_from: <original candidate>`)
+- **Neither exact nor fuzzy match** → DO NOT add the path to `files_modified`. Either:
+  - Mark it as a CREATE story (the executor will create the file fresh) — set `creates: [<path>]` in the story body
+  - OR raise a BLOCKER finding for sprint-checker to surface: file referenced by name but not present and not flagged for creation
+
+Sprint-checker enforces this — see `rihal-sprint-checker.md` Mandatory Output Markers section. Plans that claim to modify non-existent files without a CREATE marker are rejected.
+
 ## Plan Structure
 
 ```markdown

package/rihal/agents/rihal-project-researcher.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-project-researcher
 description: Researches domain ecosystem before roadmap creation. Produces files in .rihal/research/ consumed during roadmap creation. Spawned by /rihal:new-project or /rihal:new-milestone orchestrators.
-tools: read_file, write_file, run_shell_command, search_file_content, glob, google_web_search, web_fetch
+tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch
 color: cyan
 ---
 

package/rihal/agents/rihal-research-synthesizer.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-research-synthesizer
 description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /rihal:new-project after 4 researcher agents complete.
-tools: read_file, write_file, run_shell_command
+tools: Read, Write, Bash
 color: purple
 ---
 

package/rihal/agents/rihal-roadmapper.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-roadmapper
 description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /rihal:new-project orchestrator.
-tools: read_file, write_file, run_shell_command, glob, search_file_content
+tools: Read, Write, Bash, Glob, Grep
 color: purple
 ---
 

package/rihal/agents/rihal-sprint-checker.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-sprint-checker
 description: Verifies sprints will achieve phase goal before execution. Goal-backward analysis of sprint quality. Spawned by /rihal:plan orchestrator.
-tools: read_file, run_shell_command, glob, search_file_content
+tools: Read, Bash, Glob, Grep
 color: green
 ---
 
@@ -108,6 +108,24 @@ Each dimension has pass/partial/fail criteria, remediation guidance, and output
 3. **Synthesize** — Produce CHECK.md with overall verdict, per-dimension scores, remediation asks.
 4. **Return** — Block execution if critical dimensions fail; proceed with cautions if only partials.
 
+## Mandatory output markers (per #440 / #445 fix)
+
+Every return from this agent MUST include at least one of these YAML markers — they prove tool invocation actually happened. The orchestrator's malfunction guard in `plan.md` blocks execution if none are present.
+
+```yaml
+issues:           # always emit, even if empty (issues: [])
+  - dimension: <name>
+    severity: BLOCKER | WARNING | INFO
+    path: <file:line>
+    finding: <short text>
+
+verified_files:   # list every file actually read during verification
+  - path: <relative path>
+    bytes: <int>
+```
+
+If you have not invoked `Read`, `Bash`, `Grep`, or `Glob` during execution, do NOT return — instead, report the failure and stop. Empty narrative output is treated as malfunction, not pass.
+
 ## On-Demand Rule Files
 
 | When you need... | Read |

package/rihal/agents/rihal-verifier.md

@@ -1,7 +1,7 @@
 ---
 name: rihal-verifier
 description: Verifies phase goal achievement through goal-backward analysis. Checks codebase delivers what phase promised, not just that tasks completed. Creates VERIFICATION.md report.
-tools: read_file, write_file, run_shell_command, search_file_content, glob
+tools: Read, Write, Bash, Grep, Glob
 color: green
 ---
 

package/rihal/agents/rihal-waleed.md

@@ -43,7 +43,7 @@ Precise. Quantified. Trade-off oriented. Every claim cites a number, a constrain
 | Code | Description | Skill / workflow |
 |------|-------------|------------------|
 | ADR  | Write a single Architecture Decision Record | rihal-create-architecture |
-| RV   | Review existing architecture against current code | rihal-architect |
+| RV   | Review existing architecture against current code | inline |
 | TS   | Stack selection — 2-3 options + recommendation | inline |
 | FZ   | Feasibility check — can the current stack handle this? | inline |
 | KS   | Kill-switch design — exit criteria, sunset plan | inline |
@@ -64,7 +64,6 @@ Always read on activation:
 - Test / QA → Fatima
 - Backend impl detail → Yousef
 - Frontend → Haitham
-- Greenfield system design / multi-team org bets → rihal-architect (senior tier)
 
 ## Constraints (Waleed-specific)
 

package/rihal/commands/code-review.md

@@ -1,7 +1,7 @@
 ---
 name: rihal:code-review
 description: Review source files for bugs, security issues, and code quality problems.
-argument-hint: "<phase> [--depth=quick|standard|deep] [--files=file1,file2,...]"
+argument-hint: "<phase> [--depth=quick|standard|deep] [--files=file1,file2,...] [--karpathy] [--attack] [--edge-cases]"
 allowed-tools:
   - Read
   - Grep

package/rihal/commands/memory-audit.md

@@ -0,0 +1,10 @@
+---
+name: rcode:memory-audit
+description: Audit the Memory Bank for stale entries, contradictions, and unfilled placeholders — read-only report
+argument-hint: "[--severity {critical|warn|info}]"
+allowed-tools:
+  - Read
+  - Bash
+---
+
+@.rihal/workflows/memory-audit.md

package/rihal/commands/memory-distill.md

@@ -0,0 +1,11 @@
+---
+name: rcode:memory-distill
+description: Regenerate Memory Bank distillates — token-optimised lossless compressions for fast LLM context loading
+argument-hint: "[--force] [--target {project|stack|all}]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+@.rihal/workflows/memory-distill.md

package/rihal/commands/memory-init.md

@@ -0,0 +1,12 @@
+---
+name: rcode:memory-init
+description: Bootstrap the rcode Memory Bank for this project — copies templates, asks 5 questions, populates seed files
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+@.rihal/workflows/memory-init.md

package/rihal/commands/memory-update.md

@@ -0,0 +1,12 @@
+---
+name: rcode:memory-update
+description: Append a decision, known issue, stakeholder, or milestone update to the Memory Bank from conversation context
+argument-hint: "<content>"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+@.rihal/workflows/memory-update.md

package/rihal/config/model-profiles.json

@@ -41,7 +41,7 @@
         "ux-designer": "sonnet",
         "doc-verifier": "haiku",
         "docs-auditor": "haiku",
-        "tech-writer": "haiku"
+        "noor": "haiku"
       }
     },
 
@@ -82,7 +82,7 @@
         "ux-designer": "sonnet",
         "doc-verifier": "haiku",
         "docs-auditor": "haiku",
-        "tech-writer": "haiku"
+        "noor": "haiku"
       }
     },
 
@@ -123,7 +123,7 @@
         "ux-designer": "haiku",
         "doc-verifier": "haiku",
         "docs-auditor": "haiku",
-        "tech-writer": "haiku"
+        "noor": "haiku"
       }
     },
 
@@ -164,7 +164,7 @@
         "ux-designer": "inherit",
         "doc-verifier": "inherit",
         "docs-auditor": "inherit",
-        "tech-writer": "inherit"
+        "noor": "inherit"
       }
     }
   },
@@ -197,7 +197,7 @@
       "model_overrides": {
         "waleed": "opus",
         "code-reviewer": "sonnet",
-        "tech-writer": "inherit"
+        "noor": "inherit"
       }
     }
   },

package/rihal/references/karpathy-guidelines-full.md

@@ -69,7 +69,7 @@ Strong success criteria let you loop independently. Weak criteria ("make it work
 
 ## Enforcement
 
-Agents that write or modify code (rihal-executor, rihal-planner, rihal-tech-writer, rihal-codebase-mapper when producing code docs) must:
+Agents that write or modify code (rihal-executor, rihal-planner, rihal-noor, rihal-codebase-mapper when producing code docs) must:
 1. @-include this file
 2. Apply the 4 principles as hard constraints, not suggestions
 3. Reference the specific principle when refusing to make a change (e.g., "Declining per Karpathy #3: that's adjacent to the requested change but not part of it")

package/rihal/references/no-unauthorized-git-ops.md

@@ -60,7 +60,7 @@ Spawn the debug agent with git worktree isolation?
 
 ## Agent enforcement
 
-Every Rihal agent that can execute shell commands (rihal-executor, rihal-debugger, rihal-planner, rihal-tech-writer, etc.) must:
+Every Rihal agent that can execute shell commands (rihal-executor, rihal-debugger, rihal-planner, rihal-noor, etc.) must:
 
 1. Reject any prompt asking them to perform a banned operation without a prior user-confirmed authorization in their input
 2. Surface a warning if a parent workflow or user prompt tries to include a banned flag

package/rihal/references/verb-dictionary.md

@@ -87,7 +87,7 @@ These are matched alongside §Create / §Add / §Plan verbs to determine the dis
 | 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:karpathy-audit` / `/rihal:code-review` |
+| review (code) | `code review`, `karpathy`, `check my diff` | `/rihal:code-review [--karpathy]` |
 | debug | `debug`, `fix`, `bug`, `error`, `crash`, `kharab`, `theek` | `/rihal:debug` |
 
 ---