Skip to content

v4.0.0

Choose a tag to compare

View all tags
@kyle-chalmers kyle-chalmers released this 02 Sep 14:30
· 12 commits to main since this release
v4.0.0
ccca806
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[4.0.0] — 2026-09-02

Breaking: /productize is now /skillify, and templates/productized-skill/ is now
templates/generated-skill/. There is no alias — the old name is gone, and an older install's
retired skill directory is warned about rather than deleted. Everything else in this release is
additive: /setup scaffolds a human-facing README, writes stack.yaml first and resumes a
half-configured repo cleanly, and every rebuild hint names the plugin, pip and vendored routes.

Changed

  • /productize is now /skillify; templates/productized-skill/ is now templates/generated-skill/.
    The policy that drives the skill has always been called skillify_everything, so the command name
    was the odd one out — and "productize" carried a product-shipping connotation the skill never had:
    it turns a repeated workflow into a skill, it does not ship a product. The skill directory
    (.claude/skills/skillify/), its name: frontmatter, the skeleton it stamps from, and the
    adjective in prose ("productized skill" → "generated skill") all move together. There is no
    backwards-compatible alias     — the old name is gone. Note that templates/AGENTS.md.tmpl was
    already rendered into existing repos naming /productize, and /refresh does not re-render
    AGENTS.md: an existing repo needs /setup role re-run, or that one line edited by hand. See
    docs/troubleshooting.md for the rename map.

Added

  • /setup now scaffolds a human-facing README.md. Setup wrote AGENTS.md (the agent's rules
    file) but nothing a person landing on the repo could read in a minute. It now also renders a short
    intro (under 250 words of prose) — what this is (a ticket-driven work repo) and how work moves
    through it — from the new templates/project-README.md.tmpl. It's tool-agnostic (only {{repo_name}}
    and {{domain}} tokens) and never overwrites an existing README: if one is present (fresh or
    adopt), it renders README.ticketwright.md for the human to merge, mirroring the AGENTS.ticketwright.md
    convention. Written once, then human-owned — /setup role does not re-render it.

Fixed

  • /setup writes stack.yaml first and stops cleanly when the runtime refuses it. Phase 3 used
    to compose .claude/config/stack.yaml and the scaffold in one sweep. On a brand-new empty repo
    under a headless run whose runtime refuses every write beneath .claude/ (a categorical path guard
    no allow rule lifts non-interactively), setup had already written AGENTS.md, CLAUDE.md,
    README.md, .gitignore, people/*.yaml, the AI-layer index and the seeded ticket index before
    the refusal landed — leaving an AGENTS.md that describes a stack absent from disk and no source
    of truth. The order is now stack.yaml → .claude/settings.json → the derived scaffold (which
    renders FROM stack.yaml), and a refused stack.yaml write halts the whole scaffold and reports
    the refusal text, the cause, and the two ways forward (approve the prompt interactively, or
    hand-create the .claude/ files from the printed plan); everything else is written on the next
    confirm, and a re-run that finds stack.yaml without AGENTS.md resumes the scaffold instead of
    offering an edit — that route is checked before the Bootstrap route (a hand-created recovery has no
    people/ yet), and it first writes whatever of .claude/ is still missing (settings.json, the
    round-1 machine pin) before rendering. scaffold.md also now says to allow a CLI's named read verbs (jobs list,
    jobs get, current-user me, api get), never the bare CLI.
  • The generated tickets/INDEX.md and OBJECTS.md headers no longer point plugin users at a script
    that isn't there.     Both headers said "Re-run python3 bin/build_ticket_index.py". On a plugin install
    the repo has no bin/ (the engines live in the plugin cache and the skills resolve them), so a fresh
    plugin user following the hint got "No such file or directory". The hint now names the skill first —
    /refresh index (/ticketwright:refresh index on a plugin install) — then ticketwright index for pip
    installs, and the script path only for vendored repos; the --prune/--check messages and
    docs/ticket-index.md / docs/troubleshooting.md carry the same three routes. Selftest section 10 pins the new header on both files.

Docs

  • README: headless / agent-driven setup. A new Track 1 subsection says plainly that /setup under
    claude -p is a two-turn flow — the plan turn halts at the confirm gate by design, and the confirm
    is a second turn with --continue — and that a non-interactive runtime refuses every write under
    .claude/ (a categorical sensitive-file guard no allow rule lifts), so stack.yaml,
    settings.json, statusline.sh and the two gitignored *.local.yaml records need an interactive
    approval or a person writing them from the printed plan, while everything outside .claude/
    scaffolds headlessly. It names --strict-mcp-config as the way to keep MCP out of a headless run.
  • README: install-block accuracy. The Track 1 install note now says that on a machine that already
    knows a ticketwright marketplace, marketplace add … --scope project prints "already on disk —
    declared in project settings" — expected, not an error. The finished-file example notes that the
    owner/repo shorthand writes {"source": "github", "repo": …} where the https://…git form writes
    {"source": "git", "url": …}; both are valid, and setup's merge keeps whichever exists.
Assets 2
Loading