@jenga-ai/agent 1.3.0 → 3.0.0

package/skills/j-doc/scripts/resolve_last_update.py

@@ -0,0 +1,149 @@
+#!/usr/bin/env python3
+"""Resolve /doc last_update provenance from scrum board annotations."""
+
+from __future__ import annotations
+
+import argparse
+import json
+import sys
+from datetime import date
+from pathlib import Path
+from typing import Any
+
+COMPLETED_STATUSES = {"Done", "Passed"}
+BOARD_DIRS = (
+    ("epic", Path("project/board/epics")),
+    ("story", Path("project/board/stories")),
+    ("task", Path("project/board/tasks")),
+)
+
+
+def parse_args() -> argparse.Namespace:
+    parser = argparse.ArgumentParser(
+        description="Resolve the latest completed board date for a documentation target.",
+    )
+    parser.add_argument("target_path", help="Repo-relative documentation target path, e.g. README.md")
+    parser.add_argument(
+        "--root",
+        default=Path(__file__).resolve().parents[3],
+        type=Path,
+        help="Repository root containing project/board/",
+    )
+    return parser.parse_args()
+
+
+def parse_scalar(value: str) -> Any:
+    text = value.strip()
+    if text in {"", "null", "~"}:
+        return ""
+    if text.startswith("[") and text.endswith("]"):
+        inner = text[1:-1].strip()
+        if not inner:
+            return []
+        return [item.strip().strip("\"'") for item in inner.split(",") if item.strip()]
+    return text.strip("\"'")
+
+
+def parse_frontmatter(path: Path) -> dict[str, Any]:
+    text = path.read_text(encoding="utf-8")
+    if not text.startswith("---\n"):
+        raise ValueError("missing opening frontmatter delimiter")
+    parts = text.split("\n---\n", 1)
+    if len(parts) != 2:
+        raise ValueError("missing closing frontmatter delimiter")
+
+    lines = parts[0].splitlines()[1:]
+    data: dict[str, Any] = {}
+    current_key: str | None = None
+
+    for line in lines:
+        if not line.strip():
+            continue
+        if line.startswith("  - "):
+            if current_key is None:
+                raise ValueError(f"orphaned list item: {line.strip()}")
+            existing = data.get(current_key, "")
+            if existing == "":
+                existing = []
+                data[current_key] = existing
+            if not isinstance(existing, list):
+                raise ValueError(f"frontmatter key {current_key!r} is not a list")
+            existing.append(line[4:].strip().strip("\"'"))
+            continue
+        if ":" not in line:
+            raise ValueError(f"invalid frontmatter line: {line}")
+        key, raw_value = line.split(":", 1)
+        key = key.strip()
+        value = parse_scalar(raw_value)
+        data[key] = value
+        current_key = key if value == "" else None
+
+    return data
+
+
+def iter_matches(root: Path, target_path: str):
+    for item_type, relative_dir in BOARD_DIRS:
+        board_dir = root / relative_dir
+        if not board_dir.exists():
+            continue
+        for path in sorted(board_dir.glob("*.md")):
+            try:
+                frontmatter = parse_frontmatter(path)
+            except Exception as exc:  # pragma: no cover - defensive degradation
+                print(f"warning: skipping {path}: {exc}", file=sys.stderr)
+                continue
+
+            if frontmatter.get("status") not in COMPLETED_STATUSES:
+                continue
+
+            docs = frontmatter.get("docs")
+            if not isinstance(docs, list) or target_path not in docs:
+                continue
+
+            completed_raw = str(frontmatter.get("date_completed", "")).strip()
+            if not completed_raw:
+                print(
+                    f"warning: skipping {path}: matching docs annotation without date_completed",
+                    file=sys.stderr,
+                )
+                continue
+
+            try:
+                completed_on = date.fromisoformat(completed_raw)
+            except ValueError:
+                print(
+                    f"warning: skipping {path}: invalid date_completed {completed_raw!r}",
+                    file=sys.stderr,
+                )
+                continue
+
+            yield {
+                "id": frontmatter.get("id") or path.stem,
+                "type": item_type,
+                "status": frontmatter.get("status"),
+                "date_completed": completed_on.isoformat(),
+                "path": path.relative_to(root).as_posix(),
+            }
+
+
+def main() -> int:
+    args = parse_args()
+    root = args.root.resolve()
+    matches = sorted(
+        iter_matches(root, args.target_path),
+        key=lambda item: (item["date_completed"], item["id"]),
+    )
+    last_update = matches[-1]["date_completed"] if matches else "unknown"
+    payload = {
+        "target_path": args.target_path,
+        "last_update": last_update,
+        "provenance_found": bool(matches),
+        "fallback": "unknown",
+        "matched_items": matches,
+    }
+    print(json.dumps(payload, ensure_ascii=False))
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

package/skills/{doc-sync → j-doc-sync}/SKILL.md

@@ -1,18 +1,25 @@
 ---
-name: doc-sync
-description: Compare the current state of a project with its documentation and update documentation to reflect changes. Accepts `update:`, `source:`, `exclude:`, and `minify:` arguments to control scope. Use when documentation may be out of date with implementation, or when the user asks to sync, refresh, update, or shrink docs.
+name: j.doc-sync
+description: Polyfill alias of the doc-sync skill under a collision-safe directory name. Identical behavior to /doc-sync — Compare the current state of a project with its documentation and update documentation to reflect changes. Accepts `update:`, `source:`, `exclude:`, and `minify:` arguments to control scope. Use when documentation may be out of date with implementation, or when the user asks to sync, refresh, update, or shrink docs. Use when the bare /doc-sync form is shadowed by another tool's own built-in command of the same name.
 keywords:
   - doc-sync
   - documentation
   - update docs
   - sync docs
+  - j-doc-sync
+  - polyfill
 examples:
   - "update the documentation"
   - "sync docs with current state"
+  - "j-doc-sync"
 ---
 
 # Doc-Sync — Keep Documentation in Sync with the Codebase
 
+This skill is a literal-directory-name duplicate of `skills/doc-sync/`. It exists so that `/j-doc-sync` (and `j.j-doc-sync`) give a guaranteed-unshadowed way to reach the same flow as `/doc-sync`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/doc-sync` 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 doc-sync` from `skills/doc-sync/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## What this skill does
 
 Analyses project source files, compares them against existing documentation, and updates any documentation that is stale, incomplete, or missing. Can be scoped with arguments to focus on specific files or exclude noise.

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

@@ -1,21 +1,28 @@
 ---
-name: dooo
-description: Parallel execution orchestrator. Calls /do to start implementations via sub-agents, then loops back to the board to identify and offer parallelisable tasks until the user selects "Done".
+name: j.dooo
+description: Polyfill alias of the dooo skill under a collision-safe directory name. Identical behavior to /dooo — Parallel execution orchestrator. Calls /do to start implementations via sub-agents, then loops back to the board to identify and offer parallelisable tasks until the user selects "Done". Use when the bare /dooo form is shadowed by another tool's own built-in command of the same name.
 keywords:
   - dooo
   - parallel
   - batch
   - multiple tasks
   - orchestrate
+  - j-dooo
+  - polyfill
 examples:
   - "run all pending tasks in parallel"
   - "execute multiple tasks at once"
+  - "j-dooo"
 metadata:
   prefered_agent: scrum-master
 ---
 
 # Dooo — Parallel Execution Orchestrator
 
+This skill is a literal-directory-name duplicate of `skills/dooo/`. It exists so that `/j-dooo` (and `j.j-dooo`) give a guaranteed-unshadowed way to reach the same flow as `/dooo`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/dooo` 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 dooo` from `skills/dooo/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## Instructions
 
 ### 1. Invoke `/do`

package/skills/j-error/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: j.error
+description: Polyfill alias of the error skill under a collision-safe directory name. Identical behavior to /error — Guided troubleshooting flow that gathers context about an error — where it occurs, what was attempted, what went wrong, and what was expected. Use when the bare /error form is shadowed by another tool's own built-in command of the same name.
+keywords:
+  - error
+  - bug
+  - fix
+  - troubleshoot
+  - debug
+  - broken
+  - j-error
+  - polyfill
+examples:
+  - "I'm getting an error"
+  - "help me fix this bug"
+  - "j-error"
+metadata: 
+  prefered_agent: tester
+---
+
+# Error — Guided Troubleshooting
+
+This skill is a literal-directory-name duplicate of `skills/error/`. It exists so that `/j-error` (and `j.j-error`) give a guaranteed-unshadowed way to reach the same flow as `/error`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/error` 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 error` from `skills/error/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
+## Instructions
+
+Ask the following questions to understand the background of the error:
+
+1. Where does the error occur?
+2. What are you trying to do?
+3. What went wrong?
+4. What was the expected outcome?
+
+Then use the answers to investigate and resolve the issue by creating a issue using the /todo skill.

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

@@ -1,10 +1,17 @@
 ---
-name: evaluate
-description: Analyzes example files against a target goal and produces a structured evaluation rapport.
+name: j.evaluate
+description: Polyfill alias of the evaluate skill under a collision-safe directory name. Identical behavior to /evaluate — Analyzes example files against a target goal and produces a structured evaluation rapport. Use when the bare /evaluate form is shadowed by another tool's own built-in command of the same name.
+keywords:
+  - j-evaluate
+  - polyfill
 ---
 
 # Evaluate
 
+This skill is a literal-directory-name duplicate of `skills/evaluate/`. It exists so that `/j-evaluate` (and `j.j-evaluate`) give a guaranteed-unshadowed way to reach the same flow as `/evaluate`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/evaluate` 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 evaluate` from `skills/evaluate/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## Input
 
 Expects a filled `eval_invokation_template.yml` with:

package/skills/j-examplify/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: j.examplify
+description: Polyfill alias of the examplify skill under a collision-safe directory name. Identical behavior to /examplify — Explains concepts, features, use cases, and patterns based on provided context — a description, scenario, code snippet, or file. Use when the user wants to understand what something is, how it works, when to use it, or wants a concrete example. Use when the bare /examplify form is shadowed by another tool's own built-in command of the same name.
+keywords:
+  - examplify
+  - explain
+  - example
+  - how does
+  - understand
+  - j-examplify
+  - polyfill
+examples:
+  - "explain how this works"
+  - "give me an example of X"
+  - "j-examplify"
+---
+
+# Concept Explainer
+
+This skill is a literal-directory-name duplicate of `skills/examplify/`. It exists so that `/j-examplify` (and `j.j-examplify`) give a guaranteed-unshadowed way to reach the same flow as `/examplify`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/examplify` 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 examplify` from `skills/examplify/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
+## Instructions
+
+If the context is unclear or too broad, ask one focused clarifying question before proceeding. Otherwise, infer and proceed.
+
+Explain the concept by covering:
+
+1. **What it is** — a plain-language definition
+2. **Why it exists** — the problem it solves
+3. **How it works** — core mechanics
+4. **When to use it** — and when not to
+5. **Example(s)** — grounded in the user's context; show a before/after when relevant
+
+After delivering the explanation, save a copy to:
+`project/documentation/examples/<concept_and_context>.md`
+
+Derive the filename from the concept + context (lowercased, hyphenated). Tell the user where the file was saved.
+
+## Follow-up
+
+If further discussion reveals new information about the topic — a new use case, correction, or better example — ask the user:
+
+> "That adds something new to what we covered — want me to update the saved file?"
+1. Yes
+2. No
+
+If yes, append the new content under an `## Additional Notes` section. Do not overwrite the original.

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

@@ -1,19 +1,26 @@
 ---
-name: help
-description: List all available skills with a short description of what each one does. Also use this skill when the user wants to know what commands or skills are available in the project.
+name: j.help
+description: Polyfill alias of the help skill under a collision-safe directory name. Identical behavior to /help — List all available skills with a short description of what each one does. Also use this skill when the user wants to know what commands or skills are available in the project. Use when the bare /help form is shadowed by another tool's own built-in command of the same name.
 keywords:
   - help
   - skills
   - commands
   - what can you do
   - list skills
+  - j-help
+  - polyfill
 examples:
   - "what skills are available?"
   - "show me all commands"
+  - "j-help"
 ---
 
 # Help — List Available Skills
 
+This skill is a literal-directory-name duplicate of `skills/help/`. It exists so that `/j-help` (and `j.j-help`) give a guaranteed-unshadowed way to reach the same flow as `/help`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/help` 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 help` from `skills/help/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## Instructions
 
 List all available skills (from the current skill list) with a short description of what each one does. Format the output as a table with columns for the slash command and its description.

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

@@ -1,25 +1,32 @@
 ---
-name: idea
-description: Capture a loosely-defined idea to project/ideas.md — a lightweight, "maybe someday" log with no board or promotion overhead.
+name: j.idea
+description: Polyfill alias of the idea skill under a collision-safe directory name. Identical behavior to /idea — Capture a loosely-defined idea to project/ideas.md — a lightweight, "maybe someday" log with no board or promotion overhead. Use when the bare /idea form is shadowed by another tool's own built-in command of the same name.
 keywords:
   - idea
   - capture idea
   - log idea
   - brain dump
   - maybe someday
+  - j-idea
+  - polyfill
 examples:
   - "capture this as an idea"
   - "log this idea for later"
   - "I have a rough idea I want to jot down"
+  - "j-idea"
 metadata:
   prefered_agent: scrum-master
 ---
 
 # Idea — Lightweight Idea Capture
 
+This skill is a literal-directory-name duplicate of `skills/idea/`. It exists so that `/j-idea` (and `j.j-idea`) give a guaranteed-unshadowed way to reach the same flow as `/idea`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/idea` 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 idea` from `skills/idea/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## Instructions
 
-1. **Ensure `project/ideas.md` exists** — If it doesn't exist, it will be auto-created by `idea_manager.sh` from `skills/idea/assets/idea_template.md` — no manual action needed.
+1. **Ensure `project/ideas.md` exists** — If it doesn't exist, it will be auto-created by `idea_manager.sh` from `skills/j-idea/assets/idea_template.md` — no manual action needed.
 
 2. **Ask the user about the idea:**
    - What's the idea?

package/skills/{idea → j-idea}/assets/idea_handoff_template.md

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

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

@@ -1,10 +1,17 @@
 ---
-name: improve
-description: A skill for analyzing a codebase and producing a structured improvement plan toward a defined goal.
+name: j.improve
+description: Polyfill alias of the improve skill under a collision-safe directory name. Identical behavior to /improve — A skill for analyzing a codebase and producing a structured improvement plan toward a defined goal. Use when the bare /improve form is shadowed by another tool's own built-in command of the same name.
+keywords:
+  - j-improve
+  - polyfill
 ---
 
 # Improve
 
+This skill is a literal-directory-name duplicate of `skills/improve/`. It exists so that `/j-improve` (and `j.j-improve`) give a guaranteed-unshadowed way to reach the same flow as `/improve`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/improve` 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 improve` from `skills/improve/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## Instructions
 
 Before doing anything, check the attached description for an explicit or implicit goal.

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

@@ -1,18 +1,31 @@
 ---
-name: init
-description: Initialize a new project with the standard directory structure, PROJECT_SUMMARY.md, workflow.json, git repo, and gitignore. Follows a defined ordered onboarding sequence. Use when setting up a new or empty project.
+name: j.init
+description: Polyfill alias of the init skill under a collision-safe directory name. Identical behavior to /init — initializes a new project with the standard directory structure, PROJECT_SUMMARY.md, workflow.json, git repo, and gitignore. Use when the built-in "/init" command (e.g. GH Copilot's own init) shadows Jenga's /init alias.
 keywords:
   - init
   - initialize
   - setup
   - new project
   - scaffold
+  - j-init
+  - polyfill
 examples:
   - "initialize a new project"
   - "set up a new workspace"
+  - "j-init"
 ---
 
-# Init — Project Setup
+# J-Init — Project Setup (polyfill alias of Init)
+
+This skill is a literal-directory-name duplicate of `skills/init/`. It exists because
+some host tools/harnesses (e.g. GH Copilot) ship their own built-in command literally
+named `/init`, which can shadow or override Jenga AI's own `/init` alias (Claude Code's
+native skill resolution is a literal-string, directory-name-based match — see
+`docs/skill-authoring.md`'s "Invocation Convention"). `/j-init` (and `j.j-init`) give
+users a guaranteed-unshadowed way to reach the exact same setup flow.
+
+Keep this file's instructions in lockstep with `skills/init/SKILL.md` — any change made
+there should be mirrored here.
 
 ## Instructions
 
@@ -24,7 +37,7 @@ Before asking anything or scaffolding anything, classify the target directory
 (the current directory) by running the detection script:
 
 ```bash
-skills/init/scripts/detect-existing-codebase.sh .
+skills/j-init/scripts/detect-existing-codebase.sh .
 ```
 
 It prints exactly one verdict on stdout:
@@ -97,10 +110,10 @@ of the mechanical work.
 ### 3. Run the scaffold script
 
 `init.sh` is not guaranteed to live at a single fixed path: in a project that
-installed Jenga via npm, it was mirrored to `.claude/skills/init/scripts/`
-(Claude Code) and `.agents/skills/init/scripts/` (Copilot/other agents) by
+installed Jenga via npm, it was mirrored to `.claude/skills/j-init/scripts/`
+(Claude Code) and `.agents/skills/j-init/scripts/` (Copilot/other agents) by
 `postinstall.js`, and neither of those exists yet in this framework's own
-source checkout, where it lives at the bare `skills/init/scripts/` path
+source checkout, where it lives at the bare `skills/j-init/scripts/` path
 instead. This step runs before `CLAUDE.md`/`AGENTS.md` exist, so it cannot
 rely on either file's routing instructions to resolve the path — it must
 locate its own script directly. Execute the init script from the project
@@ -108,7 +121,7 @@ root, passing the choice from step 2:
 
 ```bash
 INIT_SCRIPT=""
-for candidate in .claude/skills/init/scripts/init.sh .agents/skills/init/scripts/init.sh skills/init/scripts/init.sh; do
+for candidate in .claude/skills/j-init/scripts/init.sh .agents/skills/j-init/scripts/init.sh skills/j-init/scripts/init.sh; do
   [[ -f "$candidate" ]] && { INIT_SCRIPT="$candidate"; break; }
 done
 if [[ -z "$INIT_SCRIPT" ]]; then

package/skills/j-init/assets/scope-thresholds_template.json

@@ -0,0 +1,7 @@
+{
+  "threshold_version": 2,
+  "inline_max_files": 3,
+  "inline_max_lines": 75,
+  "story_max_files": 5,
+  "bundle_lock_ttl_minutes": 30
+}

package/skills/j-jbp/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: j.jbp
+description: Polyfill alias of the jbp skill under a collision-safe directory name. Identical behavior to /jbp — Scaffold the project using the JengaBasePlate boilerplate repo template from https://github.com/samwelmunga/JengaBasePlate.git. Use when the bare /jbp form is shadowed by another tool's own built-in command of the same name.
+keywords:
+  - jbp
+  - boilerplate
+  - scaffold
+  - template
+  - jenga base
+  - j-jbp
+  - polyfill
+examples:
+  - "scaffold with JengaBasePlate"
+  - "set up the base template"
+  - "j-jbp"
+---
+
+# JBP — JengaBasePlate Scaffold
+
+This skill is a literal-directory-name duplicate of `skills/jbp/`. It exists so that `/j-jbp` (and `j.j-jbp`) give a guaranteed-unshadowed way to reach the same flow as `/jbp`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/jbp` 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 jbp` from `skills/jbp/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
+## Instructions
+
+Use the following repo as the boilerplate framework for this project:
+
+```
+https://github.com/samwelmunga/JengaBasePlate.git
+```
+
+Clone or pull the template and apply its structure to the current project.

package/skills/j-lgtm/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: j.lgtm
+description: Polyfill alias of the lgtm skill under a collision-safe directory name. Identical behavior to /lgtm — Approve and commit the current work, then continue to the next task. Shortcut that chains /commit followed by /continue. Use when the bare /lgtm form is shadowed by another tool's own built-in command of the same name.
+keywords:
+  - lgtm
+  - approve
+  - looks good
+  - done
+  - commit and continue
+  - j-lgtm
+  - polyfill
+examples:
+  - "lgtm, commit this"
+  - "looks good, move on"
+  - "j-lgtm"
+---
+
+# LGTM — Approve, Commit, and Continue
+
+This skill is a literal-directory-name duplicate of `skills/lgtm/`. It exists so that `/j-lgtm` (and `j.j-lgtm`) give a guaranteed-unshadowed way to reach the same flow as `/lgtm`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/lgtm` 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 lgtm` from `skills/lgtm/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
+## Instructions
+
+1. Invoke the `/commit` skill and wait for it to finish.
+
+2. If the current workflow is part of a `/do` execution, return to that workflow. Otherwise, invoke the `/continue` skill.

package/skills/{pi-plan → j-pi-plan}/SKILL.md

@@ -1,21 +1,28 @@
 ---
-name: pi-plan
-description: Define or expand project Epics in PROJECT_SUMMARY.md. Use this at the start of a project to establish its foundation, AND whenever the user wants to add major new features, plan a significant new area of work, or make epic-level changes to an existing project. Trigger whenever you hear things like "new feature area", "big change", "new epic", "expand the project", "add a major capability", or "plan a new phase" — even mid-project.
+name: j.pi-plan
+description: Polyfill alias of the pi-plan skill under a collision-safe directory name. Identical behavior to /pi-plan — Define or expand project Epics in PROJECT_SUMMARY.md. Use this at the start of a project to establish its foundation, AND whenever the user wants to add major new features, plan a significant new area of work, or make epic-level changes to an existing project. Trigger whenever you hear things like "new feature area", "big change", "new epic", "expand the project", "add a major capability", or "plan a new phase" — even mid-project. Use when the bare /pi-plan form is shadowed by another tool's own built-in command of the same name.
 keywords:
   - epic
   - template
   - expand
   - new feature area
   - project structure
+  - j-pi-plan
+  - polyfill
 examples:
   - "add a new epic for X"
   - "expand the project with a new feature area"
+  - "j-pi-plan"
 metadata: 
   prefered_agent: scrum-master
 ---
 
 # Pi-plan — Define and Expand Project Epics
 
+This skill is a literal-directory-name duplicate of `skills/pi-plan/`. It exists so that `/j-pi-plan` (and `j.j-pi-plan`) give a guaranteed-unshadowed way to reach the same flow as `/pi-plan`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/pi-plan` 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 pi-plan` from `skills/pi-plan/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## When to use this skill
 
 - **New project**: Gather project description and goals, then define the initial set of Epics.
@@ -59,4 +66,4 @@ Story files created under `project/board/stories/` should follow `./assets/story
 
 4. **Define new Epics** — Draft one or more new Epic objects using the same schema as above, then append them to the existing Epics list in `project/PROJECT_SUMMARY.md`. Do not modify existing Epics unless the user explicitly asks.
 
-5. **Confirm before writing** — Show the user the proposed new Epic(s) and get confirmation before updating the file.
+5. **Confirm before writing** — Show the user the proposed new Epic(s) and get confirmation before updating the file.

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

@@ -1,20 +1,27 @@
 ---
-name: proceed
-description: Review project progress by checking epics and stories, optionally consulting PROJECT_SUMMARY.md and WARP.md, then continue executing the project plan.
+name: j.proceed
+description: Polyfill alias of the proceed skill under a collision-safe directory name. Identical behavior to /proceed — Review project progress by checking epics and stories, optionally consulting PROJECT_SUMMARY.md and WARP.md, then continue executing the project plan. Use when the bare /proceed form is shadowed by another tool's own built-in command of the same name.
 keywords:
   - proceed
   - review progress
   - check epics
   - continue executing
+  - j-proceed
+  - polyfill
 examples:
   - "proceed with the plan"
   - "review progress and continue"
+  - "j-proceed"
 metadata:
   prefered_agent: scrum-master
 ---
 
 # Proceed — Resume Project Execution
 
+This skill is a literal-directory-name duplicate of `skills/proceed/`. It exists so that `/j-proceed` (and `j.j-proceed`) give a guaranteed-unshadowed way to reach the same flow as `/proceed`, even if a host tool's own built-in command of the same name would otherwise shadow or override the bare `/proceed` 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 proceed` from `skills/proceed/SKILL.md` — do not hand-edit it; re-run the generator instead to pick up source changes.
+
 ## Instructions
 
 1. **Assess progress** — Read `project/PROJECT_SUMMARY.md`, then check `project/board/epics/`, `project/board/stories/`, and `project/board/tasks/` to determine how far the project has come and what is outstanding.