Local-first, per-repo ticket board + git/PR pipeline: MCP server, guard/telemetry hooks, and a pipeline CLI. Decoupled — each repo owns its own tickets/ + events/.
This repository also configures its own agents. See what ticket-workflow tells them →
Skill Claude CodeCodex
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Skill Claude CodeCodex
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Skill Claude Code
Compact the current conversation into a handoff document for another agent to pick up.
Skill Claude CodeCodex
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Skill Claude CodeCodex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Skill Claude Code
Implement one sliced ticket end to end — premise check, worktree, red→green at the agreed seams, two-axis fresh-context review, mutation check, PR, and qa. Invoke explicitly with a ticket id. Never merges.
Skill Claude Code
Slice a merged spec into vertical child tickets under its spec ticket — blocking edges, agreed test seams and an autonomy label each — after one human approval. Invoke explicitly with the spec ticket's id. Never implements.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: