Skill Claude CodeCodex
Plan and implement non-trivial work with a fixed workflow - explore, plan, confirm, implement, validate, review, update docs. Use after write-spec, for direct implementation tasks, bug fixes, or refactors that need a plan.
Skill Claude CodeCodex
Explore an idea and close every material decision in guided, review, or autonomous mode. Use before writing a spec or plan, when requirements are unclear, when the user wants to brainstorm a feature, stress-test a design, or says "grill me".
Skill Claude CodeCodex
Decide whether a demand is one task or several, and write tasks.md when it is split. Use after brainstorm or write-spec and before write-plan, or when the user asks how to break down a feature, epic, or technical change.
Skill Claude CodeCodex
Entry point for every new task. Classify the request, choose the mode (guided, review, autonomous) and the skill path (brainstorm, write-spec, split-tasks, write-plan, write-flows), then start it. Use when the user starts a new task, reports a bug, asks for a feature or change, or changes topic.
Skill Claude CodeCodex
Document how an existing use case, capability, or codebase initiative works as short Mermaid diagrams plus a list of code entry points, in .flows.md. Use after implementing a feature, when documenting an existing feature, or when a flow, state model, or interaction is easier to understand as a diagram.
Skill Claude CodeCodex
Write a concise behavior-first spec for a use case, actor, domain rules, or cross-domain capability under .docs/. Use when writing or reviewing a spec, user story, use case, actor, business rules, or acceptance criteria before implementation.
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: