@jenga-ai/agent 3.6.0 → 4.1.0

package/skills/j-reconcile/SKILL.md

@@ -1,19 +1,18 @@
 ---
 name: j.reconcile
-description: Polyfill alias of the reconcile skill under a collision-safe directory name. Identical behavior to /reconcile — Reconcile the scrum board with actual implementation state. Cross-checks every task's board status against git history and worktrees, merges orphaned worktree branches, demotes unimplemented "Done" items, promotes secretly-implemented items, flags code with no board provenance and offers /uncharted segment for it, and cleans stale entries from todo.md. Use when the board feels out of sync, after a big merge session, when tasks were completed outside the normal workflow, or when todo.md has grown stale. Trigger on phrases like "sync the board", "clean up the board", "reconcile", "board is out of date", "todo is stale", or "check what's really done". Use when the bare /reconcile form is shadowed by another tool's own built-in command of the same name.
+description: Reconcile the scrum board with actual implementation state. Cross-checks every task's board status against git history and worktrees, merges orphaned worktree branches, demotes unimplemented "Done" items, promotes secretly-implemented items, flags code with no board provenance and offers /uncharted segment for it, and cleans stale entries from todo.md. Use when the board feels out of sync, after a big merge session, when tasks were completed outside the normal workflow, or when todo.md has grown stale. Trigger on phrases like "sync the board", "clean up the board", "reconcile", "board is out of date", "todo is stale", or "check what's really done".
 metadata:
   prefered_agent: scrum-master
 output_types: id_list
 keywords:
   - j-reconcile
-  - polyfill
 ---
 
 # Reconcile — Board ↔ Code Synchronisation
 
-This skill is a literal-directory-name duplicate of `skills/reconcile/`. It exists so that `/j-reconcile` (and `j.j-reconcile`) give a guaranteed-unshadowed way to reach the same flow as `/reconcile`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/reconcile` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-reconcile/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-reconcile/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh reconcile` from `skills/reconcile/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/reconcile/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 Walks the full board (epics → stories → tasks), verifies each item's status against what actually exists in git, and fixes any drift. Also cleans `project/todo.md` of entries that are already done. Then runs the same check in reverse — code that exists with no board item and no EST-tagged commit behind it — and offers `/uncharted segment` for what it finds.
 
@@ -136,7 +135,41 @@ in-scope tasks when scoped) whose status is **not** a completed status (Pending,
 2. **Check documentation artefacts** as in phase 2.
 3. **Spot-check acceptance criteria** against the codebase.
 
-If implementation **is confirmed**:
+Before treating a matching commit as grounds to promote, run two more checks. These exist because
+a commit referencing a task ID is evidence the code was *touched*, not evidence it is *finished* —
+a separate, still-running `/do` pipeline for this exact task may have a real fix sitting unmerged
+in a worktree while an earlier, incomplete commit already landed on the branch this `/reconcile`
+pass is reading. This is the exact race documented in
+`project/rapports/problems/E40_S01_T05-premature-main-reconcile-vs-worktree-fix.md` — a `/reconcile`
+pass promoted a task to `Passed`/`Done` from a matching commit alone while a fallback developer/tester
+pipeline for that same task still had its bugfix unmerged on a worktree branch.
+
+4. **Check for an active concurrency-slot holder** — glob `project/queue/concurrency-slots-*.json`
+   (there can be several; one per orchestrating session, per `skills/j-do/SKILL.md`'s
+   `### 4.4. Developer Concurrency Slot Enforcement`). For each file found, check both
+   `.developer.holders` and `.tester.holders` for a key matching this task's id (`E##_S##_T##`) —
+   or, if this task belongs to a story-bundle dispatch, the containing story's id (`E##_S##`),
+   since a bundle acquires one shared slot keyed to the story id rather than one per task (`### 1.5`
+   step 3 of that skill). A matching key means a developer or tester subagent for this exact item is
+   (or very recently was) live in another session.
+5. **Check for an unmerged worktree or branch** — run `git worktree list` and `git branch --all`,
+   and look for an entry matching this task's `<E##_S##_T##-short-slug>` naming convention
+   (`skills/j-do/SKILL.md`'s worktree-naming convention, e.g. its Light Execution Path and Fallback
+   to Full Task-Scope Pipeline sections) that has not yet been merged into the branch this
+   `/reconcile` run is executing against. A match means real work for this task exists on a branch
+   this reconcile pass hasn't accounted for yet.
+
+If **either** check 4 or 5 matches, skip promotion for this task:
+- Leave the task's status exactly as it is now — do not touch `date_started`, `date_completed`, or
+  its `project/todo.md` entry.
+- Do **not** merge the branch/worktree found in check 5 yourself — that is a live pipeline's own
+  work-in-progress, not an orphaned branch like phase 2's merge case.
+- Report it in the reconcile report as **"likely still in-flight — skipped"** (see
+  `assets/report_format.md`'s "⏳ IN-FLIGHT — SKIPPED" section) — not silently promoted, and not
+  silently left unmentioned.
+- Continue to the next task in Phase 3 — this is a per-task skip, not a phase abort.
+
+If implementation **is confirmed** and **neither** check 4 nor 5 matched:
 - Update the task's status to **Passed** in its board file.
 - Set `date_completed` to today (ISO 8601).
 - If the task is listed in `project/todo.md`, **comment it out** by wrapping the line:

package/skills/j-reconcile/assets/report_format.md

@@ -18,6 +18,10 @@ Scope: <resolved scope — see forms below>
 ⬆️  PROMOTED (were incomplete → now Passed)
    🔧 E##_S##_T## · <Task Title>  — commits found, acceptance criteria met
 
+⏳ IN-FLIGHT — SKIPPED (implementation confirmed by commit, but not promoted — active work appears ongoing)
+   🔧 E##_S##_T## · <Task Title>  — concurrency-slot holder found in <concurrency-slots-file>
+   🔧 E##_S##_T## · <Task Title>  — unmerged branch <branch-name>
+
 🔄 ROLL-UP CHANGES
    📖 E##_S## · <Story Title>  — <old status> → <new status>
    📦 E## · <Epic Title>  — <old status> → <new status>
@@ -51,6 +55,13 @@ Scope: <resolved scope — see forms below>
   own epics/stories/tasks only — not the whole board's.
 - Omit any section that has zero items (e.g. if nothing was demoted, skip the DEMOTED block entirely).
 - The MERGED section should include the branch name that was merged.
+- The IN-FLIGHT — SKIPPED section is distinct from both PROMOTED and the ordinary "implementation
+  not confirmed, no action" case (which is never reported at all): it means Phase 3 found a
+  matching commit (implementation confirmed) but withheld promotion because an active
+  concurrency-slot holder or an unmerged matching worktree/branch was also found — see
+  `/reconcile`'s Phase 3. Name the specific reason found (the concurrency-slots file, or the
+  branch/worktree name) so the report is checkable, not just asserted. Omit this section entirely
+  when no task was skipped for this reason.
 - The TODO CLEANUP section is always shown if `project/todo.md` existed at the start, even if zero changes were made (in that case show all counts as 0).
 - If `project/todo.md` did not exist, omit the TODO CLEANUP section.
 - The DOD GAPS section is omitted if no completed stories have unchecked DoD checkboxes.

package/skills/j-reconcile/scripts/detect-unlinked-code.sh

@@ -143,7 +143,7 @@
 #   --board-dir <dir>    Board directory to consult.
 #                        Default: <repo-root>/project/board
 #   --resolver <path>    Path to resolve-segment-target.sh.
-#                        Default: ../../uncharted/scripts/resolve-segment-target.sh
+#                        Default: ../../j-uncharted/scripts/resolve-segment-target.sh
 #   --exclude <glob>     Additional exclusion, matched against the repo-relative
 #                        path with shell-glob semantics. Repeatable.
 #   --limit N            Cap on files listed per group. Default 10. 0 = unlimited.
@@ -292,7 +292,7 @@ REPO_ROOT=$(cd -- "$REPO_ROOT" && pwd -P)
 [ -n "$BOARD_DIR" ] || BOARD_DIR="$REPO_ROOT/project/board"
 
 # --- the borrowed linkage check -------------------------------------------------------------
-[ -n "$RESOLVER" ] || RESOLVER="$SCRIPT_DIR/../../uncharted/scripts/resolve-segment-target.sh"
+[ -n "$RESOLVER" ] || RESOLVER="$SCRIPT_DIR/../../j-uncharted/scripts/resolve-segment-target.sh"
 [ -f "$RESOLVER" ] || die 4 "board-linkage checker not found: $RESOLVER
   This script deliberately has no fallback implementation -- see the header. Restore
   skills/j-uncharted/scripts/resolve-segment-target.sh or pass --resolver <path>."

package/skills/j-reconcile-origin/SKILL.md

@@ -1,13 +1,12 @@
 ---
 name: j.reconcile-origin
-description: Polyfill alias of the reconcile-origin skill under a collision-safe directory name. Identical behavior to /reconcile-origin — Sync the current (or specified) branch with origin by rebasing local commits on top of the latest upstream state. Use when the bare /reconcile-origin form is shadowed by another tool's own built-in command of the same name.
+description: Sync the current (or specified) branch with origin by rebasing local commits on top of the latest upstream state.
 keywords:
   - "sync branch"
   - "rebase origin"
   - "reconcile origin"
   - "pull rebase"
   - j-reconcile-origin
-  - polyfill
 examples:
   - "sync my branch with origin"
   - "rebase local commits on top of origin"
@@ -17,9 +16,9 @@ examples:
 
 # Reconcile Origin
 
-This skill is a literal-directory-name duplicate of `skills/reconcile-origin/`. It exists so that `/j-reconcile-origin` (and `j.j-reconcile-origin`) give a guaranteed-unshadowed way to reach the same flow as `/reconcile-origin`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/reconcile-origin` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-reconcile-origin/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-reconcile-origin/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh reconcile-origin` from `skills/reconcile-origin/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/reconcile-origin/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 Use this skill to rebase local work on top of the latest `origin/<branch>` state without re-implementing git logic inline.
 

package/skills/j-redo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.redo
-description: Polyfill alias of the redo skill under a collision-safe directory name. Identical behavior to /redo — Redo parts or entire previous implementations identified by a commit SHA or an Epic/Story number (e.g. E01, E02_S03). Expects an identifier and a description of what to redo and why. Use when the user wants to revisit, rework, or rewrite previously completed work, including updating all affected documentation. Use when the bare /redo form is shadowed by another tool's own built-in command of the same name.
+description: Redo parts or entire previous implementations identified by a commit SHA or an Epic/Story number (e.g. E01, E02_S03). Expects an identifier and a description of what to redo and why. Use when the user wants to revisit, rework, or rewrite previously completed work, including updating all affected documentation.
 keywords:
   - redo
   - rework
@@ -8,7 +8,6 @@ keywords:
   - revisit
   - redo task
   - j-redo
-  - polyfill
 examples:
   - "redo the login implementation"
   - "rewrite story E02_S01"
@@ -19,9 +18,9 @@ metadata:
 
 # Redo — Rework a Previous Implementation
 
-This skill is a literal-directory-name duplicate of `skills/redo/`. It exists so that `/j-redo` (and `j.j-redo`) give a guaranteed-unshadowed way to reach the same flow as `/redo`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/redo` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-redo/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-redo/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh redo` from `skills/redo/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/redo/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Input Format
 

package/skills/j-skillify/SKILL.md

@@ -1,16 +1,15 @@
 ---
 name: j.skillify
-description: Polyfill alias of the skillify skill under a collision-safe directory name. Identical behavior to /skillify — Refactor one or more existing skills into a cleaner, more maintainable structure — extracting hardcoded content into asset files, offloading deterministic steps into scripts, and reorganizing the skill body to reflect the leaner result. Use this whenever the user wants to clean up, improve, or restructure an existing skill, mentions that a skill has hardcoded content that could be templated, or asks to "skillify", "refactor", or "tidy up" a skill. Trigger even if the user just pastes a skill and says something like "can we make this better?". Use when the bare /skillify form is shadowed by another tool's own built-in command of the same name.
+description: Refactor one or more existing skills into a cleaner, more maintainable structure — extracting hardcoded content into asset files, offloading deterministic steps into scripts, and reorganizing the skill body to reflect the leaner result. Use this whenever the user wants to clean up, improve, or restructure an existing skill, mentions that a skill has hardcoded content that could be templated, or asks to "skillify", "refactor", or "tidy up" a skill. Trigger even if the user just pastes a skill and says something like "can we make this better?".
 keywords:
   - j-skillify
-  - polyfill
 ---
 
 # Skillify — Refactor a Skill into a Cleaner Structure
 
-This skill is a literal-directory-name duplicate of `skills/skillify/`. It exists so that `/j-skillify` (and `j.j-skillify`) give a guaranteed-unshadowed way to reach the same flow as `/skillify`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/skillify` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-skillify/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-skillify/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh skillify` from `skills/skillify/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/skillify/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## What this skill does
 

package/skills/j-spinoff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.spinoff
-description: Polyfill alias of the spinoff skill under a collision-safe directory name. Identical behavior to /spinoff — Capture a diverging topic mid-conversation. Collects context and a mandatory origin, optionally runs /brainstorm for prerequisites, saves an /idea entry, and returns focus to the primary thread. Use when the bare /spinoff form is shadowed by another tool's own built-in command of the same name.
+description: Capture a diverging topic mid-conversation. Collects context and a mandatory origin, optionally runs /brainstorm for prerequisites, saves an /idea entry, and returns focus to the primary thread.
 keywords:
   - spinoff
   - diverge
@@ -8,7 +8,6 @@ keywords:
   - capture topic
   - new thread
   - j-spinoff
-  - polyfill
 examples:
   - "let's spinoff this idea"
   - "capture this as a separate thread"
@@ -19,9 +18,9 @@ metadata:
 
 # Spinoff — Capture a Diverging Topic
 
-This skill is a literal-directory-name duplicate of `skills/spinoff/`. It exists so that `/j-spinoff` (and `j.j-spinoff`) give a guaranteed-unshadowed way to reach the same flow as `/spinoff`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/spinoff` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-spinoff/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-spinoff/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh spinoff` from `skills/spinoff/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/spinoff/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 

package/skills/j-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: j.status
-description: Polyfill alias of the status skill under a collision-safe directory name. Identical behavior to /status — Print a human-readable summary of the entire scrum board — all epics, stories, and tasks with their statuses — plus any open rapports and unprocessed queue triggers. Use when you want a quick overview of project state without reading raw files. Use when the bare /status form is shadowed by another tool's own built-in command of the same name.
+description: Print a human-readable summary of the entire scrum board — all epics, stories, and tasks with their statuses — plus any open rapports and unprocessed queue triggers. Use when you want a quick overview of project state without reading raw files.
 output_types: text
 keywords:
   - status
@@ -9,7 +9,6 @@ keywords:
   - project state
   - what's done
   - j-status
-  - polyfill
 examples:
   - "show me the project status"
   - "what's the state of the board?"
@@ -18,9 +17,9 @@ examples:
 
 # Status — Board Overview
 
-This skill is a literal-directory-name duplicate of `skills/status/`. It exists so that `/j-status` (and `j.j-status`) give a guaranteed-unshadowed way to reach the same flow as `/status`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/status` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-status/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-status/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh status` from `skills/status/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/status/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## Instructions
 
@@ -40,7 +39,7 @@ This file is generated/synced by `scripts/generate-j-alias.sh status` from `skil
 `scripts/` directory of its own comparable to `/self-sync`'s, so invoke the shared pipeline
 directly rather than adding a third skill-local wrapper script:
    ```
-   bash scripts/mark-deployed.sh
+   bash "$([ -f scripts/mark-deployed.sh ] && echo scripts/mark-deployed.sh || echo node_modules/@jenga-ai/agent/scripts/mark-deployed.sh)"
    ```
    This defaults to invoking its own sibling `scripts/compute-deploy-reconcile.sh`, which
    discovers any not-yet-reconciled `vX.Y.Z-stage`/`vX.Y.Z` tags on the public `jenga-npm` repo

package/skills/j-todo/SKILL.md

@@ -1,7 +1,11 @@
 ---
 name: j.todo
-description: Polyfill alias of the todo skill under a collision-safe directory name. Identical behavior to /todo — Add missions to the project todo list (project/todo.md), optionally linking them to epics and stories. Loops until the user is done, then optionally executes the list. Use when the bare /todo form is shadowed by another tool's own built-in command of the same name.
-output_types: id_list
+description: Add missions to the project todo list (project/todo.md), optionally linking them to epics and stories. Loops until the user is done, then optionally executes the list.
+output_types:
+  - when: argument-is-ranked-list
+    type: ranked_list
+  - when: argument-is-not-ranked-list
+    type: id_list
 input_types: id_list
 keywords:
   - todo
@@ -10,7 +14,6 @@ keywords:
   - backlog
   - add to list
   - j-todo
-  - polyfill
 examples:
   - "add this to the todo list"
   - "queue this as a task"
@@ -21,9 +24,9 @@ metadata:
 
 # Todo — Add Missions to the Todo List
 
-This skill is a literal-directory-name duplicate of `skills/todo/`. It exists so that `/j-todo` (and `j.j-todo`) give a guaranteed-unshadowed way to reach the same flow as `/todo`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/todo` alias (Claude Code's native skill resolution is a literal-string, directory-name-based match — see `docs/skill-authoring.md`'s "Invocation Convention").
+`skills/j-todo/` is the **canonical, hand-edited** directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the `E50` reopening of 2026-09-09, which promoted `skills/j-todo/` from generated twin to sole canonical form). The `j-` prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see `docs/skill-authoring.md`'s "Invocation Convention").
 
-This file is generated/synced by `scripts/generate-j-alias.sh todo` from `skills/todo/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+> ⚠️ **`scripts/generate-j-alias.sh` was retired by `E50_S14` and no longer exists — there is nothing to run.** This file was previously generated from a bare `skills/todo/SKILL.md` source; `E50_S15` deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.
 
 ## `--trivial` Flag
 
@@ -35,8 +38,42 @@ When `--trivial` is present, the mission is written as a **fully-formed task boa
 
 **Fallback on failure is out of scope here.** If a `--trivial`-forced inline run fails the smoke-harness or shows scope creep at dispatch time, `/do`'s own `--trivial` handling (a separate task, E32_S14_T02) is responsible for falling back to the full `task` pipeline — this skill only ever writes the initial forced-inline task.
 
+## `--ranked-list` Flag
+
+**Syntax:** `/todo --ranked-list` — takes no other arguments.
+
+**Non-interactive, one-shot, read-only.** `--ranked-list` is a distinct mode, not a modifier on a
+normal `/todo` mission-add invocation. It calls the shared `scripts/render-ranked-list.sh` (built by
+`E63_S01_T01`; see that script's own header comment for the full eligibility rule and its env-var
+overrides — do not re-derive or restate the scan logic here) and prints its stdout **verbatim**, then
+exits — this is exactly the same script and the same eligibility scan `/dooo`'s own step 2/3 already
+uses (`skills/j-dooo/SKILL.md`), so `--ranked-list`'s output is byte-for-byte identical to `/dooo`'s
+list for the same board/`todo.md` state. Do not append a trailing "Done" option or any interactive
+prompt — that framing belongs to `/dooo`'s own UI layer on top of the script, not to the shared
+script's output, and not to `--ranked-list` either.
+
+**No mutation.** `--ranked-list` never writes `project/todo.md`, never writes a board file, and never
+dispatches a task. It is a pure read/render, matching `scripts/render-ranked-list.sh`'s own
+no-mutation contract.
+
+**Takes precedence over mission text.** If the user somehow passes `--ranked-list` together with
+mission text, treat `--ranked-list` as taking precedence and ignore the mission text — it has no
+mission to attach to, so it cannot combine the way `--trivial` combines with an epic/story reference.
+
+**Short-circuits the whole flow.** See step 0 below — when `--ranked-list` is passed, none of the
+normal `/todo` steps 1-6 (the "where/what/goal" questions, mission classification, board writes, the
+"add another" loop) are ever reached.
+
 ## Instructions
 
+0. **If `--ranked-list` was passed, handle it now and stop — do not proceed to step 1:**
+   ```
+   bash "$([ -f scripts/render-ranked-list.sh ] && echo scripts/render-ranked-list.sh || echo node_modules/@jenga-ai/agent/scripts/render-ranked-list.sh)"
+   ```
+   Print the script's stdout verbatim as the response (no added framing, no "Done" option, no
+   follow-up question) and end the skill invocation here. Steps 1-6 below do not apply to
+   `--ranked-list` at all.
+
 1. **Ensure `project/todo.md` exists** — If it doesn't exist, it will be auto-created by `todo_manager.sh` — no manual action needed.
 
 2. **Ask the user about the mission:**

package/skills/j-todo/scripts/add_trivial_task.sh

@@ -28,7 +28,18 @@
 
 set -euo pipefail
 
-REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../../.." && pwd)"
+# Locate the project root via git, not a fixed relative climb — this script
+# is deployed both at its source location (skills/j-todo/scripts/) and
+# mirrored to .claude/skills/j-todo/scripts/ / .agents/skills/j-todo/scripts/,
+# and a fixed "three levels up" climb lands in the wrong place from a mirror.
+# Same approach as skills/j-close-story/scripts/check-story-closeable.sh,
+# check-privatized.sh:138, and compute-scope-divergence.sh:54.
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+REPO_ROOT="$(git -C "$SCRIPT_DIR" rev-parse --show-toplevel 2>/dev/null || true)"
+if [[ -z "$REPO_ROOT" ]]; then
+  echo "ERROR: could not locate project root (git rev-parse --show-toplevel failed from $SCRIPT_DIR)" >&2
+  exit 1
+fi
 cd "$REPO_ROOT"
 
 TASKS_DIR="project/board/tasks"

package/skills/j-todo/scripts/argument-is-not-ranked-list.sh

@@ -0,0 +1,92 @@
+#!/usr/bin/env bash
+# ---------------------------------------------------------------------------
+# skills/j-todo/scripts/argument-is-not-ranked-list.sh
+#
+# Classifier for the OTHER half of j-todo's conditional `output_types` declaration
+# (E63_S01_T04, corrected). `output_types: id_list` was deliberately declared on j-todo by
+# `E53_S11_T01` ("j-todo (none) -> id_list (emits board item ids)") -- /todo's normal
+# mission-capture flow genuinely does produce a forwardable board-item id, and that claim is
+# still true after E63_S01_T03 added --ranked-list. It must stay declared, not be silently
+# dropped when the ranked_list branch is added alongside it.
+#
+# This script is the "when" for that id_list branch. It is the exact logical complement of
+# `argument-is-ranked-list.sh` -- deliberately implemented as a thin delegate to that script
+# rather than a second, independently-written check, so the two branches can never quietly
+# drift apart on what "--ranked-list" means. There is exactly one place that decision is made
+# (argument-is-ranked-list.sh); this script only inverts its verdict.
+#
+# Why not the built-in `argument_nonempty` predicate instead of a real script: `--ranked-list`
+# is ALSO a non-empty argument, so `argument_nonempty -> id_list` would be a false claim for
+# that one specific invocation shape (its actual output is ranked_list, never id_list). Using
+# the built-in here would pass load-playbooks.sh's structural check trivially (no script to
+# find), but it would misdescribe the one case this task exists to carve out -- exactly the
+# honesty-over-breadth violation E53_S11 rejects. A dedicated classifier that excludes
+# `--ranked-list` precisely is the honest choice.
+#
+# ---------------------------------------------------------------------------
+# USAGE
+# ---------------------------------------------------------------------------
+#   skills/j-todo/scripts/argument-is-not-ranked-list.sh "<raw /todo invocation argument>"
+#
+# ---------------------------------------------------------------------------
+# OUTPUT CONTRACT
+# ---------------------------------------------------------------------------
+# stdout is always a single JSON object:
+#
+#   {"classification": "normal"}       -- exit 0 -- the argument is anything OTHER than exactly
+#                                          `--ranked-list` (empty, mission text, `--trivial ...`,
+#                                          etc.) -- /todo's normal mission-capture flow applies.
+#   {"classification": "ranked_list"}  -- exit 1 -- the argument IS exactly `--ranked-list`; the
+#                                          complement branch (argument-is-ranked-list.sh) applies
+#                                          instead, not this one.
+#
+# ---------------------------------------------------------------------------
+# EXIT CODES
+# ---------------------------------------------------------------------------
+#   0   "normal" classification (see above)
+#   1   "ranked_list" classification (see above) -- a legitimate outcome, not an error
+#   2   usage error (no argument given), or the delegate script is missing/unreadable, or the
+#       delegate exited with an exit code this script does not recognize
+#
+# ---------------------------------------------------------------------------
+
+set -euo pipefail
+
+if [ $# -lt 1 ]; then
+  echo 'Usage: argument-is-not-ranked-list.sh "<raw /todo invocation argument>"' >&2
+  exit 2
+fi
+
+RAW_INPUT="$1"
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+RANKED_LIST_CLASSIFIER="$SCRIPT_DIR/argument-is-ranked-list.sh"
+
+if [ ! -f "$RANKED_LIST_CLASSIFIER" ]; then
+  echo "Error: argument-is-ranked-list.sh not found at $RANKED_LIST_CLASSIFIER" >&2
+  exit 2
+fi
+
+# Guard the capture explicitly so `set -e` doesn't abort this script on the delegate's own
+# legitimate non-zero exit (1 == "normal" from the delegate's point of view).
+set +e
+bash "$RANKED_LIST_CLASSIFIER" "$RAW_INPUT" >/dev/null 2>&1
+DELEGATE_EXIT=$?
+set -e
+
+case "$DELEGATE_EXIT" in
+  0)
+    # Delegate says "ranked_list" -- the complement is false.
+    echo '{"classification": "ranked_list"}'
+    exit 1
+    ;;
+  1)
+    # Delegate says "normal" -- the complement is true.
+    echo '{"classification": "normal"}'
+    exit 0
+    ;;
+  *)
+    echo "Error: argument-is-ranked-list.sh exited with unexpected status $DELEGATE_EXIT" >&2
+    exit 2
+    ;;
+esac

package/skills/j-todo/scripts/argument-is-ranked-list.sh

@@ -0,0 +1,78 @@
+#!/usr/bin/env bash
+# ---------------------------------------------------------------------------
+# skills/j-todo/scripts/argument-is-ranked-list.sh
+#
+# Classifier for `j-todo`'s conditional `output_types` declaration (E63_S01_T04). `/todo`'s normal
+# behavior (adding a mission to the board) produces no forwardable output -- only the distinct
+# `--ranked-list` invocation (E63_S01_T03) does, by printing `scripts/render-ranked-list.sh`'s
+# `ranked_list`-typed output verbatim (see `skills/j-todo/SKILL.md`'s "--ranked-list Flag" section).
+#
+# Declaring `output_types: ranked_list` unconditionally would misdescribe every normal /todo
+# invocation as a ranked_list producer, violating E53_S11's honesty-over-breadth policy. This script
+# is the classifier `skills/j-todo/SKILL.md`'s `output_types` keys off of instead, per
+# `docs/skill-authoring.md`'s conditional `{when, type}` form -- the same pattern `j.jenga` already
+# uses for `detect-nl-intent.sh`.
+#
+# Neither built-in predicate (`argument_empty` / `argument_nonempty`) fits here: `--ranked-list` is a
+# non-empty argument, but so is mission text and `--trivial ...` -- both of which still produce
+# `/todo`'s normal (undeclared-type) output, not `ranked_list`. `argument_nonempty` alone cannot tell
+# those apart, so this dedicated classifier exists to draw that one distinction.
+#
+# ---------------------------------------------------------------------------
+# WHAT THIS SCRIPT IS FOR (read before assuming it gates runtime routing)
+# ---------------------------------------------------------------------------
+# `skills/jenga/scripts/load-playbooks.sh` only ever checks that a classifier-script `when` value
+# resolves to an existing, executable file on disk under this skill's own `scripts/` directory -- it
+# never runs this script to decide which `output_types` branch actually fires (see
+# `docs/skill-authoring.md`'s "output_types" and "forward_from resolution" sections for the exact,
+# narrow claim that load-time check does and does not make). This script exists so that structural
+# check has a real file to find, and so the classification it names is genuinely correct if anything
+# ever does execute it (e.g. a future runtime-verification path) -- not because anything wires its
+# exit code into routing today. `skills/j-todo/SKILL.md`'s own step 0 short-circuit is what actually
+# decides the `--ranked-list` branch at real invocation time; this script's job is narrower and
+# purely descriptive.
+#
+# ---------------------------------------------------------------------------
+# USAGE
+# ---------------------------------------------------------------------------
+#   skills/j-todo/scripts/argument-is-ranked-list.sh "<raw /todo invocation argument>"
+#
+# ---------------------------------------------------------------------------
+# OUTPUT CONTRACT
+# ---------------------------------------------------------------------------
+# stdout is always a single JSON object:
+#
+#   {"classification": "ranked_list"}   -- exit 0 -- the argument, trimmed, is exactly `--ranked-list`
+#   {"classification": "normal"}        -- exit 1 -- anything else, including an empty argument,
+#                                           mission text, or `--trivial ...`
+#
+# ---------------------------------------------------------------------------
+# EXIT CODES
+# ---------------------------------------------------------------------------
+#   0   "ranked_list" classification (see above)
+#   1   "normal" classification (see above) -- a legitimate outcome, not an error
+#   2   usage error (no argument given)
+#
+# ---------------------------------------------------------------------------
+
+set -euo pipefail
+
+if [ $# -lt 1 ]; then
+  echo 'Usage: argument-is-ranked-list.sh "<raw /todo invocation argument>"' >&2
+  exit 2
+fi
+
+RAW_INPUT="$1"
+
+# Trim leading/trailing whitespace only -- no other normalization. `--ranked-list` "takes no other
+# arguments" per skills/j-todo/SKILL.md, so anything beyond the flag itself (e.g. trailing mission
+# text accidentally combined with it) is deliberately NOT classified as ranked_list here.
+TRIMMED="$(printf '%s' "$RAW_INPUT" | sed -e 's/^[[:space:]]*//' -e 's/[[:space:]]*$//')"
+
+if [ "$TRIMMED" = "--ranked-list" ]; then
+  echo '{"classification": "ranked_list"}'
+  exit 0
+fi
+
+echo '{"classification": "normal"}'
+exit 1