@hanzlaa/rcode 4.4.3 → 4.5.0

package/rcode/data/intent-table.json

@@ -1,87 +1,87 @@
 [
   {
     "intent": "new-project",
-    "keywords": ["set up a new project", "initialize a new project", "start a new project", "create a new project"],
+    "keywords": ["set up a new project", "initialize a new project", "start a new project", "create a new project", "naya project shuru karo", "naya project banao", "مشروع جديد", "ابدأ مشروع جديد"],
     "command": "/rcode-new-project"
   },
   {
     "intent": "map-codebase",
-    "keywords": ["map the codebase", "map this codebase", "analyze the codebase", "analyse the codebase", "map existing codebase"],
+    "keywords": ["map the codebase", "map this codebase", "analyze the codebase", "analyse the codebase", "map existing codebase", "codebase samjhao", "code ka structure dikhao", "حلل الكود", "افهم هيكل المشروع"],
     "command": "/rcode-map-codebase"
   },
   {
     "intent": "debug",
-    "keywords": ["bug", "getting an error", "throwing an error", "error in the", "fix the error", "debug this", "crash", "failure", "broken", "not working", "fails", "exception", "traceback"],
+    "keywords": ["bug", "getting an error", "throwing an error", "error in the", "fix the error", "debug this", "crash", "failure", "broken", "not working", "fails", "exception", "traceback", "kharab", "masla", "ye kaam nahi kar raha", "yeh kaam nahi kar raha", "error a raha hai", "theek karo", "khud se crash", "خطأ", "مشكلة", "لا يعمل", "أصلح الخطأ", "تعطل البرنامج"],
     "command": "/rcode-debug"
   },
   {
-    "intent": "audit-karpathy",
-    "keywords": ["audit", "review changes", "check my diff", "karpathy", "too complex", "complexity", "code review"],
-    "command": "/rcode-review --karpathy"
+    "intent": "karpathy-audit",
+    "keywords": ["review changes", "check my diff", "karpathy", "too complex", "complexity", "diff check karo", "پیچیدہ کوڈ", "تحقق من التغييرات"],
+    "command": "/rcode-karpathy-audit"
   },
   {
     "intent": "lazy",
-    "keywords": ["be lazy", "lazy mode", "simplest solution", "yagni", "over-engineered", "over-engineering", "kam code likho"],
+    "keywords": ["be lazy", "lazy mode", "simplest solution", "yagni", "over-engineered", "over-engineering", "kam code likho", "asaan tareeqa", "سهل الحل", "أبسط طريقة"],
     "command": "/rcode-lazy"
   },
   {
     "intent": "checkpoint",
-    "keywords": ["checkpoint", "explain this diff", "human review", "walk through the change", "walk through this change"],
+    "keywords": ["checkpoint", "explain this diff", "human review", "walk through the change", "walk through this change", "diff samjhao", "اشرح هذا التغيير"],
     "command": "/rcode-checkpoint-preview"
   },
   {
     "intent": "brainstorm",
-    "keywords": ["brainstorm", "generate ideas", "explore options", "what could we do", "ideate", "ideas for"],
+    "keywords": ["brainstorm", "generate ideas", "explore options", "what could we do", "ideate", "ideas for", "ideas do", "hum kya kar sakte hain", "أفكار", "ما الذي يمكننا فعله"],
     "command": "/rcode-brainstorm"
   },
   {
     "intent": "explore",
-    "keywords": ["explore", "research phase", "do some research", "comparing", "investigate", "look into", "understand how"],
+    "keywords": ["explore", "research phase", "do some research", "comparing", "investigate", "look into", "understand how", "research karo", "pata karo", "ابحث عن", "قارن بين"],
     "command": "/rcode-research-phase"
   },
   {
     "intent": "discuss",
-    "keywords": ["which one", "better ux", "how should", "still have confusion", "conflicting", "discuss the scope", "design this", "architect this"],
+    "keywords": ["which one", "better ux", "how should", "still have confusion", "conflicting", "discuss the scope", "design this", "architect this", "confusion hai", "kaunsa behtar hai", "أيهما أفضل", "لست متأكداً"],
     "command": "/rcode-discuss-phase"
   },
   {
     "intent": "add-phase",
-    "keywords": ["refactor", "migration", "multi-file", "system redesign", "multi file", "large refactor", "architectural", "integration", "integrate"],
+    "keywords": ["refactor", "migration", "multi-file", "system redesign", "multi file", "large refactor", "architectural", "integration", "integrate", "poora refactor karo", "migration karna hai", "إعادة هيكلة", "ترحيل النظام"],
     "command": "/rcode-add-phase"
   },
   {
     "intent": "sprint-planning",
-    "keywords": ["sprint planning", "plan the sprint", "next sprint", "what's in this sprint"],
+    "keywords": ["sprint planning", "plan the sprint", "next sprint", "what's in this sprint", "sprint plan karo", "تخطيط السبرنت"],
     "command": "/rcode-sprint-planning"
   },
   {
     "intent": "execute-sprint",
-    "keywords": ["run the sprint", "start sprint", "execute sprint", "work on sprint"],
+    "keywords": ["run the sprint", "start sprint", "execute sprint", "work on sprint", "sprint chalao", "sprint shuru karo", "نفذ السبرنت", "ابدأ السبرنت"],
     "command": "/rcode-execute-sprint"
   },
   {
     "intent": "plan",
-    "keywords": ["let's plan", "plan phase", "plan this", "let me plan", "planning phase", "create a plan", "please plan", "plan and think", "scope this", "scope the feature"],
+    "keywords": ["let's plan", "plan phase", "plan this", "let me plan", "planning phase", "create a plan", "please plan", "plan and think", "scope this", "scope the feature", "plan banao", "isko plan karo", "خطط لهذا", "أنشئ خطة"],
     "command": "/rcode-plan"
   },
   {
     "intent": "new-milestone",
-    "keywords": ["create milestones", "plan milestones", "create roadmap", "break project into milestones", "new milestone", "what milestones"],
+    "keywords": ["create milestones", "plan milestones", "create roadmap", "break project into milestones", "new milestone", "what milestones", "milestones banao", "خطة الطريق", "مراحل المشروع"],
     "command": "/rcode-new-milestone"
   },
   {
     "intent": "epics-stories",
-    "keywords": ["create epics", "user stories", "create stories", "epics and stories", "break into epics"],
+    "keywords": ["create epics", "user stories", "create stories", "epics and stories", "break into epics", "stories banao", "قصص المستخدم", "أنشئ ملاحم"],
     "command": "/rcode-create-epics-and-stories"
   },
   {
     "intent": "feature-drift",
-    "keywords": ["out of date", "out-of-date", "verify docs", "audit feature docs", "fill out existing", "prd drift", "docs vs code"],
+    "keywords": ["out of date", "out-of-date", "verify docs", "audit feature docs", "fill out existing", "prd drift", "docs vs code", "docs purane hain", "الوثائق قديمة", "تحقق من التوثيق"],
     "command": "/rcode-feature-drift"
   },
   {
     "intent": "audit",
-    "keywords": ["re-audit", "extend the audit", "fill out the", "expand the", "re audit"],
+    "keywords": ["re-audit", "extend the audit", "fill out the", "expand the", "re audit", "audit", "code review", "dobara audit karo", "audit karo", "code review karo", "دقق الكود", "مراجعة الكود", "راجع التغييرات"],
     "command": "/rcode-audit"
   }
 ]

package/rcode/templates/memory/INDEX.md

@@ -1,6 +1,8 @@
 # Memory Bank — `{{PROJECT_NAME}}`
 
-> The Memory Bank is your project's persistent brain. AI agents read from here on every session. You write to it as work happens. Survives session resets, team changes, and AI memory limits.
+> The Memory Bank is your project's persistent brain. Full read/write access is on-demand: run `/rcode-memory-init` to scaffold it, `/rcode-memory-update` after work happens, `/rcode-memory-distill` to regenerate the compressed distillates, and `/rcode-memory-audit` to check it for staleness. Ambient injection also runs automatically (#958): the `session-start` hook emits its usual one-line phase-status primer from `.rcode/state.json`, then — when this directory exists and has content — a relevance-ranked selector (`rcode/bin/lib/memory-select.cjs`) scores every file here against the current phase, git branch, and recently touched files, and injects the top-scoring excerpts as `additionalContext` within a ~1500-token budget (override via `.rcode/config.yaml`'s `memory_inject_budget`). The `pre-compact` hook does the same with a smaller ~600-token budget as part of its survival context. This keeps agents grounded in relevant memory without a human having to run a `/rcode-memory-*` command first — full manual review is still the way to go deep.
+>
+> A `post-commit` hook runs a lightweight drift check after every commit (#958): it compares `project/stack.md` and `project/decisions.md` claims against the last 10 commits and the current working tree — removed/added dependencies, referenced files/dirs that no longer exist, and an `INDEX.md` older than 30 days. If it finds anything, it nudges you toward `/rcode-memory-update` once per session. Run `rcode-hooks drift` (or `node .rcode/bin/rcode-hooks.cjs drift` if the CLI isn't on your PATH) anytime for the full report.
 
 **Last updated:** {{INIT_DATE}}
 
@@ -27,6 +29,8 @@
 
 ## Token budget guide
 
+- **Ambient session-start injection** (~1.5K tokens, `memory_inject_budget`) — automatic, relevance-ranked, no command needed
+- **Ambient pre-compact injection** (~600 tokens) — automatic survival context alongside `HANDOFF.json`
 - **`INDEX.md` only** (~500 tokens) — quick orientation
 - **`INDEX.md` + `distillates/project.distillate.md`** (~5K tokens) — standard session start
 - **Full `project/` directory** (~10–15K tokens) — deep planning
@@ -39,6 +43,7 @@
 - **`incidents/known-issues.md`** — add when a workaround ships, remove when a real fix lands
 - **`distillates/`** — regenerate via `/rcode-memory-distill` when source files change
 - **Whole bank** — audit via `/rcode-memory-audit` at every milestone close
+- **Drift check** — runs automatically on every commit; run `rcode-hooks drift` manually anytime, or after a large dependency/refactor change
 
 ## Constraints
 

package/rcode/templates/settings-hooks.json

@@ -1,5 +1,5 @@
 {
-  "_comment": "pre-edit hook is currently advisory (logs warning, does not block). Full session-read tracking requires PostToolUse Read hook to write state file. Implemented in follow-up. prompt-router (UserPromptSubmit) is advisory — emits additionalContext to nudge toward the right rcode command; never blocks.",
+  "_comment": "pre-edit hook is currently advisory (logs warning, does not block). Full session-read tracking requires PostToolUse Read hook to write state file. Implemented in follow-up. prompt-router (UserPromptSubmit) is advisory — emits additionalContext to nudge toward the right rcode command; never blocks. session-start (SessionStart) emits a one-line project status primer at session open.",
   "hooks": {
     "PreToolUse": [
       {
@@ -85,6 +85,17 @@
           }
         ]
       }
+    ],
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .rcode/bin/rcode-hooks.cjs session-start"
+          }
+        ]
+      }
     ]
   }
 }

package/rcode/workflows/do.md

@@ -290,7 +290,7 @@ Evaluate `$QUESTION` against these routing rules. Apply the **first matching** r
 | A bug, error, crash, failure, or something broken | `/rcode-debug` | Needs systematic investigation |
 | Validate an idea, "working backwards", "press release", "PRFAQ", "is this worth building" | `/rcode-prfaq` | Stress-test concept before committing sprint capacity |
 | Brainstorm, generate ideas, "explore options", "what could we do" | `/rcode-brainstorm` | Structured ideation before planning |
-| Audit code quality, "review changes", "karpathy", "check my diff", "too complex" | `/rcode-review --karpathy` | 4-principle code audit against recent diff |
+| "karpathy", "review changes", "check my diff", "too complex" — 4-principle code audit against a diff | `/rcode-karpathy-audit` | Runs the karpathy-audit workflow directly (review.md has no `--karpathy` flag) |
 | Make it simpler, "be lazy", "lazy mode", "simplest solution", "yagni", "over-engineered", "kam code likho" | `/rcode-lazy` | Generative simplicity lens — YAGNI before code is written (rcode-trim removes bloat after the fact) |
 | Walk through a change, "checkpoint", "explain this diff", "human review" | `/rcode-checkpoint-preview` | Human-in-the-loop diff walkthrough |
 | Exploring, researching, comparing, or "how does X work" | `/rcode-research-phase` | Domain research before planning |
