16 skills
The skills
A skill is a written procedure for one situation. The list below is grouped by when you need one, not by what it is made of.
First contact
First contact with an existing codebase: read it before you touch it.
Running the work
The everyday path of a ticket, from dispatch to receipt.
At the gate
Where someone else re-reads before anything moves on.
- codex-armRun a Codex pass over a finished artifact so a different vendor reads the diff before it merges.Gate
- codex-claude-armRun a Claude pass over a finished artifact when the root session runs on Codex.Gate
- dispatch-qa-walkStart the app in its own worktree and let QA use it as a user, before a PR, a merge or a release.Gate
- review-with-rinRun Rin's milestone gate as an observable pane, then classify what she finds.Gate
When the code is old
Code that has lived a while: no tests, no module boundaries.
Keeping it honest
The recurring work that keeps the board and git telling one story.
Same flow, other tooling
The same procedure against a different runtime or a different tracker.
- dispatch-ticket-claudeLaunch, brief and watch a Claude Code pane, in the one order that cannot fake a finished turn.Adapters
- dispatch-ticket-codexLaunch a Codex pane from the owner's machine-local profile, after checking it matches the configured row.Adapters
- dispatch-ticket-opencodeLaunch an OpenCode pane and report which checks of the shared protocol degrade on this runtime.Adapters
- github-issue-trackerDrive GitHub Issues as the harness tracker, with status in labels and the board as a mirror you write.Adapters
- jira-issue-trackerDrive Jira as the harness tracker, where a status is a numbered transition you read before every write.Adapters
- linear-issue-trackerDrive Linear as the harness tracker, and check the tier's issue ceiling before building a pipeline.Adapters