Skip to content
v0.1.0MIT

One person's stack for running a repo's tasks as agent threads under T3 Code: a home plans and briefs, a crewmate does one task and opens its pull request, a reviewer reviews it, and jbus and jmerge do the routine work.

why

Use for /why, 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Finds the MCP servers this session has and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

Read SKILL.md at the source

Pinned to revision e0f7be0bfb85, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.