@jenga-ai/agent 2.0.0 → 3.1.0

package/skills/{publish → j-publish}/scripts/npm_stage_pipeline.sh

@@ -379,13 +379,18 @@ if [[ -z "${STAGE_ID}" ]] && printf '%s' "${STAGE_OUTPUT}" | jq -e . >/dev/null
   STAGE_ID="$(printf '%s' "${STAGE_OUTPUT}" | jq -r '.id // .stageId // .stage_id // empty' 2>/dev/null || true)"
 fi
 
-# Attempt 3: fall back to `npm stage list <package>@<version> --json` and
-# extract the most recent matching entry's id.
+# Attempt 3: fall back to `npm stage list <package> --json` and extract the
+# most recent matching entry's id. `npm stage list` rejects a version-
+# qualified spec ("Version specifiers are not supported for listing staged
+# packages") — it only accepts a bare package name — so this must pass
+# PACKAGE_NAME, never PACKAGE_SPEC; the version match happens client-side via
+# jq below instead (confirmed live on jenga-npm during v1.3.0 staging on
+# 2026-09-01, project/todo.md).
 if [[ -z "${STAGE_ID}" ]]; then
   log_warn "could not parse a stage id directly from stage output; falling back to 'npm stage list --json'..."
 
   LIST_STATUS=0
-  LIST_OUTPUT="$(npm stage list "${PACKAGE_SPEC}" --json 2>&1)" || LIST_STATUS=$?
+  LIST_OUTPUT="$(npm stage list "${PACKAGE_NAME}" --json 2>&1)" || LIST_STATUS=$?
 
   if [[ ${LIST_STATUS} -ne 0 ]]; then
     printf '%s\n' "${LIST_OUTPUT}" >&2
@@ -405,7 +410,7 @@ if [[ -z "${STAGE_ID}" ]]; then
 fi
 
 if [[ -z "${STAGE_ID}" ]]; then
-  printf 'npm stage pipeline: staged successfully but the stage id could not be captured from either the direct output or "npm stage list --json". Run "npm stage list %s --json" manually to recover it.\n' "${PACKAGE_SPEC}" >&2
+  printf 'npm stage pipeline: staged successfully but the stage id could not be captured from either the direct output or "npm stage list --json". Run "npm stage list %s --json" manually to recover it (bare package name — a version-qualified spec is rejected by npm).\n' "${PACKAGE_NAME}" >&2
   exit "${EXIT_STAGE_FAILURE}"
 fi
 

package/skills/{publish → j-publish}/scripts/publish_deploy.sh

@@ -463,16 +463,16 @@ print_manual_steps() {
   local adapter_doc
   case "$TARGET_TYPE" in
     droplet)
-      adapter_doc="$PUBLISH_REPO_ROOT/skills/publish/adapters/droplet.md"
+      adapter_doc="$PUBLISH_REPO_ROOT/skills/j-publish/adapters/droplet.md"
       ;;
     npm)
-      adapter_doc="$PUBLISH_REPO_ROOT/skills/publish/adapters/npm.md"
+      adapter_doc="$PUBLISH_REPO_ROOT/skills/j-publish/adapters/npm.md"
       ;;
     npm-ci)
-      adapter_doc="$PUBLISH_REPO_ROOT/skills/publish/adapters/npm-ci.md"
+      adapter_doc="$PUBLISH_REPO_ROOT/skills/j-publish/adapters/npm-ci.md"
       ;;
     mobile-ios)
-      adapter_doc="$PUBLISH_REPO_ROOT/skills/publish/adapters/mobile-ios.md"
+      adapter_doc="$PUBLISH_REPO_ROOT/skills/j-publish/adapters/mobile-ios.md"
       ;;
     *)
       return 0

package/skills/{publish → j-publish}/scripts/validate_npm_stage_env.sh

@@ -13,7 +13,7 @@
 # Exit codes:
 #   0  all four preflight checks passed
 #   4  one of the checks failed (config/environment invalid), matching
-#      skills/publish/assets/ci-contract.md
+#      skills/j-publish/assets/ci-contract.md
 #
 # Security note: the registry probe (check 4) never prints npm's raw stdout/stderr. Only
 # messages composed by this script are emitted, so nothing npm writes — which could in

package/skills/{publish → j-publish}/wizards/droplet.md

@@ -261,7 +261,7 @@ Once all answers have been collected, perform the following steps in order:
    ```
 
 4. **Validate against the schema.** Run
-   `bash skills/publish/scripts/validate_config.sh <path-to-publish.json>`
+   `bash skills/j-publish/scripts/validate_config.sh <path-to-publish.json>`
    before saving. If validation fails, report the error and abort — do not
    write a broken `publish.json`.
 

package/skills/{publish → j-publish}/wizards/mobile-ios.md

@@ -110,7 +110,7 @@ Optional short string such as `exampleco`.
 Maps to: `targets[].secrets.app_store_connect_api_key_id`
 
 Enter the environment-variable name that will supply the App Store Connect API key identifier.
-See `skills/publish/assets/secrets-guide.md` before answering.
+See `skills/j-publish/assets/secrets-guide.md` before answering.
 
 ## Expected format:
 

package/skills/{publish → j-publish}/wizards/npm-ci.md

@@ -213,7 +213,7 @@ Once all six answers have been collected, perform the following steps in order:
    - Do not include a `secrets` block — this adapter uses OIDC and no token
      is required.
 4. **Validate against the schema.** Run
-   `skills/publish/scripts/validate_config.sh` before saving. If validation
+   `skills/j-publish/scripts/validate_config.sh` before saving. If validation
    fails, report the error and abort — do not write a broken `publish.json`.
 5. **Report to the user.** Print a short summary confirming (a) the target
    block written, (b) the `github_repo` value, and (c) the `workflow_path`

package/skills/{publish → j-publish}/wizards/npm.md

@@ -97,7 +97,7 @@ deploy).
 ## Prerequisite: NPM_TOKEN
 
 The npm pipeline reads the auth token from the `NPM_TOKEN` environment
-variable at publish time (`skills/publish/adapters/npm.md` defines this
+variable at publish time (`skills/j-publish/adapters/npm.md` defines this
 contract). The wizard does not collect the token value — that would be
 unsafe. Instead, at the end of the wizard, write the following instructions
 file so the user knows exactly what to configure:

package/skills/{reconcile → j-reconcile}/SKILL.md

@@ -1,12 +1,19 @@
 ---
-name: j:reconcile
-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".
+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.
 metadata:
   prefered_agent: scrum-master
+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").
+
+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.
+
 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.
 
 ## Scope argument
@@ -35,7 +42,7 @@ Omitting the argument entirely keeps today's full-board behavior completely unch
 phase below.
 
 Scope resolution itself is deterministic and handled entirely by
-`skills/reconcile/scripts/resolve-reconcile-scope.sh` (see Phase 0 immediately below) — this skill
+`skills/j-reconcile/scripts/resolve-reconcile-scope.sh` (see Phase 0 immediately below) — this skill
 only interprets that script's output; it does not re-parse scope arguments or re-derive range
 expansion.
 
@@ -50,7 +57,7 @@ Before touching anything else, resolve the scope argument (if any — see "Scope
 into a concrete set of epic/story/task ids:
 
 ```bash
-skills/reconcile/scripts/resolve-reconcile-scope.sh <scope-argument>
+skills/j-reconcile/scripts/resolve-reconcile-scope.sh <scope-argument>
 ```
 
 Omit `<scope-argument>` entirely for an unscoped, full-board run (the script's own no-argument
@@ -176,7 +183,7 @@ Phases 2 and 3 ask "does this board item exist in the code?". This phase asks th
 Run:
 
 ```bash
-skills/reconcile/scripts/detect-unlinked-code.sh
+skills/j-reconcile/scripts/detect-unlinked-code.sh
 ```
 
 It emits a single JSON object and exits `0` whether or not it finds anything; read

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

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 # ---------------------------------------------------------------------------
-# skills/reconcile/scripts/detect-unlinked-code.sh
+# skills/j-reconcile/scripts/detect-unlinked-code.sh
 #
 # The inverse half of `/reconcile`. The normal pass asks "does this board item
 # exist in the code?"; this asks "does this code exist on the board?" and finds
@@ -31,7 +31,7 @@
 # It scans, it classifies, it reports. It NEVER writes anything, never touches
 # the board, and never invokes `/uncharted`. Deciding which groups are worth
 # investigating and presenting the offer is agent judgement and lives in
-# `skills/reconcile/SKILL.md`.
+# `skills/j-reconcile/SKILL.md`.
 #
 # ---------------------------------------------------------------------------
 # SIGNAL A IS BORROWED, NOT REBUILT

package/skills/{reconcile → j-reconcile}/scripts/resolve-reconcile-scope.sh

@@ -1,10 +1,10 @@
 #!/usr/bin/env bash
 # ---------------------------------------------------------------------------
-# skills/reconcile/scripts/resolve-reconcile-scope.sh
+# skills/j-reconcile/scripts/resolve-reconcile-scope.sh
 #
 # Deterministic scope-argument resolver backing `/reconcile`'s new scope
 # argument (story E17_S07). This script owns ALL scope-argument parsing and
-# id-range expansion for `/reconcile` — `skills/reconcile/SKILL.md` (wired in
+# id-range expansion for `/reconcile` — `skills/j-reconcile/SKILL.md` (wired in
 # the sibling task E17_S07_T02) only interprets this script's structured
 # stdout output; it must not re-derive any parsing or resolution logic
 # inline.
@@ -124,7 +124,7 @@
 #     "epic_ids":         ["E12"],
 #     "story_ids":        ["E12_S03", "E12_S04", "E12_S05"],
 #     "task_ids":         ["E12_S03_T01", "..."],
-#     "owned_path_hints": ["skills/reconcile/", "..."]
+#     "owned_path_hints": ["skills/j-reconcile/", "..."]
 #   }
 #
 #   scope_type "full"   epic_ids/story_ids/task_ids are all EMPTY arrays.

package/skills/{reconcile-origin → j-reconcile-origin}/SKILL.md

@@ -1,19 +1,26 @@
 ---
-name: j:reconcile-origin
-description: Sync the current (or specified) branch with origin by rebasing local commits on top of the latest upstream state.
+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.
 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"
   - "reconcile-origin feature/my-branch"
+  - "j-reconcile-origin"
 ---
 
 # 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").
+
+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.
+
 Use this skill to rebase local work on top of the latest `origin/<branch>` state without re-implementing git logic inline.
 
 ## Instructions
@@ -22,7 +29,7 @@ Use this skill to rebase local work on top of the latest `origin/<branch>` state
    - If the user passed an argument, use that branch name.
    - Otherwise, use the current branch name.
 
-2. Invoke `.agents/skills/reconcile-origin/scripts/reconcile-origin.sh [<branch>]` and capture stdout.
+2. Invoke `.agents/skills/j-reconcile-origin/scripts/reconcile-origin.sh [<branch>]` and capture stdout.
    - Do not run any inline git commands in this skill — all git work is handled by the script.
    - The script handles dirty-worktree detection internally and returns `{"status":"error","code":"uncommitted_changes",...}` if the working tree is not clean.
 
@@ -38,7 +45,7 @@ Use this skill to rebase local work on top of the latest `origin/<branch>` state
        2. Cancel and inspect the branch setup manually
        3. Other (describe below)
 
-     - If the user chooses option 1, invoke `.agents/skills/reconcile-origin/scripts/reconcile-origin.sh <branch> --create-tracking`.
+     - If the user chooses option 1, invoke `.agents/skills/j-reconcile-origin/scripts/reconcile-origin.sh <branch> --create-tracking`.
      - If `remote_exists` is `false`, explain that neither a local branch nor `origin/<branch>` was found and stop.
    - `conflict`
      - Present one structured conflict rapport per item in `conflicts`.
@@ -55,7 +62,7 @@ Use this skill to rebase local work on top of the latest `origin/<branch>` state
        3. Handle it later — leave annotated conflict markers in the file and continue the scripted flow
        4. Other (describe below)
 
-     - If the user chooses “Handle it later”, invoke `.agents/skills/reconcile-origin/scripts/reconcile-origin.sh <branch> --handle-later <file>` for the selected conflict file.
+     - If the user chooses “Handle it later”, invoke `.agents/skills/j-reconcile-origin/scripts/reconcile-origin.sh <branch> --handle-later <file>` for the selected conflict file.
    - `handled_later`
      - Confirm that the selected file was annotated for later resolution.
      - Tell the user the conflict markers were intentionally preserved with a `# RECONCILE-ORIGIN CONFLICT:` note.
@@ -71,5 +78,5 @@ Use this skill to rebase local work on top of the latest `origin/<branch>` state
 
 ## Guard Rails
 
-- All git work must go through `.agents/skills/reconcile-origin/scripts/reconcile-origin.sh`.
+- All git work must go through `.agents/skills/j-reconcile-origin/scripts/reconcile-origin.sh`.
 - Do not inline fetch, checkout, pull, merge, rebase, or status commands in this skill body.

package/skills/{redo → j-redo}/SKILL.md

@@ -1,21 +1,28 @@
 ---
-name: j:redo
-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.
+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.
 keywords:
   - redo
   - rework
   - rewrite
   - revisit
   - redo task
+  - j-redo
+  - polyfill
 examples:
   - "redo the login implementation"
   - "rewrite story E02_S01"
+  - "j-redo"
 metadata: 
   prefered_agent: scrum-master
 ---
 
 # 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").
+
+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.
+
 ## Input Format
 
 ```

package/skills/{skillify → j-skillify}/SKILL.md

@@ -1,10 +1,17 @@
 ---
-name: j:skillify
-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?".
+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.
+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").
+
+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.
+
 ## What this skill does
 
 Takes one or more existing skills and refactors them by:
@@ -65,4 +72,4 @@ The rewritten SKILL.md should:
 - `assets/init-old/SKILL.md` — The init skill before refactoring (hardcoded heredocs, inline JSON, hardcoded directory list)
 - `assets/init-new/SKILL.md` — The init skill after refactoring (all content in assets, steps delegated to `init.sh`)
 
-Read these when you need a concrete example of the before/after pattern.
+Read these when you need a concrete example of the before/after pattern.

package/skills/{spinoff → j-spinoff}/SKILL.md

@@ -1,21 +1,28 @@
 ---
-name: j:spinoff
-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.
+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.
 keywords:
   - spinoff
   - diverge
   - side topic
   - capture topic
   - new thread
+  - j-spinoff
+  - polyfill
 examples:
   - "let's spinoff this idea"
   - "capture this as a separate thread"
+  - "j-spinoff"
 metadata:
   prefered_agent: scrum-master
 ---
 
 # 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").
+
+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.
+
 ## Instructions
 
 1. **Identify the diverging topic** — Ask the user to confirm or briefly describe the diverging topic.

package/skills/{status → j-status}/SKILL.md

@@ -1,19 +1,26 @@
 ---
-name: j:status
-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.
+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.
 keywords:
   - status
   - board summary
   - overview
   - project state
   - what's done
+  - j-status
+  - polyfill
 examples:
   - "show me the project status"
   - "what's the state of the board?"
+  - "j-status"
 ---
 
 # 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").
+
+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.
+
 ## Instructions
 
 1. **Read `project/configs/workflow.json`** to confirm board paths. Fall back to `project/board/` if the file does not exist.

package/skills/{todo → j-todo}/SKILL.md

@@ -1,21 +1,28 @@
 ---
-name: j:todo
-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.
+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.
 keywords:
   - todo
   - add task
   - queue work
   - backlog
   - add to list
+  - j-todo
+  - polyfill
 examples:
   - "add this to the todo list"
   - "queue this as a task"
+  - "j-todo"
 metadata: 
   prefered_agent: scrum-master
 ---
 
 # 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").
+
+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.
+
 ## `--trivial` Flag
 
 **Syntax:** `/todo --trivial <description>` — optionally combined with the same `: <Epic no.>_<Story no.>` linkage syntax normal `/todo` entries use, e.g. `/todo --trivial Fix typo in error message: E12_S03`.
@@ -58,7 +65,7 @@ When `--trivial` is present, the mission is written as a **fully-formed task boa
 
    c. **Run the helper script**, which handles everything mechanical — next task-ID assignment, writing the task board file with `execution_scope: inline` forced, registering the new task ID into the parent story's `tasks:` frontmatter list, and adding the `project/todo.md` entry using the full task ID (so `/do` routes straight into its Inline Execution Path with no redundant breakdown pass):
       ```
-      bash skills/todo/scripts/add_trivial_task.sh \
+      bash skills/j-todo/scripts/add_trivial_task.sh \
         --story <E##_S##> \
         --title "<mission title>" \
         --description "<mission description>" \

package/skills/{todo → j-todo}/assets/todo_handoff_template.md

@@ -13,7 +13,7 @@
 <!-- PLACEHOLDER: what this todo is trying to achieve -->
 
 ## Affected Files or Scope
-<!-- PLACEHOLDER: which files, modules, or areas are involved, e.g. src/auth/, skills/todo/ -->
+<!-- PLACEHOLDER: which files, modules, or areas are involved, e.g. src/auth/, skills/j-todo/ -->
 
 ## Intended Approach
 <!-- PLACEHOLDER: step-by-step or high-level approach to the work -->

package/skills/{todo → j-todo}/scripts/add_trivial_task.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# skills/todo/scripts/add_trivial_task.sh
+# skills/j-todo/scripts/add_trivial_task.sh
 #
 # Creates a fully-formed task board file for a `/todo --trivial` mission,
 # forced to execution_scope: inline unconditionally, and registers it both
@@ -10,7 +10,7 @@
 # The JUDGMENT half — estimating file/line counts and deciding what
 # execution_scope the normal heuristic in agents/scrum-master.md would have
 # assigned (computed_tier) — happens in the calling agent's instructions
-# (skills/todo/SKILL.md), per the Skill Implementation Principle: a step that
+# (skills/j-todo/SKILL.md), per the Skill Implementation Principle: a step that
 # requires reasoning about branching logic, new dependencies, etc. does not
 # belong in a script. This script never reads project/configs/scope-thresholds.json
 # or recomputes computed_tier itself — it only records what it was told.
@@ -33,7 +33,7 @@ cd "$REPO_ROOT"
 
 TASKS_DIR="project/board/tasks"
 STORIES_DIR="project/board/stories"
-UPDATE_STORY_SCRIPT="skills/todo/scripts/update_story_tasks.py"
+UPDATE_STORY_SCRIPT="skills/j-todo/scripts/update_story_tasks.py"
 
 story_id=""
 title=""

package/skills/{todo → j-todo}/scripts/update_story_tasks.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-skills/todo/scripts/update_story_tasks.py
+skills/j-todo/scripts/update_story_tasks.py
 
 Mechanically inserts a task ID into a story board file's `tasks:` frontmatter
 list, if it is not already present. Idempotent (a re-run with the same
@@ -12,7 +12,7 @@ scripts/with-lock.sh, keyed to the story file, per templates/SCRUM_BOARD_SCHEMA.
 File Locking section (board frontmatter writes must go through the lock wrapper).
 
 Usage:
-    python3 skills/todo/scripts/update_story_tasks.py <story-file> <task-id>
+    python3 skills/j-todo/scripts/update_story_tasks.py <story-file> <task-id>
 
 Exit codes:
     0   success (task_id inserted, or already present)