@@ -317,7 +317,7 @@ Evaluate `$QUESTION` against these routing rules. Apply the **first matching** r
 | Adding tests, "write tests", "test coverage" | `/rcode-add-tests` | Test generation |
 | Completing a milestone, shipping, releasing | `/rcode-complete-milestone` | Milestone lifecycle |
 | Drift / out-of-date / "verify docs vs code" / "audit feature docs" / "fill out existing PRD/epics/stories" | `/rcode-feature-drift` | Detects PRD↔epics↔stories↔code drift; --fix patches trivial items |
-| General audit / re-audit / extend / fill out / expand an existing artifact | `/rcode-audit` | Unified audit entry — picks artifact type and re-runs |
+| Bare "audit" / "code review" / re-audit / extend / fill out / expand an existing artifact | `/rcode-audit` | Unified audit entry — disambiguates plans/phase/milestone/UAT/code before dispatching |
 > **SEO route guard:** Skills in this block assume a project context exists (`.planning/PROJECT.md`). If absent, the `HAS_PRD` check in `<step name="check_project">` redirects to `/rcode-new-project`.
 
 | **— SEO / Content intent —** | | |

package/rcode/workflows/enable-hooks.md

@@ -1,7 +1,7 @@
 # Workflow: rcode-enable-hooks
 
 <purpose>
-Merge rcode opt-in hooks from settings-hooks.json into .claude/settings.json. Creates settings.json if missing. Enables all 9 guardrails: pre-edit (read-before-edit check), pre-workflow (command hint), post-commit (format validation), bash-guard (blocks dangerous commands), pre-compact (refreshes HANDOFF.json before context compaction), stop-verify (syntax-checks files changed during the response), cost-track (logs measured token usage to .rcode/telemetry/cost.jsonl), compact-nudge (advises /rcode-trim or /clear after many edits), and prompt-router (proactive nudge toward the right rcode command for long-term memory consistency).
+Merge rcode opt-in hooks from settings-hooks.json into .claude/settings.json. Creates settings.json if missing. Enables all 10 guardrails: pre-edit (read-before-edit check), pre-workflow (command hint), post-commit (format validation), bash-guard (blocks dangerous commands), pre-compact (refreshes HANDOFF.json before context compaction), stop-verify (syntax-checks files changed during the response), cost-track (logs measured token usage to .rcode/telemetry/cost.jsonl), compact-nudge (advises /rcode-trim or /clear after many edits), prompt-router (proactive nudge toward the right rcode command for long-term memory consistency), and session-start (SessionStart — one-line project status primer at session open).
 </purpose>
 
 
@@ -44,7 +44,7 @@ If `.claude/` directory does not exist, create it first.
 
 ## Step 3 — Merge hooks
 
-For each hook type (`PreToolUse`, `PostToolUse`, `PreCompact`, `Stop`, `UserPromptSubmit`):
+For each hook type (`PreToolUse`, `PostToolUse`, `PreCompact`, `Stop`, `UserPromptSubmit`, `SessionStart`):
 
 - If the hook type does not exist in the current settings.json, add it.
 - If it exists, append the new matchers and hook commands (avoid duplicates by checking for exact command matches).
@@ -87,6 +87,7 @@ Enabled guardrails:
   • cost-track: Logs measured token usage to .rcode/telemetry/cost.jsonl
   • compact-nudge: Advises /rcode-trim or /clear after many edits
   • prompt-router: Nudges toward the matching /rcode-* command and /rcode-memory-update so work lands in .rcode/state.json (toggle via prompt_nudge in .rcode/config.yaml: every|once-per-intent|when-stale|off)
