Skill Claude CodeCodex
Use before writing Gherkin when exploring a story's behaviour, rules, examples, questions, scope, or readiness with stakeholders.
Skill Claude CodeCodex
Use before writing Gherkin when exploring a story's behaviour, rules, examples, questions, scope, or readiness with stakeholders.
Skill Claude CodeCodex
Use when writing or reviewing Gherkin scenarios, especially after discovering examples or edge cases that reveal a business rule.
Skill Claude CodeCodex
Use when designing event-driven architectures, evaluating aggregate boundaries, deciding between event sourcing and current-state storage, building read models, or when a codebase has overlapping domain objects emitting events.
Skill Claude CodeCodex
Use when a feature feels under-tested, after implementing new functionality, or before a release to discover edge cases, UX issues, and bugs through hands-on CLI exploration.
Skill Claude CodeCodex
Use when multiple independent leaf yaks are ready to implement and can be worked on concurrently with separate agents in worktrees.
Skill Claude CodeCodex
Use when a yak needs requirements, examples, and a plan before implementation - prepares a yak so it's ready for subagent-driven development.
Skill Claude CodeCodex
Use when mutation testing reveals survived mutants — guides deep analysis of whether each mutant signals a missing test, a design improvement opportunity, or an equivalent mutation.
Skill Claude CodeCodex
Use when evaluating the ubiquitous language in a codebase - produces a glossary of domain terms with references and commentary on inconsistencies, awkward names, or overlapping concepts.
Skill Claude CodeCodex
Use when planning work by approaching goals and discovering blockers, before creating comprehensive plans.
Skill Claude CodeCodex
Use when starting work on a yak - sets up an isolated git worktree, reads yak context, and guides the full cycle from claiming through merge and cleanup.
Skill Claude CodeCodex
Use when running yx commands that create, modify, or delete yaks outside of real project work — provides an isolated temp environment.
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: