bristlenose

Start work in an ISOLATED git worktree (the exception path — use only when two envs must be live at once, the work is multi-day and main must stay shippable meanwhile, or it's a throwaway spike). Creates the branch + worktree + venv + frontend build + smoke test + BRANCHES.md entry. For ordinary work, use /new-feature (trunk) instead. Any Kind — captured in Step 3.5. The `--from-cloud` flag instead ADOPTS an existing `origin/claude/*` cloud branch (built on phone/cloud, never compiled): fetch → build the Mac env → run the tests the cloud couldn't → preview the merge against main.

End-of-session ritual — verify, document for humans and robots, commit, close out

Ship a release — bump version, finalise changelog/readme, tag, push, and verify PyPI. The ONLY workflow command that touches public distribution (PyPI, Homebrew, the public changelog, the tag). Evening window on weekdays. Supports --dry-run.

Finish a piece of trunk work on main — runs tests + lint, surfaces human-QA checks, trues docs, adds a changelog line, marks the 100days item done, and commits. No merge (you're already on main). If you're on a branch, it offers to close the branch properly instead.

Archive a merged feature branch — stale marker, detach worktree, update BRANCHES.md (preserves local directory)

Start a piece of work on main (trunk — the DEFAULT path). Loads the plan / 100days item, checks recent history, agrees a plan, and records the task. No branch, no worktree, no env setup. For work that needs an isolated live environment, use /new-branch instead.

Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

Fan out all relevant review agents in parallel against a plan or implementation, then consolidate into a single triageable report

Bidirectional sync between 100days.md and GitHub Projects board — strikethrough Done items, create new cards, backfill Sprint tags

Pre-mortem a dependency-bump set before merging — predict what breaks, prove how, and record the prophecy for later calibration

Situation report — compare planning docs against git delivery over a window, surface lateral wins, and lay out forward candidates respecting dependencies. User picks; skill does not pick.

Reconcile developer-facing design docs in `docs/` and `docs/private/` against shipped reality (code, commits, post-mortem artefacts). Classifies each doc (A/B/C/D/E/P archetypes), then applies per-archetype edits — preserving historical value where it matters, archiving what's truly superseded. Three modes: `--corpus` (whole-tree triage report), `--topic <theme>` (slice reconciliation), `--doc <path>` (single-doc mode). Use after a checkpoint or release, when code has outrun its design docs.

Add a new item to 100days.md and create a matching card on the GitHub Projects board

Critique changed code — find bugs, check conventions, raise design questions