@jenga-ai/agent 3.5.0 → 4.0.0

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

@@ -37,7 +37,7 @@
 # SIGNAL A IS BORROWED, NOT REBUILT
 # ---------------------------------------------------------------------------
 # The board-linkage question is answered by
-# `skills/uncharted/scripts/resolve-segment-target.sh` (E40_S02_T01) through its
+# `skills/j-uncharted/scripts/resolve-segment-target.sh` (E40_S02_T01) through its
 # documented batch interface:
 #
 #     git ls-files | resolve-segment-target.sh --paths-from -
@@ -70,7 +70,7 @@
 #
 # This is deliberate. `run-engine.sh` currently renders the out-of-repo
 # `not_checked` case as `unlinked` in its understanding document, which asserts
-# a verified absence that was never verified. `skills/uncharted/SKILL.md` names
+# a verified absence that was never verified. `skills/j-uncharted/SKILL.md` names
 # Step 1 (`resolve-segment-target.sh`) authoritative on linkage where the two
 # disagree, so this script passes the resolver's status through unchanged and
 # does not repeat that conflation.
@@ -104,8 +104,8 @@
 # Classifying files and then reporting directories would assert about a
 # directory something that was only ever verified about its contents. Because
 # the resolver's match is a path-boundary test, a board item naming
-# `skills/convert/` links THAT DIRECTORY without linking
-# `skills/convert/convert_cli.py`. Both facts are true, and the directory-level
+# `skills/j-convert/` links THAT DIRECTORY without linking
+# `skills/j-convert/convert_cli.py`. Both facts are true, and the directory-level
 # one is what decides whether a segment is worth investigating -- offering
 # `/uncharted segment` there would duplicate a board item that already exists.
 #
@@ -125,7 +125,7 @@
 # MIRROR SPELLINGS. Per CLAUDE.md the canonical file lives in the root tree and
 # `.agents/`, `.claude/` are generated build outputs -- but older board items
 # were often written against the mirror path. E17_S05 owns `/reconcile-origin`
-# and names it `.agents/skills/reconcile-origin/SKILL.md`, so a match on the
+# and names it `.agents/skills/j-reconcile-origin/SKILL.md`, so a match on the
 # root path alone misses a board item that plainly owns the directory. Each
 # group directory is therefore asked about under its own name and under both
 # mirror prefixes, and `directory_linkage.matched_as` records which spelling
@@ -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.
@@ -187,14 +187,14 @@
 #                  "not_checked_paths": N,
 #                  "groups": N, "covered_groups": N },
 #     "groups": [
-#       { "directory": "skills/skillify",
+#       { "directory": "skills/j-skillify",
 #         "unlinked_count": N,        // files keyed to THIS group
 #         "subtree_candidates": N,    // all candidates under the directory
 #         "subtree_unlinked": N,      // all unlinked under the directory
 #         "fully_unlinked": true,
 #         "directory_linkage": { "status": "unlinked", "reason": "...",
 #                                "items": [], "match_count": 0,
-#                                "matched_as": "skills/skillify" },
+#                                "matched_as": "skills/j-skillify" },
 #         "files": ["..."],           // capped by --limit
 #         "files_truncated": N }
 #     ],
@@ -292,10 +292,10 @@ 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/uncharted/scripts/resolve-segment-target.sh or pass --resolver <path>."
+  skills/j-uncharted/scripts/resolve-segment-target.sh or pass --resolver <path>."
 [ -x "$RESOLVER" ] || die 4 "board-linkage checker is not executable: $RESOLVER"
 RESOLVER=$(cd -- "$(dirname -- "$RESOLVER")" && pwd -P)/$(basename -- "$RESOLVER")
 
@@ -572,8 +572,8 @@ for path, status in sorted(status_of.items()):
 # --- second pass: is the GROUP DIRECTORY itself on the board? ---------------------------------
 # Reporting a directory while only ever having checked the files inside it asserts an absence
 # that was never verified -- the same error this script is careful to avoid for `not_checked`.
-# The resolver's match is a path-boundary test, so a board item naming `skills/convert/` links
-# that directory without linking `skills/convert/convert_cli.py`. Both facts are true and the
+# The resolver's match is a path-boundary test, so a board item naming `skills/j-convert/` links
+# that directory without linking `skills/j-convert/convert_cli.py`. Both facts are true and the
 # directory-level one is the one that decides whether a segment is worth investigating.
 #
 # Same borrowed checker, same batch interface, one extra call. No new linkage logic -- the only
@@ -582,7 +582,7 @@ for path, status in sorted(status_of.items()):
 # MIRROR SPELLINGS. Per CLAUDE.md the canonical file lives in the root tree and `.agents/` and
 # `.claude/` are generated build outputs, but plenty of older board items were written against
 # the mirror path -- E17_S05 owns `/reconcile-origin` and names it as
-# `.agents/skills/reconcile-origin/SKILL.md`. A boundary match on the root path alone therefore
+# `.agents/skills/j-reconcile-origin/SKILL.md`. A boundary match on the root path alone therefore
 # misses a board item that plainly owns the directory. So each directory is asked about under its
 # own name and under both mirror prefixes, and a hit on any spelling is board provenance. This
 # adds path spellings to the QUESTION; it does not add a second answer to it.

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
 
@@ -60,7 +59,7 @@ Compare the user's redo description against the original implementation to deter
 Summarise scope findings to the user in a brief list before continuing.
 
 ### 3. Plan the redo
-Populate `skills/todo/assets/todo_handoff_template.md` with the following pre-collected context:
+Populate `skills/j-todo/assets/todo_handoff_template.md` with the following pre-collected context:
 - **Mission title**: a short name for the redo work
 - **Goal / objective**: the redo objective — what is changing and the desired outcome
 - **Affected files or scope**: code, tests, and documentation files identified in step 2

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
 
@@ -44,7 +43,7 @@ This file is generated/synced by `scripts/generate-j-alias.sh spinoff` from `ski
 
 4. **Run /brainstorm (if chosen)** — Invoke the `/brainstorm` skill, passing the diverging topic and collected context as the opening prompt. After `/brainstorm` completes, use the refined output as the idea description.
 
-5. **Save via `/idea`** — Populate `skills/idea/assets/idea_handoff_template.md` with the context collected so far:
+5. **Save via `/idea`** — Populate `skills/j-idea/assets/idea_handoff_template.md` with the context collected so far:
    - **Mission title**: the diverging topic name (as confirmed in step 1)
    - **Goal / objective**: what the diverging topic aims to achieve
    - **Affected files or scope**: any files or modules identified during the conversation

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
 
@@ -36,6 +35,21 @@ This file is generated/synced by `scripts/generate-j-alias.sh status` from `skil
 
 6. **Check the queue** — If `project/queue/scrum_triggers.jsonl` is non-empty, note the number of pending triggers awaiting the scrum master.
 
+6.5. **Run the deploy-reconcile pass** (`E51_S05`) before printing the summary — `/status` has no
+`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 "$([ -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
+   (unauthenticated read — no credential required) and promotes matching `Publicized`/
+   `Deployed to Stage` tickets to `Deployed to Stage`/`Deployed to Prod` (writing
+   `date_deployed_prod` on a Prod promotion) by commit ancestry, before this skill re-scans the
+   board in steps 2-4 above. This step is **non-fatal**: a failure anywhere in the pipeline
+   (including an unreachable public repo) is logged as a warning only and never prevents `/status`
+   from printing whatever board state it already has, and never causes a non-zero exit.
+
 7. **Print the summary** following the layout and icon conventions in `assets/output_format.md`.
 
 8. If no epics exist, print: `No board items found. Run /pi-plan to define epics or /todo to add items.`

package/skills/j-todo/SKILL.md

@@ -1,6 +1,12 @@
 ---
 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.
+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
   - add task
@@ -8,7 +14,6 @@ keywords:
   - backlog
   - add to list
   - j-todo
-  - polyfill
 examples:
   - "add this to the todo list"
   - "queue this as a task"
@@ -19,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
 
@@ -29,12 +34,46 @@ This file is generated/synced by `scripts/generate-j-alias.sh todo` from `skills
 
 When `--trivial` is present, the mission is written as a **fully-formed task board file immediately** (not just a raw `todo.md` line deferred to `/do`'s own breakdown pass) with `execution_scope: inline` forced unconditionally — no threshold computation is consulted for the scope value itself. See step 4.5 below for the mechanics.
 
-**Human-only override.** `--trivial` is invoked by a human typing `/todo --trivial ...` — it is never applied by the scrum-master to itself during autonomous story/epic breakdown elsewhere (e.g. `/jenga`'s Phase 0.5, or `/do`'s own scrum-master decomposition step in `skills/do/SKILL.md` step 3). Those paths keep using the normal heuristic-only `execution_scope` assignment documented in `agents/scrum-master.md`'s Execution Scope Assignment section, unmodified by this flag.
+**Human-only override.** `--trivial` is invoked by a human typing `/todo --trivial ...` — it is never applied by the scrum-master to itself during autonomous story/epic breakdown elsewhere (e.g. `/jenga`'s Phase 0.5, or `/do`'s own scrum-master decomposition step in `skills/j-do/SKILL.md` step 3). Those paths keep using the normal heuristic-only `execution_scope` assignment documented in `agents/scrum-master.md`'s Execution Scope Assignment section, unmodified by this flag.
 
 **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/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