Apply three lenses to one problem in a fixed order — recon (what is actually there), debug-mantra (is what I believe actually true), ponytail (what is the smallest thing that works) — with an explicit rule for how much evidence to buy before shrinking. Use when a task tempts you toward opposite errors at once…
Install the full swarm stack into a target repo: vendor the XYZ harness (relay/marathon/consult/self-improve + tick) into /.xyz/, then optionally install the PDDA doc-governance runtime (PROJECT/PDDA.md + utils/pdda/.sh). Both installers self-locate, are idempotent, and register the target into their own per-user…
Give a git repo a stable, distinct VS Code background tint so windows are tellable apart at a glance. The color is scoped to the workspace (.vscode/settings.json under workbench.colorCustomizations), so it applies every session with no per-session step. Two modes: deterministic (SHA-256 of the repo's GitHub slug -> a…
Summarize what shipped to main over the last week as a concise, human- sounding end-user report. Use when the user wants "this week's shipped improvements", "top things that landed", or a weekly release-style recap from git history, especially when they want the answer framed around everyday user impact instead of…
Coordinate two (or more) AI coding agents working CONCURRENTLY on non-overlapping, path-scoped lanes of ONE shared repo, via the tick CLI — for parallel builds and parallel codebase recon, with collision-free claims, liveness heartbeats, and an honest concurrency metric. Use when the user wants to "run two agents in…