Skill Claude CodeCodex
Use when setting up test infrastructure, adding tests, reorganizing test directories, or reviewing test structure. Triggers include creating test files, discussing test strategy, separating unit from integration tests, or when tests need external services like databases or Docker.
Skill Claude CodeCodex
An instruction set for starting and coordinating other coding agents through HCOM, a system for agents to communicate and work together. It covers choosing an agent, giving it a task, monitoring it, and ending the collaboration.
Skill Claude CodeCodex
A coordinator for a multi-stage process in which separate agents discuss requirements, write a specification, create tickets, implement changes, and perform quality checks. It uses handoffs and project records to track the work between stages.
Skill Codex
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Skill Claude CodeCodex
Compact the current conversation into a handoff document for another agent to pick up.
Skill Codex
Implement a piece of work based on a spec or set of tickets.
Skill Codex
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Skill Codex
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Skill Codex
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Skill Codex
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Skill Codex
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Skill Codex
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
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: