@hanzlaa/rcode 4.7.3 → 4.9.0

package/rcode/references/execute-close-parent-artifacts.md

@@ -0,0 +1,49 @@
+# execute.md — close_parent_artifacts (decimal/polish phases only)
+
+Extracted from `execute.md`'s `close_parent_artifacts` step. Only loaded when `PHASE_NUMBER` contains a decimal (gap-closure phases like `4.1`, `03.1`) — see the conditional include at that point in `execute.md`.
+
+For decimal/polish phases only (X.Y pattern): close the feedback loop by resolving parent UAT and debug artifacts.
+
+**1. Detect decimal phase and derive parent:**
+```bash
+# Check if phase_number contains a decimal
+if [[ "$PHASE_NUMBER" == *.* ]]; then
+  PARENT_PHASE="${PHASE_NUMBER%%.*}"
+fi
+```
+
+**2. Find parent UAT file:**
+```bash
+PARENT_INFO=$(node ".rcode/bin/rcode-tools.cjs" find-phase "${PARENT_PHASE}" --raw)
+# Extract directory from PARENT_INFO JSON, then find UAT file in that directory
+```
+
+**If no parent UAT found:** Skip this step (gap-closure may have been triggered by VERIFICATION.md instead).
+
+**3. Update UAT gap statuses:**
+
+Read the parent UAT file's `## Gaps` section. For each gap entry with `status: failed`:
+- Update to `status: resolved`
+
+**4. Update UAT frontmatter:**
+
+If all gaps now have `status: resolved`:
+- Update frontmatter `status: diagnosed` → `status: resolved`
+- Update frontmatter `updated:` timestamp
+
+**5. Resolve referenced debug sessions:**
+
+For each gap that has a `debug_session:` field:
+- Read the debug session file
+- Update frontmatter `status:` → `resolved`
+- Update frontmatter `updated:` timestamp
+- Move to resolved directory:
+```bash
+mkdir -p .planning/debug/resolved
+mv .planning/debug/{slug}.md .planning/debug/resolved/
+```
+
+**6. Commit updated artifacts:**
+```bash
+node ".rcode/bin/rcode-tools.cjs" commit "docs(phase-${PARENT_PHASE}): resolve UAT gaps and debug sessions after ${PHASE_NUMBER} gap closure" --files .planning/phases/*${PARENT_PHASE}*/*-UAT.md .planning/debug/resolved/*.md
+```

package/rcode/references/execute-interactive-mode.md

@@ -0,0 +1,44 @@
+# execute.md — Interactive Execution Mode
+
+Extracted from `execute.md`'s `check_interactive_mode` step. Only loaded when the `--interactive` flag is present — see the conditional include at that point in `execute.md`.
+
+Interactive mode executes plans sequentially **inline** (no subagent spawning) with user
+checkpoints between tasks. The user can review, modify, or redirect work at any point.
+
+**Interactive execution flow:**
+
+1. Load plan inventory as normal (discover_and_group_plans)
+2. For each plan (sequentially, ignoring wave grouping):
+
+   a. **Present the plan to the user:**
+      ```
+      ## Plan {plan_id}: {plan_name}
+
+      Objective: {from plan file}
+      Tasks: {task_count}
+
+      Options:
+      - Execute (proceed with all tasks)
+      - Review first (show task breakdown before starting)
+      - Skip (move to next plan)
+      - Stop (end execution, save progress)
+      ```
+
+   b. **If "Review first":** Read and display the full plan file. Ask again: Execute, Modify, Skip.
+
+   c. **If "Execute":** Read and follow `.rcode/workflows/execute-sprint.md` **inline**
+      (do NOT spawn a subagent). Execute tasks one at a time.
+
+   d. **After each task:** Pause briefly. If the user intervenes (types anything), stop and address
+      their feedback before continuing. Otherwise proceed to next task.
+
+   e. **After plan complete:** Show results, commit, create SUMMARY.md, then present next plan.
+      **Overwrite guard:** If the SUMMARY.md file already exists from a previous run, delete it first with `rm -f <path>` before writing the new version. Never append to or skip an existing SUMMARY.md — always overwrite with the current sprint's completion data.
+
+3. After all plans: proceed to verification (same as normal mode).
+
+**Benefits of interactive mode:**
+- No subagent overhead — dramatically lower token usage
+- User catches mistakes early — saves costly verification cycles
+- Maintains rcode's planning/tracking structure
+- Best for: small phases, bug fixes, verification gaps, learning rcode

