Repo-local vaults
Your booping artifacts — plans, sprints.md, retros, lessons, project extensions — no longer have to live under ~/Claude/{project}/. They can now sit inside the repo instead.
- Opt in at setup:
/installnow asks where you want the vault. Pick the repo-local option and it scaffolds the vault in-tree and wires the repo to use it. - Branch offer on local vaults: when the vault lives in the repo working tree,
/groomoffers to create a branch for the plan before drafting it, so plan files and code changes land together.
Faster plan transitions
Moving a plan between statuses used to be the LLM's job — it set the status, stamped dates, snapshotted the commit, re-rendered sprints.md, and committed the vault by hand, one tool call at a time. That could take a couple of minutes per move.
Those moves now run through a deterministic state machine: the model only decides which transition to make, and a hook script applies every mechanical side effect atomically. Status changes are near-instant and can't drift — no more waiting on the LLM to remember to commit or update frontmatter.
summary replaces business_goal
The old business_goal plan field — an inaccurate, AI-guessed value — is gone, replaced by summary: a bounded, single-line statement of plan intent. /groom now writes it, and it shows up as a new column in sprints.md. Existing plans keep loading; re-groom or edit frontmatter to add a summary.
Other changes
/installfix: project extension stubs are no longer seeded for every skill when the project signal isCLAUDE.md— extra instructions are only seeded for the non-CLAUDE.mdsignal.- Docs sweep: correctness fixes vs v0.1.5, homepage information architecture + README freshness, local-vault documentation.
- Added CI (lint, typecheck, tests on push and PR).
See PR #14 for the full diff.