Skill Claude CodeCodex
Part of signum
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Risk-adaptive development pipeline with adversarial consensus code review
Skill Claude CodeCodex
Part of signum
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Skill Claude CodeCodex
Part of signum
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Skill Claude CodeCodex
Part of signum
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Skill Claude CodeCodex
Part of signum
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Skill Claude CodeCodex
Part of signum
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Skill Claude CodeCodex
Part of signum
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
Skill Claude CodeCodex
Part of signum
Use when the user wants contract-first development — define correctness before coding, implement against a contract, audit with multiple models, and package proof artifacts.
Skill Claude CodeCodex
Part of signum
Use when the user wants a contract-first implementation workflow, asks to define correctness before coding, wants multi-stage execution with verification and audit, or needs a proof-style artifact for a code change. Codex should run a CONTRACT -> EXECUTE -> AUDIT -> PACK pipeline.
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: