@hanzlaa/rcode 4.0.0 → 4.1.1

package/rcode/skills/actions/4-implementation/rcode-herdr-orchestration/templates/wave-prompt.md

@@ -0,0 +1,69 @@
+# Wave-Agent Prompt Template
+
+Use this as the body of `herdr pane send-text` when dispatching each agent in a wave. Replace the placeholders.
+
+---
+
+```
+You are in an isolated worktree at <WORKTREE_PATH> on branch <BRANCH_NAME>. <REPO_NAME> repo.
+
+YOUR PARENT BRANCH IS <INTEGRATION_BRANCH> (NOT master). Your branch was forked from <INTEGRATION_BRANCH>. When you finish, the orchestrator will merge your branch INTO <INTEGRATION_BRANCH> (not master). Master stays untouched throughout the campaign.
+
+If you need to pull the latest parent work (rare, only between waves):
+  git fetch origin
+  git merge origin/<INTEGRATION_BRANCH> --no-edit
+
+CAMPAIGN MODE — pick top 3-5 pending P1/P2 items from <AUDIT_DOC_PATH> and ship them. Long-running autonomous fix campaign — your branch will be merged into the campaign integration branch when done.
+
+PROTOCOL
+1. Read <AUDIT_DOC_PATH> fully. Identify items marked pending, ⏳, [ ], TODO, or labeled P1/P2 that are NOT already shipped (cross-reference `git log <INTEGRATION_BRANCH>` to avoid double-fixing).
+2. Pick 3-5 items that are surgical, well-scoped, and unrelated to other in-flight campaign agents (no overlap with: <IN_FLIGHT_AREAS>).
+3. Implement each item as a small, separately-committed change. Conventional commit format (e.g. `fix(area): summary` / `feat(area): summary`). Each commit message must reference the audit finding.
+4. STRICT auto-heal from project CLAUDE.md while editing:
+   - super_admin in role filters
+   - no silent .catch(()=>{}) — use logger.warn with reason
+   - no React.FC, no style={{}}, no raw <button> (use Button component)
+   - no alert()/confirm() — use toast/AlertDialog
+   - Prisma schema changes need migration files via `prisma migrate dev --create-only --name <slug>`
+   - new /api routes need server/middleware/routeSecurity.js MANIFEST entries
+5. Keep TSC at baseline. Run `pnpm tsc --noEmit` before final commit. If you introduce a NEW error, fix it before committing.
+6. STAY on branch <BRANCH_NAME>. Do NOT push. Do NOT merge to master. Do NOT merge to <INTEGRATION_BRANCH>. Do NOT touch other audit areas.
+7. End with a short numbered summary listing each commit (hash + one-line message) and what audit item it addressed.
+
+DO NOT
+- Touch master at all
+- Merge into the integration branch (the orchestrator does that — your job is to commit on your own branch and stop)
+- Touch out-of-scope code outside the audit area
+- Add new abstractions or refactor wholesale
+- Make schema changes without a migration file
+- Write tests "as a bonus" unless the audit specifically called for them
+- Push to origin
+
+Begin by reading the audit doc and listing the candidate items you'll fix.
+```
+
+---
+
+## Placeholders
+
+| Placeholder | Source |
+|---|---|
+| `<WORKTREE_PATH>` | `../sm-worktrees/camp-<area>` |
+| `<BRANCH_NAME>` | `campaign-<area>` |
+| `<INTEGRATION_BRANCH>` | `campaign-integration` (default) or `campaign-<topic>` for named campaigns |
+| `<REPO_NAME>` | e.g. `LeadLyze` |
+| `<AUDIT_DOC_PATH>` | `.planning/audits/AUDIT-<area>.md` |
+| `<IN_FLIGHT_AREAS>` | Comma-list from STATE.md |
+
+## When to deviate from this template
+- **Heavy schema work**: add explicit migration-naming guidance and require `prisma migrate diff` review before commit.
+- **Pure UI/CSS area**: drop the routeSecurity MANIFEST bullet, add "use design tokens not hex codes".
+- **Authentication / RBAC area**: add "no role-relation rename without checking every call site; super_admin always included".
+
+## Related templates
+- `BACKLOG-template.md` — initial backlog format
+- `heartbeat.sh` — secondary heartbeat process
+
+## Related rules
+- `rules/integration-branch.md` — why the parent branch is `<INTEGRATION_BRANCH>` and not master
+- `rules/merge-strategy.md` — what happens after sub-agent commits land on the branch