package/rcode/references/execute-notify-webhooks.md

@@ -0,0 +1,22 @@
+# execute.md — notify_on_completion (webhook notifications)
+
+Extracted from `execute.md`'s `notify_on_completion` step. Only loaded when a webhook URL is configured — see the conditional include at that point in `execute.md`.
+
+**Post phase completion to configured webhooks (Slack / Discord / MS Teams).**
+
+```bash
+node ".rcode/bin/rcode-tools.cjs" notify send \
+  --title "Phase ${phase_number} complete — ${phase_name}" \
+  --body "$(basename "$PWD") · $(git rev-parse --short HEAD) · ${incomplete_count:-0} plan(s) remaining" \
+  --event "execute-done" 2>/dev/null || true
+```
+
+Users configure webhooks by editing `.rcode/config.yaml`:
+
+```yaml
+slack_webhook_url: "https://hooks.slack.com/services/..."
+discord_webhook_url: "https://discord.com/api/webhooks/..."
+teams_webhook_url: "https://outlook.office.com/webhook/..."
+```
+
+Then verify with `/rcode-notify-test`.

package/rcode/references/execution-protocol.md

@@ -10,13 +10,13 @@ Every plan file must have this frontmatter and structure:
 
 ```markdown
 ---
-id: "01.02"                 # full hierarchical ID
-phase: "01"                 # phase ID (2-digit, zero-padded)
-plan: "02"                  # plan ID within phase (2-digit, zero-padded)
-milestone: "M1"             # optional, if assigned to milestone
-type: auto | tdd
-depends_on: []              # list of other plan IDs like ["01.01"]
-wave: 1                     # auto-derived from depends_on
+phase: "8"                  # phase ID (no leading zeros — issue #652)
+plan_number: 1               # plan ID within phase (no leading zeros — issue #652)
+wave: 1                      # auto-derived from depends_on
+depends_on: []                # list of other plan IDs like ["8-1"]
+files_modified: []            # files this plan touches
+autonomous: true               # whether the plan runs without checkpoints
+requirements: []               # requirement IDs mapped to this plan, if any
 ---
 
 ## Objective
@@ -41,10 +41,10 @@ type: checkpoint:human-verify
 
 **Hierarchical ID format:**
 - Milestone: `M{N}` (e.g., M1, M2)
-- Phase: `{NN}` 2-digit, zero-padded (e.g., 01, 02, 72)
-- Decimal phase (inserted): `{NN.M}` (e.g., 02.1, 72.3)
-- Plan within phase: `{NN.MM}` (e.g., 01.02)
-- Task within plan: `{NN.MM.TT}` (e.g., 01.02.03)
+- Phase: `{N}` — no leading zeros (issue #652), e.g. 1, 2, 72
+- Decimal phase (inserted): `{N.M}` (e.g., 2.1, 72.3)
+- Plan within phase: `{N.M}` (e.g., 1.2)
+- Task within plan: `{N.M.T}` (e.g., 1.2.3)
 
 **Task types:**
 - `auto` — executor runs without pausing

package/rcode/references/git-preflight.md

@@ -14,13 +14,16 @@ Run these read-only commands in order. Any failure halts the workflow with the f
 # Check 1: working tree clean
 DIRTY=$(git status --porcelain 2>/dev/null)
 
-# Check 2: not on a protected branch
+# Check 2: not on a protected branch (skipped entirely when `git.branching_strategy`
+# config is `none` — committing directly to main/master is the deliberately configured
+# workflow in that case)
 BRANCH=$(git branch --show-current 2>/dev/null)
+BRANCHING_STRATEGY=$(node .rcode/bin/rcode-tools.cjs config-get git.branching_strategy 2>/dev/null)
 PROTECTED="main master develop v2-prototype"
 
 # Check 3: branch follows naming convention
-# Allowed: feat/foo-bar, fix/123-baz, issue-123-name, task-123-slug
-BRANCH_OK=$(echo "$BRANCH" | grep -qE '^((feat|fix|docs|chore|refactor|test|perf|style|build|ci)/[a-z0-9][a-z0-9-]*|(issue|task)-[0-9]+-[a-z0-9-]+)$' && echo yes || echo no)
+# Allowed: feat/foo-bar, fix/123-baz, issue-123-name, task-123-slug, 8-1-aria (phase-plan-slug)
+BRANCH_OK=$(echo "$BRANCH" | grep -qE '^((feat|fix|docs|chore|refactor|test|perf|style|build|ci)/[a-z0-9][a-z0-9-]*|(issue|task)-[0-9]+-[a-z0-9-]+|[0-9]+-[0-9]+-[a-z0-9-]+)$' && echo yes || echo no)
 
 # Check 4: scope drift — files touched that don't belong to the active task
 # The workflow MUST pass $TASK_SCOPE_GLOB (e.g. ".planning/phases/8-*/" or "src/auth/")
@@ -35,7 +38,7 @@ fi
 The workflow MUST stop and print the banner below if ANY of:
 
 - `DIRTY` is non-empty AND user did not pass `--allow-dirty`
-- `BRANCH` is in `$PROTECTED` AND user did not pass `--on-main`
+- `BRANCH` is in `$PROTECTED` AND `BRANCHING_STRATEGY` is not `none` AND user did not pass `--on-main`
 - `BRANCH_OK` is `no` AND user did not pass `--allow-dirty` (branch-name lint is advisory if working tree is dirty AND user accepted the dirty override)
 - `OUT_OF_SCOPE` is non-empty AND user did not pass `--allow-scope-drift`
 

package/rcode/references/output-format.md

@@ -42,7 +42,7 @@ Use for major workflow transitions.
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- RCODE ► {STAGE NAME}
+ rcode ► {STAGE NAME}
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -69,7 +69,7 @@ Use this when a router command dispatches to another command:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- RCODE ► ROUTING
+ rcode ► ROUTING
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Input: {user's question or intent}
@@ -328,7 +328,7 @@ Use standard markdown pipe tables with status symbols:
 **Majlis banner** (multi-agent council):
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- RCODE ► MAJLIS CONVENING
+ rcode ► MAJLIS CONVENING
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -354,7 +354,7 @@ the banner, not inside it.
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- RCODE ► PLANNING SPRINT 01.1
+ rcode ► PLANNING SPRINT 01.1
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 التخطيط للسباق 01.1 — يرجى الانتظار
 ```
@@ -389,7 +389,7 @@ translated prose goes outside the art, on its own line(s).
 
 - Varying box/banner widths within same output
 - Mixing banner styles (`===`, `---`, `***`)
-- Skipping `RCODE ►` prefix in stage banners
+- Skipping `rcode ►` prefix in stage banners
 - Random emoji (`🚀`, `✨`, `💫`) outside the approved set
 - Missing Next Up block after workflow completions
 - Hardcoding references to other methodologies in rcode's UX

package/rcode/references/plan-gaps-mode.md

@@ -0,0 +1,89 @@
+# plan.md — `--gaps` Mode (Handle `--gaps` Mode)
+
+Extracted from `plan.md` step 3.6. Only loaded when `GAPS_MODE=true` — see the conditional include at that point in `plan.md`.
+
+**Skip unless:** `GAPS_MODE=true`.
+
+**Purpose:** Read `NNN-VERIFICATION.md`, extract failing/partial gaps, count existing plan files, and prepare a `gap_list` payload to feed the planner. On completion, control flow continues at step 8 (skipping CONTEXT.md gating, research, and validation-strategy creation).
+
+**Step 1: Locate VERIFICATION.md**
+
+```bash
+PHASE_DIR=$(node ".rcode/bin/rcode-tools.cjs" roadmap get-phase "${PHASE}" --pick dir 2>/dev/null || echo "")
+# Fallback if --pick dir not supported. TODO(#118): expose roadmap --pick dir cleanly.
+if [[ -z "$PHASE_DIR" ]]; then
+  PHASE_DIR=$(ls -d .planning/phases/${padded_phase}-* 2>/dev/null | head -1)
+fi
+
+VERIFICATION_FILE=$(ls "${PHASE_DIR}"/*-VERIFICATION.md 2>/dev/null | head -1)
+```
+
+**If `VERIFICATION_FILE` is empty:**
+```
+Error: No VERIFICATION.md found for Phase {X}. Gap-closure planning requires the phase to have run through the verifier first.
+
+Try:
+  /rcode-execute {X} ${RCODE_WS}      # run or re-run execution + verification
+```
+Exit workflow.
+
+**Step 2: Extract gaps from VERIFICATION.md**
+
+Parse the file for gap entries with `status: gap_found` or `status: partial`. Inspect these sections:
+- `## Automated Gap` (or `## Automated Gaps`)
+- `## Human Verification Required`
+- Any findings block that includes a `status:` field set to `gap_found` or `partial`
+
+Collect into `GAP_LIST` (an ordered list where each entry has: id, title, expected, actual, status, source_section, severity if present).
+
+If `GAP_LIST` is empty, display:
+```
+Phase {X} VERIFICATION.md contains no gap_found or partial items — nothing to close.
+Report: {VERIFICATION_FILE}
+```
+Exit workflow.
+
+**Step 3: Determine next plan number**
+
+```bash
+EXISTING_PLAN_COUNT=$(ls "${PHASE_DIR}"/*-SPRINT.md 2>/dev/null | wc -l | tr -d ' ')
+# Issue #652 — no leading zeros in planning artifacts. Phase 8 not 08, plan 2 not 02.
+NEXT_PLAN_NUMBER=$((EXISTING_PLAN_COUNT + 1))
+PADDED_PHASE="${PHASE}"
+GAP_PLAN_FILENAME="${PADDED_PHASE}-${NEXT_PLAN_NUMBER}-SPRINT.md"
+GAP_PLAN_PATH="${PHASE_DIR}/${GAP_PLAN_FILENAME}"
+```
+
+If `EXISTING_PLAN_COUNT == 0`, there is no prior execution to reference. Display a warning but proceed — the planner can still close verification gaps.
+
+**Step 4: Gather prior plans for planner context**
+
+```bash
+EXISTING_PLAN_FILES=$(ls "${PHASE_DIR}"/*-SPRINT.md 2>/dev/null | tr '\n' ' ')
+EXISTING_SUMMARY_FILES=$(ls "${PHASE_DIR}"/*-SUMMARY.md 2>/dev/null | tr '\n' ' ')
+```
+
+**Step 5: Display banner**
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ rcode ► GAP-CLOSURE PLANNING — Phase {X}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Verification report: {VERIFICATION_FILE}
+Gaps to close:       {count(GAP_LIST)}
+Existing plans:      {EXISTING_PLAN_COUNT}
+New plan file:       {GAP_PLAN_FILENAME}
+```
+
+**Step 6: Skip ahead**
+
+Control flow jumps directly to step 8 (Spawn rcode-planner). Steps 4 (CONTEXT.md), 5 (Research), and 5.5 (Validation) are ALL skipped when `GAPS_MODE=true`.
+
+Step 8 will consume these variables when filling the planner prompt:
+- `GAP_LIST` — serialized list of gaps (id, title, expected, actual, status)
+- `GAP_PLAN_PATH` — exact output path the planner must write
+- `EXISTING_PLAN_FILES` / `EXISTING_SUMMARY_FILES` — prior phase context
+- `VERIFICATION_FILE` — authoritative source-of-truth
+
+After the planner returns, the existing plan-checker / revision loop (step 10 onward) runs unchanged — gap plans are verified just like normal plans.

package/rcode/references/plan-thinking-partner.md

@@ -0,0 +1,20 @@
+# plan.md — Thinking Partner for Architectural Tradeoffs
+
+Extracted from `plan.md` step 11. Only loaded when `features.thinking_partner` is enabled — see the conditional include at that point in `plan.md`.
+
+If `features.thinking_partner` is enabled, scan the checker's issues for architectural tradeoff keywords
+("architecture", "approach", "strategy", "pattern", "vs", "alternative"). If found:
+
+```
+The sprint-checker flagged an architectural decision point:
+{issue description}
+
+Brief analysis:
+- Option A: {approach_from_plan} — {pros/cons}
+- Option B: {alternative_approach} — {pros/cons}
+- Recommendation: {choice} aligned with {phase_goal}
+
+Apply this to the revision? [Yes] / [No, I'll decide]
+```
+
+If yes: include the recommendation in the revision prompt. If no: proceed to revision loop as normal.

package/rcode/references/plan-windows-troubleshooting.md

@@ -0,0 +1,25 @@
+# plan.md — Windows Troubleshooting
+
+Extracted from `plan.md`'s `<windows_troubleshooting>` block. Only loaded on Windows — see the conditional include at that point in `plan.md`.
+
+**Windows users:** If sprint-plan freezes during agent spawning (common on Windows due to
+stdio deadlocks with MCP servers — see Claude Code issue anthropics/claude-code#28126):
+
+1. **Force-kill:** Close the terminal (Ctrl+C may not work)
+2. **Clean up orphaned processes:**
+   ```powershell
+   # Kill orphaned node processes from stale MCP servers
+   Get-Process node -ErrorAction SilentlyContinue | Where-Object {$_.StartTime -lt (Get-Date).AddHours(-1)} | Stop-Process -Force
+   ```
+3. **Clean up stale task directories:**
+   ```powershell
+   # Remove stale subagent task dirs (Claude Code never cleans these on crash)
+   Remove-Item -Recurse -Force "$env:USERPROFILE\.claude\tasks\*" -ErrorAction SilentlyContinue
+   ```
+4. **Reduce MCP server count:** Temporarily disable non-essential MCP servers in settings.json
+5. **Retry:** Restart Claude Code and run `/rcode-plan` again
+
+If freezes persist, try `--skip-research` to reduce the agent chain from 3 to 2 agents:
+```
+/rcode-plan N --skip-research
+```

package/rcode/references/planner-playbook.md

@@ -160,42 +160,36 @@ Sprint-checker enforces this — see `rcode-sprint-checker.md` Mandatory Output
 
 ```markdown
 ---
-[frontmatter with phase, plan, type, wave, depends_on, files_modified, autonomous, requirements, must_haves]
+phase: {phase}
+plan_number: {N}
+wave: {N}
+depends_on: []
+autonomous: true|false
+files_modified: [...]
+requirements: [...]
+must_haves: {truths, artifacts, key_links}
 ---
 
-<objective>
-[What this plan accomplishes]
-Purpose: [Why this matters]
-Output: [Artifacts created]
-</objective>
-
+<objective>...</objective>
 <execution_context>
-@.rcode/workflows/execute.md
+@.rcode/workflows/execute-sprint.md
 @.rcode/templates/summary.md
 </execution_context>
-
-<context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
-@.planning/STATE.md
-[Only prior SUMMARY refs if genuinely needed]
-</context>
-
+<context>...</context>
 <tasks>
-[2-3 tasks max, each 15-60 min]
+<task id="{phase}.{plan}.{N}" type="auto">
+<title>...</title>
+<read_first>...</read_first>
+<files>...</files>
+<action>...</action>
+<verify><automated>...</automated></verify>
+<done>...</done>
+<evidence>...</evidence>
+</task>
 </tasks>
-
-<verification>
-[Overall phase checks]
-</verification>
-
-<success_criteria>
-[Measurable completion]
-</success_criteria>
-
-<output>
-Create `.planning/phases/XX-name/{phase}-{plan}-SUMMARY.md`
-</output>
+<verification>...</verification>
+<success_criteria>...</success_criteria>
+<output>Create `.planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md`</output>
 ```
 
 ## Common Planning Mistakes to Avoid

package/rcode/skills/_shared/state-sync-rule.md

@@ -8,7 +8,7 @@ Immediately after appending content to any of:
 
 - `.planning/ROADMAP.md` — milestones and phases
 - `.planning/epics.md` — epics and stories
-- `.rcode/phases/{phase}/sprint-{N}.md` — sprint commitments
+- `.planning/phases/{phase-dir}/{phase}-{plan}-SPRINT.md` — sprint commitments
 
 Call the state-sync helper:
 

package/rcode/skills/actions/1-analysis/rcode-document-project/SKILL.md

@@ -16,6 +16,8 @@ triggers:
   - "create LLM-friendly docs"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

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

@@ -11,6 +11,8 @@ triggers:
   - "forge a product idea"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

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

@@ -27,8 +27,19 @@ triggers:
   - "تحليل وثيقة المتطلبات"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
+> **Note (experimental, no execution consumer):** the epics/stories/dev-story pipeline this
+> skill is part of is not wired to `/rcode-execute` today — `rcode-executor` only reads
+> `*-SPRINT.md` files (see `rcode/agents/rcode-executor.md`). The only way to "run" a story
+> produced here is the manual `/rcode {dev-prompt-file}` invocation documented in
+> `rcode/workflows/dev-story.md`, which has none of `/rcode-execute`'s atomic-commit,
+> checkpoint, wave, or verification machinery. Treat this pipeline as experimental /
+> unsupported for production execution until a decision is made to either wire it to
+> `/rcode-execute` or deprecate it in favor of the SPRINT.md pipeline (see
+> `AUDIT-redundant-work.md` finding 2).
 
 ## Overview
 

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

@@ -29,6 +29,8 @@ triggers:
   - "صمم المتطلبات"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/2-plan/rcode-create-story/SKILL.md

@@ -27,8 +27,19 @@ triggers:
   - "جهّز القصة للتنفيذ"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
+> **Note (experimental, no execution consumer):** the epics/stories/dev-story pipeline this
+> skill is part of is not wired to `/rcode-execute` today — `rcode-executor` only reads
+> `*-SPRINT.md` files (see `rcode/agents/rcode-executor.md`). The only way to "run" a story
+> produced here is the manual `/rcode {dev-prompt-file}` invocation documented in
+> `rcode/workflows/dev-story.md`, which has none of `/rcode-execute`'s atomic-commit,
+> checkpoint, wave, or verification machinery. Treat this pipeline as experimental /
+> unsupported for production execution until a decision is made to either wire it to
+> `/rcode-execute` or deprecate it in favor of the SPRINT.md pipeline (see
+> `AUDIT-redundant-work.md` finding 2).
 
 ## Overview
 

package/rcode/skills/actions/2-plan/rcode-edit-prd/SKILL.md

@@ -16,6 +16,8 @@ triggers:
   - "change the scope in the PRD"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/2-plan/rcode-validate-prd/SKILL.md

@@ -16,6 +16,8 @@ triggers:
   - "audit the PRD"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/3-solutioning/rcode-check-implementation-readiness/SKILL.md

@@ -17,6 +17,8 @@ triggers:
   - "can we start building"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/3-solutioning/rcode-create-architecture/SKILL.md

@@ -20,6 +20,8 @@ triggers:
   decision to use X"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/4-implementation/rcode-checkpoint-preview/SKILL.md

@@ -12,6 +12,8 @@ triggers:
 user-invocable: true
 ---
 
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
+
 ## Overview
 
 Checkpoint preview skill for rcode.

package/rcode/skills/actions/4-implementation/rcode-code-review/SKILL.md

@@ -29,6 +29,8 @@ triggers:
   - "جودة الكود"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/4-implementation/rcode-correct-course/SKILL.md

@@ -18,6 +18,8 @@ triggers:
   - "change story mid-way"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/4-implementation/rcode-debug/SKILL.md

@@ -29,8 +29,8 @@ triggers:
   - "تتبّع السبب"
 user-invocable: false
 ---
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
-
 ## The Iron Law
 
 ```

package/rcode/skills/actions/4-implementation/rcode-dev-story/SKILL.md

@@ -17,6 +17,8 @@ triggers:
   - "implement .rcode/phases/{phase}/stories/{file}"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

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

@@ -16,6 +16,8 @@ triggers:
   - "extract learnings from this sprint"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/4-implementation/rcode-scaffold-project/SKILL.md

@@ -28,6 +28,8 @@ triggers:
   - "add rcode to existing project"
 user-invocable: true
 ---
+
+<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. -->
 @.rcode/references/karpathy-guidelines.md
 
 

package/rcode/skills/actions/4-implementation/rcode-sprint-planning/SKILL.md

@@ -40,8 +40,9 @@ Follow the instructions in ./workflow.md.
 
 ## Output Format
 
-- Output: .rcode/phases/{phase}/sprint-{N}.md
-- Fixed structure: Sprint Goal (one sentence) | Assumptions | Duration | Stories (with owners) | Capacity Used/Available | Risks | Definition of Done
+- Output: sprint-status.yaml (path from {status_file}, per workflow.md step 4) — an epic/story status tracker, NOT a SPRINT.md
+- Fixed structure: generated/last_updated/project metadata + development_status (epic -> stories -> retrospective, ordered)
+- Distinct from `/rcode-sprint-planning` the slash command (`rcode/workflows/sprint-planning.md`), which writes a SPRINT.md via a separate in-line flow
 - Stories ranked by priority from epics.md
 - Leave 20% capacity buffer
 - Do NOT commit to stories without explicit owners