+  • session-start: Greets the session with one-line phase status and suggested next command
 
 To disable, remove the hooks section from .claude/settings.json or edit .rcode/templates/settings-hooks.json and re-run.
 ```

package/rcode/workflows/execute.md

@@ -871,7 +871,16 @@ The CLI handles:
 - Updating REQUIREMENTS.md traceability
 - Scanning for verification debt (returns `warnings` array)
 
-Extract from result: `next_phase`, `next_phase_name`, `is_last_phase`, `warnings`, `has_warnings`.
+Extract from result: `next_phase`, `next_phase_name`, `is_last_phase`, `warnings`, `has_warnings`, `open_phases_remaining`, `nudge`.
+
+**If `nudge` is present (#943 — no open phases remain, milestone finished):**
+Surface it verbatim so the user is guided forward instead of stranded:
+```
+✓ Milestone complete — all phases done.
+{nudge}
+```
+Do not auto-advance past a finished milestone; let the user choose
+`/rcode-complete-milestone` or `/rcode-new-milestone`.
 
 **If has_warnings is true:**
 ```

package/rcode/workflows/insert-phase.md

@@ -83,6 +83,14 @@ Next steps:
 Or continue with current work and return to this phase later.
 ```
 
+## Step 3.5 — Surface milestone-health nudge (#942)
+
+`state insert-phase` returns a `nudge` field when the milestone has too many
+open phases (≥8 = consider, ≥12 = should-close). If `RESULT.nudge` is present,
+print it verbatim so the user is guided toward `/rcode-complete-milestone` +
+`/rcode-new-milestone` instead of silently accumulating phases. If absent, say
+nothing.
+
 ## Anti-patterns
 
 - Don't insert before Phase 1 (decimal 0.1 makes no sense)

package/rcode/workflows/new-project-roadmap.md

@@ -302,12 +302,12 @@ Use AskUserQuestion:
 node .rcode/bin/rcode-tools.cjs generate-claude-md
 ```
 
-This ensures new projects get the default rcode workflow-enforcement guidance and current project context in `CLAUDE.md`.
+This ensures new projects get the default rcode workflow-enforcement guidance and current project context in `CLAUDE.md` and `AGENTS.md` (the cross-tool standard read by Codex, Cursor, Windsurf, Antigravity, and Gemini). `AGENTS.md` is only written when absent — an install-managed roster section is preserved.
 
 **Commit roadmap (after approval or auto mode):**
 
 ```bash
-node .rcode/bin/rcode-tools.cjs commit "docs: create roadmap ([N] phases)" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md CLAUDE.md
+node .rcode/bin/rcode-tools.cjs commit "docs: create roadmap ([N] phases)" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md CLAUDE.md AGENTS.md
 ```
 
 ## 9. Done

package/rcode/workflows/plan.md

@@ -906,6 +906,23 @@ node ".rcode/bin/rcode-tools.cjs" state planned-phase --phase "${PHASE_NUMBER}"
 
 This updates STATUS to "Ready to execute", sets the correct plan count, and timestamps Last Activity.
 
+## 13c. Milestone-health nudge (#942)
+
+After recording completion, check whether the milestone has accumulated too many
+open phases — so planning the Nth phase of a sprawling milestone guides the user
+toward closing it instead of silently growing the roadmap:
+
+```bash
+HEALTH=$(node ".rcode/bin/rcode-tools.cjs" milestone-health 2>/dev/null)
+REC=$(echo "$HEALTH" | node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>{try{console.log(JSON.parse(s).recommendation||'')}catch{console.log('')}})")
+OPEN=$(echo "$HEALTH" | node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>{try{console.log(JSON.parse(s).open_phases||0)}catch{console.log(0)}})")
+```
+
+- If `REC` is `should-close` (≥12 open): surface a hard nudge recommending
+  `/rcode-complete-milestone` then `/rcode-new-milestone`.
+- If `REC` is `consider-closing` (8–11 open): softer nudge.
+- If `healthy`: say nothing.
+
 ## 14. Present Final Status
 
 Route to `<offer_next>` OR `auto_advance` depending on flags/config.