package/rcode/skills/actions/4-implementation/rcode-retrospective/workflow.md

@@ -34,11 +34,30 @@ This keeps `.rcode/state.json` in sync with disk — `/rcode-progress`, `/rcode-
 
 ---
 
+## AUTO MODE (--auto / yolo)
+
+**If `--auto` was passed OR `config.mode == "yolo"`:** skip all `<action>WAIT</action>` gates,
+skip all roleplay dialog (Bob/Alice/Charlie personas), and produce the retrospective document
+directly from available artifacts.
+
+Auto-mode steps:
+1. Load config + resolve paths (same as INITIALIZATION below).
+2. Detect epic number automatically (highest epic in sprint-status or implementation_artifacts).
+3. Read epic file, SUMMARY.md, and previous retrospective if present.
+4. Produce the retrospective markdown document at `{implementation_artifacts}/epic-{N}-retro-{date}.md`
+   with sections: Epic Summary, Metrics, Successes, Challenges, Key Learnings, Action Items,
+   Next Epic Preparation.
+5. Update sprint-status.yaml to mark `epic-{N}-retrospective` as done.
+6. Run `node .rcode/bin/rcode-tools.cjs state sync --from-disk`.
+7. Print completion banner and stop — do not run the interactive EXECUTION steps below.
+
+---
+
 ## INITIALIZATION
 
 ### Configuration Loading
 
-Load config from `{project-root}/.rcode/config.json` and resolve:
+Load config from `{project-root}/.rcode/config.yaml` and resolve:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`
@@ -495,83 +514,26 @@ Bob (Scrum Master): "No problem. We'll still do a thorough retro on Epic {{epic_
 <action>Ensure key roles present: Product Owner, Scrum Master (facilitating), Devs, Testing/QA, Architect</action>
 
 <output>
-Bob (Scrum Master): "Alright team, everyone's here. Let me set the stage for our retrospective."
-
 ═══════════════════════════════════════════════════════════
 🔄 TEAM RETROSPECTIVE - Epic {{epic_number}}: {{epic_title}}
 ═══════════════════════════════════════════════════════════
 
-Bob (Scrum Master): "Here's what we accomplished together."
-
 **EPIC {{epic_number}} SUMMARY:**
 
