@hanzlaa/rcode 4.1.0 → 4.1.1

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").

package/rcode/workflows/retrospective.md

@@ -9,7 +9,11 @@ Run an epic retrospective and produce owned action items. Delegates to the rcode
 Locate and follow the installed skill:
 
 ```bash
-find .rcode/skills/actions -path "*rcode-retrospective/workflow.md" 2>/dev/null | head -1
+if [ -f .rcode/skills/rcode-retrospective/workflow.md ]; then
+  printf '%s\n' ".rcode/skills/rcode-retrospective/workflow.md"
+else
+  find .rcode/skills/actions -path "*rcode-retrospective/workflow.md" 2>/dev/null | head -1
+fi
 ```
 
 Read and follow the workflow at that path. If the path is empty:

package/rcode/workflows/sprint-planning.md

@@ -14,8 +14,9 @@ back to the in-line implementation.
 
 <delegate_to_skill>
 Required skill: `rcode-sprint-planning`
-Path:           `.claude/skills/rcode-sprint-planning/SKILL.md`
-Workflow ref:   `.claude/skills/rcode-sprint-planning/workflow.md`
+Path:           `.rcode/skills/rcode-sprint-planning/SKILL.md`
+Workflow ref:   `.rcode/skills/rcode-sprint-planning/workflow.md`
+Fallback path:  `.claude/skills/rcode-sprint-planning/SKILL.md`
 
 Behaviour:
 1. Load the skill's `SKILL.md` and `workflow.md`. Apply every Critical
@@ -99,8 +100,9 @@ Exit.
 - Commit max 80% of average (buffer for interrupts + unknowns)
 
 **If no velocity history (first sprint):**
-- Ask user: "This is your first sprint. How many story points can you commit to? (Typical: 8-13 for solo dev + AI)"
-- Or use `--velocity` flag
+- If `--velocity <N>` flag was supplied, use that value directly and skip the prompt.
+- If `mode == "yolo"` (config) and no `--velocity` flag, default to 10 points and proceed.
+- Otherwise ask user: "This is your first sprint. How many story points can you commit to? (Typical: 8-13 for solo dev + AI)"
 
 Store as `velocity_target`.
 
@@ -127,7 +129,9 @@ Present story table to user:
 **Capacity check:** Total committed points <= velocity_target.
 If over: "We're at {N} points vs {target} capacity. Move story #{X} to next sprint?"
 
-Wait for user confirmation before proceeding.
+**Automation escape:** if `mode == "yolo"` or `--auto` flag was passed, skip the
+confirmation; automatically move lowest-priority over-capacity stories to backlog
+and proceed. Otherwise wait for user confirmation before proceeding.
 
 ## Step 4 — Create sprint