Skill Claude CodeCodex
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Skill Claude CodeCodex
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (a domain glossary and ADRs under .context/) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Skill Claude CodeCodex
Find deepening opportunities in a codebase, informed by the domain language in .context/ and the decisions in .context/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Skill Claude CodeCodex
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine…
Skill Claude CodeCodex
Break a plan, spec, or PRD into independently-grabbable iudex tickets using tracer-bullet vertical slices, and register them in the iudex queue with their dependencies. Use when the user wants to convert a plan into tickets, create implementation tickets, or break down work into the iudex queue.
Skill Claude CodeCodex
Turn the current conversation context into a PRD and write it to .context/prd/ so it can be sliced into iudex tickets. Use when the user wants to create a PRD from the current context.
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: