extension.install_notesinextension.yml— afterspecify extension add, Specify prints this note when using aspecify-clibuild that supportsinstall_notes(see upstream spec-kit). Reminds you to optionally disable the Git extension’sbefore_specifyhook for parallel worktrees; full.specify/extensions.ymlsnippet remains in the README
- README section Parallel agents and the Git extension: manual
.specify/extensions.ymlchange to disable Git’sbefore_specifyhook when you need a stable primary checkout; branch base--base-ref HEAD; honest note onafter_specifyordering vs running specify from the worktree root - Command doc prerequisites: Git extension vs
gitCLI, and corrected branch-creation rule (worktree can create the branch withgit worktree add -b)
- Documentation-only release aligned with Spec Kit maintainer guidance: no cross-extension hook mutation on install; optional future preset for worktree-first command overrides called out in README
modifies_hooksintegration (revert of PR #1). The extension no longer disables the git extension’sbefore_specify → speckit.git.featurehook on install. If you rely on a stable primary branch with parallel worktrees, disable or adjust that hook manually in your Spec Kit config.
- Default layout switched from
siblingtonested— worktrees now created at.worktrees/<branch>/inside the repo by default - Sibling layout (
../<repo>--<branch>) remains available vialayout: "sibling"in config
post_installlifecycle script — adds.worktrees/to.gitignoreat install time (not just at first worktree creation)- README section "How worktrees stay isolated" documenting gitignore + commit isolation model
speckit.worktrees.createcommand — spawn isolated worktrees with configurable layoutspeckit.worktrees.listcommand — dashboard of all active worktrees with spec-artifact and task progressspeckit.worktrees.cleancommand — safe cleanup of merged, orphaned, or stale worktreesafter_specifyhook — auto-creates worktree after feature specification (configurable)- Two layout modes: sibling (
../<repo>--<branch>) and nested (.worktrees/<branch>/) - Bash script
create-worktree.shfor deterministic worktree creation with JSON output - Per-repo configuration via
worktree-config.yml SPECIFY_WORKTREE_PATHenvironment variable for path overrides--in-place/--no-worktreeopt-out for single-agent flows