-Delivery Metrics:
-
-- Completed: {{completed_stories}}/{{total_stories}} stories ({{completion_percentage}}%)
-- Velocity: {{actual_points}} story points{{#if planned_points}} (planned: {{planned_points}}){{/if}}
-- Duration: {{actual_sprints}} sprints{{#if planned_sprints}} (planned: {{planned_sprints}}){{/if}}
-- Average velocity: {{points_per_sprint}} points/sprint
-
-Quality and Technical:
-
-- Blockers encountered: {{blocker_count}}
-- Technical debt items: {{debt_count}}
-- Test coverage: {{coverage_info}}
-- Production incidents: {{incident_count}}
-
-Business Outcomes:
-
-- Goals achieved: {{goals_met}}/{{total_goals}}
-- Success criteria: {{criteria_status}}
-- Stakeholder feedback: {{feedback_summary}}
-
-Alice (Product Owner): "Those numbers tell a good story. {{completion_percentage}}% completion is {{#if completion_percentage >= 90}}excellent{{else}}something we should discuss{{/if}}."
-
-Charlie (Senior Dev): "I'm more interested in that technical debt number - {{debt_count}} items is {{#if debt_count > 10}}concerning{{else}}manageable{{/if}}."
-
-Dana (QA Engineer): "{{incident_count}} production incidents - {{#if incident_count == 0}}clean epic!{{else}}we should talk about those{{/if}}."
+Delivery: {{completed_stories}}/{{total_stories}} stories ({{completion_percentage}}%) · {{actual_points}} pts · {{actual_sprints}} sprints · {{points_per_sprint}} pts/sprint avg
+Quality: {{blocker_count}} blockers · {{debt_count}} tech-debt items · {{coverage_info}} coverage · {{incident_count}} incidents
+Outcomes: {{goals_met}}/{{total_goals}} goals · {{criteria_status}} · {{feedback_summary}}
 
 {{#if next_epic_exists}}
-═══════════════════════════════════════════════════════════
 **NEXT EPIC PREVIEW:** Epic {{next_epic_num}}: {{next_epic_title}}
-═══════════════════════════════════════════════════════════
-
-Dependencies on Epic {{epic_number}}:
-{{list_dependencies}}
-
-Preparation Needed:
-{{list_preparation_gaps}}
-
-Technical Prerequisites:
-{{list_technical_prereqs}}
-
-Bob (Scrum Master): "And here's what's coming next. Epic {{next_epic_num}} builds on what we just finished."
-
-Elena (Junior Dev): "Wow, that's a lot of dependencies on our work."
-
-Charlie (Senior Dev): "Which means we better make sure Epic {{epic_number}} is actually solid before moving on."
+Dependencies: {{list_dependencies}}
+Preparation gaps: {{list_preparation_gaps}}
+Technical prerequisites: {{list_technical_prereqs}}
 {{/if}}
 
-═══════════════════════════════════════════════════════════
-
-Bob (Scrum Master): "Team assembled for this retrospective:"
-
-{{list_participating_agents}}
-
-Bob (Scrum Master): "{user_name}, you're joining us as Project Lead. Your perspective is crucial here."
-
-{user_name} (Project Lead): [Participating in the retrospective]
-
-Bob (Scrum Master): "Our focus today:"
-
-1. Learning from Epic {{epic_number}} execution
-   {{#if next_epic_exists}}2. Preparing for Epic {{next_epic_num}} success{{/if}}
-
-Bob (Scrum Master): "Ground rules: psychological safety first. No blame, no judgment. We focus on systems and processes, not individuals. Everyone's voice matters. Specific examples are better than generalizations."
-
-Alice (Product Owner): "And everything shared here stays in this room - unless we decide together to escalate something."
-
-Bob (Scrum Master): "Exactly. {user_name}, any questions before we dive in?"
+Participants: {{list_participating_agents}} + {user_name} (Project Lead)
+Focus: (1) Learn from Epic {{epic_number}} · {{#if next_epic_exists}}(2) Prepare Epic {{next_epic_num}}{{/if}}
+Ground rules: No blame — systems focus — psychological safety — specific examples preferred.
 </output>
 
 <action>WAIT for {user_name} to respond or indicate readiness</action>
@@ -874,49 +836,19 @@ Bob (Scrum Master): "I want specific, achievable actions with clear owners. Not
 - Time-bound: Has clear deadline
 
 <output>
-Bob (Scrum Master): "Based on our discussion, here are the action items I'm proposing..."
-
 ═══════════════════════════════════════════════════════════
 📝 EPIC {{epic_number}} ACTION ITEMS:
 ═══════════════════════════════════════════════════════════
 
 **Process Improvements:**
-
-1. {{action_item_1}}
-   Owner: {{agent_1}}
-   Deadline: {{timeline_1}}
-   Success criteria: {{criteria_1}}
-
-2. {{action_item_2}}
-   Owner: {{agent_2}}
-   Deadline: {{timeline_2}}
-   Success criteria: {{criteria_2}}
-
-Charlie (Senior Dev): "I can own action item 1, but {{timeline_1}} is tight. Can we push it to {{alternative_timeline}}?"
-
-Bob (Scrum Master): "What do others think? Does that timing still work?"
-
-Alice (Product Owner): "{{alternative_timeline}} works for me, as long as it's done before Epic {{next_epic_num}} starts."
-
-Bob (Scrum Master): "Agreed. Updated to {{alternative_timeline}}."
+1. {{action_item_1}} — Owner: {{agent_1}} · Due: {{timeline_1}} · Success: {{criteria_1}}
+2. {{action_item_2}} — Owner: {{agent_2}} · Due: {{timeline_2}} · Success: {{criteria_2}}
 
 **Technical Debt:**
+1. {{debt_item_1}} — Owner: {{agent_3}} · Priority: {{priority_1}} · Effort: {{effort_1}}
+2. {{debt_item_2}} — Owner: {{agent_4}} · Priority: {{priority_2}} · Effort: {{effort_2}}
 
-1. {{debt_item_1}}
-   Owner: {{agent_3}}
-   Priority: {{priority_1}}
-   Estimated effort: {{effort_1}}
-
-2. {{debt_item_2}}
-   Owner: {{agent_4}}
-   Priority: {{priority_2}}
-   Estimated effort: {{effort_2}}
-
-Dana (QA Engineer): "For debt item 1, can we prioritize that as high? It caused testing issues in three different stories."
-
-Charlie (Senior Dev): "I marked it medium because {{reasoning}}, but I hear your point."
-
-Bob (Scrum Master): "{user_name}, this is a priority call. Testing impact vs. {{reasoning}} - how do you want to prioritize it?"
+{user_name}, debt item 1 priority is a call you need to make — testing impact vs. {{reasoning}}.
 </output>
 
 <action>WAIT for {user_name} to help resolve priority discussions</action>
@@ -998,59 +930,20 @@ Estimated: {{est_4}}
 
 <check if="significant discoveries detected">
   <output>
+🚨 SIGNIFICANT DISCOVERY — Epic {{next_epic_num}} plan needs review
 
-═══════════════════════════════════════════════════════════
-🚨 SIGNIFICANT DISCOVERY ALERT 🚨
-═══════════════════════════════════════════════════════════
-
-Bob (Scrum Master): "{user_name}, we need to flag something important."
-
-Bob (Scrum Master): "During Epic {{epic_number}}, the team uncovered findings that may require updating the plan for Epic {{next_epic_num}}."
-
-**Significant Changes Identified:**
+Changes identified:
+1. {{significant_change_1}} — Impact: {{impact_description_1}}
+2. {{significant_change_2}} — Impact: {{impact_description_2}}
+{{#if significant_change_3}}3. {{significant_change_3}} — Impact: {{impact_description_3}}{{/if}}
 
-1. {{significant_change_1}}
-   Impact: {{impact_description_1}}
-
-2. {{significant_change_2}}
-   Impact: {{impact_description_2}}
-
-{{#if significant_change_3}} 3. {{significant_change_3}}
-Impact: {{impact_description_3}}
-{{/if}}
+Epic {{next_epic_num}} currently assumes: {{wrong_assumption_1}} / {{wrong_assumption_2}}
+Epic {{epic_number}} revealed: {{actual_reality_1}} / {{actual_reality_2}}
+Changes needed: {{list_likely_changes_needed}}
 
-Charlie (Senior Dev): "Yeah, when we discovered {{technical_discovery}}, it fundamentally changed our understanding of {{affected_area}}."
+Recommended: review Epic {{next_epic_num}} definition · update affected stories · hold alignment session{{#if prd_update_needed}} · update PRD{{/if}}
 
-Alice (Product Owner): "And from a product perspective, {{product_discovery}} means Epic {{next_epic_num}}'s stories are based on wrong assumptions."
-
-Dana (QA Engineer): "If we start Epic {{next_epic_num}} as-is, we're going to hit walls fast."
-
-**Impact on Epic {{next_epic_num}}:**
-
-The current plan for Epic {{next_epic_num}} assumes:
-
-- {{wrong_assumption_1}}
-- {{wrong_assumption_2}}
-
-But Epic {{epic_number}} revealed:
-
-- {{actual_reality_1}}
-- {{actual_reality_2}}
-
-This means Epic {{next_epic_num}} likely needs:
-{{list_likely_changes_needed}}
-
-**RECOMMENDED ACTIONS:**
-
-1. Review and update Epic {{next_epic_num}} definition based on new learnings
-2. Update affected stories in Epic {{next_epic_num}} to reflect reality
-3. Consider updating architecture or technical specifications if applicable
-4. Hold alignment session with Product Owner before starting Epic {{next_epic_num}}
-   {{#if prd_update_needed}}5. Update PRD sections affected by new understanding{{/if}}
-
-Bob (Scrum Master): "**Epic Update Required**: YES - Schedule epic planning review session"
-
-Bob (Scrum Master): "{user_name}, this is significant. We need to address this before committing to Epic {{next_epic_num}}'s current plan. How do you want to handle it?"
+{user_name}: how do you want to handle this before committing to Epic {{next_epic_num}}'s current plan?
 </output>
 
 <action>WAIT for {user_name} to decide on how to handle the significant changes</action>
@@ -1274,61 +1167,27 @@ Charlie (Senior Dev): "Better to catch this now than three stories into the next
 <step n="10" goal="Retrospective Closure with Celebration and Commitment">
 
 <output>
-Bob (Scrum Master): "We've covered a lot of ground today. Let me bring this retrospective to a close."
-
 ═══════════════════════════════════════════════════════════
-✅ RETROSPECTIVE COMPLETE
+✅ RETROSPECTIVE COMPLETE — Epic {{epic_number}}: {{epic_title}}
 ═══════════════════════════════════════════════════════════
 
-Bob (Scrum Master): "Epic {{epic_number}}: {{epic_title}} - REVIEWED"
-
 **Key Takeaways:**
-
 1. {{key_lesson_1}}
 2. {{key_lesson_2}}
 3. {{key_lesson_3}}
-   {{#if key_lesson_4}}4. {{key_lesson_4}}{{/if}}
-
-Alice (Product Owner): "That first takeaway is huge - {{impact_of_lesson_1}}."
-
-Charlie (Senior Dev): "And lesson 2 is something we can apply immediately."
-
-Bob (Scrum Master): "Commitments made today:"
-
-- Action Items: {{action_count}}
-- Preparation Tasks: {{prep_task_count}}
-- Critical Path Items: {{critical_count}}
-
-Dana (QA Engineer): "That's a lot of commitments. We need to actually follow through this time."
+{{#if key_lesson_4}}4. {{key_lesson_4}}{{/if}}
 
-Bob (Scrum Master): "Agreed. Which is why we'll review these action items in our next standup."
+Commitments: {{action_count}} action items · {{prep_task_count}} prep tasks · {{critical_count}} critical path items
 
-═══════════════════════════════════════════════════════════
-🎯 NEXT STEPS:
-═══════════════════════════════════════════════════════════
-
-1. Execute Preparation Sprint (Est: {{prep_days}} days)
-2. Complete Critical Path items before Epic {{next_epic_num}}
+**Next Steps:**
+1. Execute Preparation Sprint ({{prep_days}} days)
+2. Complete critical path items before Epic {{next_epic_num}}
 3. Review action items in next standup
-   {{#if epic_update_needed}}4. Hold Epic {{next_epic_num}} planning review session{{else}}4. Begin Epic {{next_epic_num}} planning when preparation complete{{/if}}
-
-Elena (Junior Dev): "{{prep_days}} days of prep work is significant, but necessary."
+{{#if epic_update_needed}}4. Hold Epic {{next_epic_num}} planning review{{else}}4. Begin Epic {{next_epic_num}} planning when prep complete{{/if}}
 
-Alice (Product Owner): "I'll communicate the timeline to stakeholders. They'll understand if we frame it as 'ensuring Epic {{next_epic_num}} success.'"
+Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_description}} velocity across {{blocker_count}} blockers.
 
-═══════════════════════════════════════════════════════════
-
-Bob (Scrum Master): "Before we wrap, I want to take a moment to acknowledge the team."
-
-Bob (Scrum Master): "Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_description}} velocity. We overcame {{blocker_count}} blockers. We learned a lot. That's real work by real people."
-
-Charlie (Senior Dev): "Hear, hear."
-
-Alice (Product Owner): "I'm proud of what we shipped."
-
-Dana (QA Engineer): "And I'm excited about Epic {{next_epic_num}} - especially now that we're prepared for it."
-
-Bob (Scrum Master): "{user_name}, any final thoughts before we close?"
+{user_name}, any final thoughts before we close?
 </output>
 
 <action>WAIT for {user_name} to share final reflections</action>
@@ -1409,61 +1268,17 @@ Retrospective document was saved successfully, but {sprint_status_file} may need
 <output>
 **✅ Retrospective Complete, {user_name}!**
 
-**Epic Review:**
-
-- Epic {{epic_number}}: {{epic_title}} reviewed
-- Retrospective Status: completed
-- Retrospective saved: {implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md
-
-**Commitments Made:**
-
-- Action Items: {{action_count}}
-- Preparation Tasks: {{prep_task_count}}
-- Critical Path Items: {{critical_count}}
+Epic {{epic_number}}: {{epic_title}} — retrospective saved: `{implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md`
+Commitments: {{action_count}} action items · {{prep_task_count}} prep tasks · {{critical_count}} critical path items
 
 **Next Steps:**
+1. Review `{implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md`
+2. Execute preparation sprint (~{{prep_days}} days) — {{critical_count}} critical items + {{prep_task_count}} prep tasks
+3. Review action items in next standup
+{{#if epic_update_needed}}4. ⚠️ SCHEDULE Epic {{next_epic_num}} planning review — do NOT start until complete{{else}}4. Begin Epic {{next_epic_num}} when prep complete{{/if}}
 
-1. **Review retrospective summary**: {implementation_artifacts}/epic-{{epic_number}}-retro-{date}.md
-
-2. **Execute preparation sprint** (Est: {{prep_days}} days)
-   - Complete {{critical_count}} critical path items
-   - Execute {{prep_task_count}} preparation tasks
-   - Verify all action items are in progress
-
-3. **Review action items in next standup**
-   - Ensure ownership is clear
-   - Track progress on commitments
-   - Adjust timelines if needed
-
-{{#if epic_update_needed}} 4. **IMPORTANT: Schedule Epic {{next_epic_num}} planning review session**
-
-- Significant discoveries from Epic {{epic_number}} require epic updates
-- Review and update affected stories
-- Align team on revised approach
-- Do NOT start Epic {{next_epic_num}} until review is complete
-  {{else}}
-
-4. **Begin Epic {{next_epic_num}} when ready**
-   - Start creating stories with SM agent's `create-story`
-   - Epic will be marked as `in-progress` automatically when first story is created
-   - Ensure all critical path items are done first
-     {{/if}}
-
-**Team Performance:**
-Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_summary}}. The retrospective surfaced {{insight_count}} key insights and {{significant_discovery_count}} significant discoveries. The team is well-positioned for Epic {{next_epic_num}} success.
-
-{{#if significant_discovery_count > 0}}
-⚠️ **REMINDER**: Epic update required before starting Epic {{next_epic_num}}
-{{/if}}
-
----
-
-Bob (Scrum Master): "Great session today, {user_name}. The team did excellent work."
-
-Alice (Product Owner): "See you at epic planning!"
-
-Charlie (Senior Dev): "Time to knock out that prep work."
-
+Epic {{epic_number}}: {{completed_stories}} stories · {{velocity_summary}} · {{insight_count}} insights · {{significant_discovery_count}} discoveries
+{{#if significant_discovery_count > 0}}⚠️ Epic update required before starting Epic {{next_epic_num}}{{/if}}
 </output>
 
 </step>

package/rcode/templates/sprint.md

@@ -35,6 +35,22 @@
 | Risk | Impact | Mitigation |
 |------|--------|------------|
 
+## Files Touched
+
+<!-- Planner must populate before handoff to executor. Used by wave-overlap checker and merge reviewers. -->
+
+**Creates:**
+<!-- - `exact/path/new-file.ts` — one-line responsibility -->
+
+**Modifies:**
+<!-- - `exact/path/existing.ts` — what changes -->
+
+**Tests:**
+<!-- - `tests/exact/path/test.ts` — tests for -->
+
+**Aggregator files (append-only — never replace):**
+<!-- - `packages/shared/src/index.ts` — adds export for X -->
+
 ## Sprint Review
 
 <!-- Fill at sprint completion only — omit this section until then -->

package/rcode/workflows/audit.md

@@ -18,6 +18,7 @@ If `$ARGUMENTS` contains `--help` or `-h`:
 
 ```
 /rcode-audit                           # interactive — asks what to audit
+/rcode-audit --auto                    # non-interactive — auto-picks best target from project state
 /rcode-audit plans [--report]         # → audit-plans (structural + status + deps check)
 /rcode-audit phase [<NN>]              # → /rcode-verify-phase
 /rcode-audit milestone [--strict]      # → /rcode-audit-milestone (with synth fallback)
@@ -49,6 +50,8 @@ DISCUSS=$($TOOL config-get workflow.discuss_mode 2>/dev/null || echo "adaptive")
 ```
 
 Parse `$ARGUMENTS`:
+- If `--auto` flag is present: strip it from args and force `MODE=yolo` for this invocation
+  (allows non-interactive runs without permanently changing the project config).
 - First word ∈ {plans, phase, milestone, uat, code, fix, work, lens, worktrees} → set `$TARGET`, drop it from args, jump to Step 4.
 - Empty or unrecognised → continue to Step 2.
 

package/rcode/workflows/brainstorm.md

@@ -40,7 +40,7 @@ AskUserQuestion(
 
 ## Step 2 — Load brainstorming methods
 
-Read `rcode/references/brain-methods.csv` and parse it.
+Read `.rcode/references/brain-methods.csv` and parse it.
 
 If `--method` was specified:
 - Validate the method exists in the CSV

package/rcode/workflows/council.md

@@ -29,9 +29,10 @@ Closure: `rcode ► COUNCIL COMPLETE ✓` + Next Up with decision options.
 
 <required_reading>
 @.rcode/references/auto-init-guard.md
-@.rcode/references/output-format.md
 @.rcode/references/council-protocol.md
 </required_reading>
+<!-- output-format.md removed: council is self-contained via <output_format> above.
+     General banner/todo/spawn patterns are defined inline — no 398-line load needed. -->
 
 <process>
 ## Step 0 — Usage check
@@ -101,6 +102,12 @@ list from INIT_JSON so new agents added to team.yaml are automatically available
 Do not invoke `general-purpose` or any agent type not present in
 `installed_agents`. If the scorer surfaces an unknown agent, drop it
 from the panel silently.
+
+**Post-install agent namespace fallback:** If a `Task(subagent_type="rcode-{id}")` call
+fails with "Agent type not found", the runtime has not yet registered the new agent files
+(requires IDE/window reload). In that case retry with `subagent_type="rihal-{id}"` — the
+`rihal-*` agents are content-identical to `rcode-*` (pre-rebrand names). If neither works,
+skip that panelist and log `[council] agent rcode-{id} not available — reload IDE to register`.
 </available_agent_types>
 
 ## Step 1 — Observe

package/rcode/workflows/create-architecture.md

@@ -9,7 +9,11 @@ Write an Architecture Decision Record (ADR) or system design document. Delegates
 Locate and follow the installed skill:
 
 ```bash
-find .rcode/skills/actions -path "*rcode-create-architecture/workflow.md" 2>/dev/null | head -1
+if [ -f .rcode/skills/rcode-create-architecture/workflow.md ]; then
+  printf '%s\n' ".rcode/skills/rcode-create-architecture/workflow.md"
+else
+  find .rcode/skills/actions -path "*rcode-create-architecture/workflow.md" 2>/dev/null | head -1
+fi
 ```
 
 Read and follow the workflow at that path. If the path is empty:

package/rcode/workflows/create-prd.md

@@ -9,7 +9,11 @@ Create a Product Requirements Document from scratch through guided facilitation.
 Locate and follow the installed skill:
 
 ```bash
-find .rcode/skills/actions -path "*rcode-create-prd/workflow.md" 2>/dev/null | head -1
+if [ -f .rcode/skills/rcode-create-prd/workflow.md ]; then
+  printf '%s\n' ".rcode/skills/rcode-create-prd/workflow.md"
+else
+  find .rcode/skills/actions -path "*rcode-create-prd/workflow.md" 2>/dev/null | head -1
+fi
 ```
 
 Read and follow the workflow at that path. If the path is empty:

package/rcode/workflows/dashboard.md

@@ -33,8 +33,11 @@ if [ -f ./server/dashboard.js ]; then
 # 2. Installed package copy inside project
 elif [ -f ./.rcode/lib/server/dashboard.js ]; then
   DASHBOARD="./.rcode/lib/server/dashboard.js"
+# 3. Local npm dependency install
+elif [ -f ./node_modules/@hanzlaa/rcode/server/dashboard.js ]; then
+  DASHBOARD="./node_modules/@hanzlaa/rcode/server/dashboard.js"
 else
-  # 3. Global installs — check npm, pnpm, and yarn roots
+  # 4. Global installs — check npm, pnpm, and yarn roots
   for ROOT in "$(npm root -g 2>/dev/null)" "$(pnpm root -g 2>/dev/null)" "$(yarn global dir 2>/dev/null)/node_modules"; do
     [ -z "$ROOT" ] && continue
     if [ -f "$ROOT/@hanzlaa/rcode/server/dashboard.js" ]; then
@@ -42,7 +45,7 @@ else
       break
     fi
   done
-  # 4. Last resort — resolve via the rcode/rcode binary symlink
+  # 5. Last resort — resolve via the rcode/rcode binary symlink
   if [ -z "$DASHBOARD" ]; then
     for BIN in rcode; do
       BIN_PATH="$(command -v $BIN 2>/dev/null)" || continue

package/rcode/workflows/discuss-phase.md

@@ -39,21 +39,9 @@ Only include domain-probes.md when `HAS_PRODUCT_SIGNALS` is 0.
 </downstream_awareness>
 
 <philosophy>
-**User = founder/visionary. Claude = builder.**
-
-The user knows:
-- How they imagine it working
-- What it should look/feel like
-- What's essential vs nice-to-have
-- Specific behaviors or references they have in mind
-
-The user doesn't know (and shouldn't be asked):
-- Codebase patterns (researcher reads the code)
-- Technical risks (researcher identifies these)
-- Implementation approach (planner figures this out)
-- Success metrics (inferred from the work)
-
-Ask about vision and implementation choices. Capture decisions for downstream agents.
+User = visionary (knows what, not how). Claude = builder (asks about choices, not implementation).
+Ask about vision and decisions. Capture for downstream agents. Never ask about codebase patterns,
+technical risks, or architecture — those are research/planner territory.
 </philosophy>
 
 <scope_guardrail>

package/rcode/workflows/execute-sprint.md

@@ -4,7 +4,7 @@ Execute a phase prompt (SPRINT.md) and create the outcome summary (SUMMARY.md).
 
 <required_reading>
 Read STATE.md before any operation to load project context.
-Read config.json for planning behavior settings.
+Read config.yaml for planning behavior settings.
 
 @.rcode/references/git-integration.md
 @.rcode/references/karpathy-guidelines.md
@@ -104,6 +104,8 @@ grep -n "type=\"checkpoint" .planning/phases/XX-name/{phase}-{plan}-SPRINT.md
 
 **Pattern A:** init_agent_tracking → capture `EXPECTED_BASE=$(git rev-parse HEAD)` → spawn Task(subagent_type="rcode-executor", model=executor_model) with prompt: execute plan at [path], autonomous, all tasks + SUMMARY + commit, follow deviation/auth rules, report: plan name, tasks, SUMMARY path, commit hash → track agent_id → wait → update tracking → report. **Include `isolation="worktree"` only if `workflow.use_worktrees` is not `false`** (read via `config-get workflow.use_worktrees`). **When using `isolation="worktree"`, include a `<worktree_branch_check>` block in the prompt** instructing the executor to run `git merge-base HEAD {EXPECTED_BASE}` and, if the result differs from `{EXPECTED_BASE}`, reset the branch base with `git reset --soft {EXPECTED_BASE}` before starting work. This corrects a known issue on Windows where `EnterWorktree` creates branches from `main` instead of the feature branch HEAD.
 
+**Post-install namespace fallback:** If `Task(subagent_type="rcode-executor")` fails with "Agent type not found", the runtime has not yet registered the agent (requires IDE reload after install). Retry with `subagent_type="rihal-executor"`. If that also fails, fall back to Pattern C (execute in main context) and log `[execute-sprint] rcode-executor not available — reload IDE or executing in main context`.
+
 **Pattern B:** Execute segment-by-segment. Autonomous segments: spawn subagent for assigned tasks only (no SUMMARY/commit). Checkpoints: main context. After all segments: aggregate, create SUMMARY, commit. See segment_execution.
 
 **Pattern C:** Execute in main using standard flow (step name="execute").