**Triathlon Agent Developer Guide**: Rules and context for developing the triathlon-agent bot. MANDATORY: use this skill for ANY work on project code. Triggers: code, bug, feature, refactor, test, migration, deploy, MCP tool, actor, ORM, API endpoint, webapp, React, Docker, PR, commit, branch, pipeline, CI, worker, scheduler, Dramatiq, Redis, Intervals.icu, alembic, FastAPI, poetry. Also triggers when MCP triathlon is connected and when discussing project architecture, performance, or infrastructure.
Disciplined workflow for moving a `docs/*_SPEC.md` forward — forces audit → phased plan → confirmation gate → implementation. Triggers when the user invokes `/spec`, `/spec <path>`, or `/spec <path> phase=<N>`. Use this instead of jumping straight into implementation when the user references a spec document. Without arguments: list all specs with phase-status snapshot (which phases done / pending / in-progress). With a spec path: audit existing implementation in code → present phase plan from the spec → identify the first incomplete phase → propose its scope as a punch-list → **STOP and ask user for explicit OK before writing any code**. Mandatory stop point: never start implementing before the user confirms. Even if the punch-list seems obvious. The forced gate is the whole point — `/spec` exists because plain "implement WEBHOOK_DATA_CAPTURE Phase 1" loses the audit step.
Close GitHub issues with a structured comment (What was done, How to verify). Use after fixing a bug or completing a task linked to a GitHub issue.