comet-design
25Skill Claude CodeCodex
Comet Phase 2: Deep Design. Invoke with /comet-design. Produce Design Doc and delta spec through brainstorming.
not rated 3.0k
+35 today A SkillSpector: pass 29 tokens
original MIT
3.0kStars on the repository
57Mods indexed here, across every type
todayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
comet-hotfix
26Skill Claude CodeCodex
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
not rated 3.0k
+35 today A SkillSpector: warn 40 tokens
original MIT
comet-open
27Skill Claude CodeCodex
Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).
not rated 3.0k
+35 today A SkillSpector: pass 40 tokens
original MIT
comet-tweak
28Skill Claude CodeCodex
Comet preset path: Non-bug small changes (tweak). Skip brainstorming and full plan, directly open → lightweight build → light verify → archive. Applicable for copy, configuration, documentation or prompt local optimization.
not rated 3.0k
+35 today A SkillSpector: warn 48 tokens
original MIT
comet-verify
29Skill Claude CodeCodex
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
not rated 3.0k
+35 today A SkillSpector: warn 32 tokens
original MIT
comet
30Skill Claude CodeCodex
Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.
not rated 3.0k
+35 today A SkillSpector: warn 44 tokens
original MIT
Skill Claude CodeCodex
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
not rated 3.0k
+35 today A 31 tokens
copy · 88% MIT
Skill Claude CodeCodex
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
not rated 3.0k
+35 today A 31 tokens
copy · 88% MIT
Skill Claude CodeCodex
Archive multiple completed changes at once. Use when archiving several parallel changes.
not rated 3.0k
+35 today A SkillSpector: pass 23 tokens
copy · 77% MIT
Skill Claude CodeCodex
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
not rated 3.0k
+35 today A SkillSpector: pass 39 tokens
copy · 77% MIT
Skill Claude CodeCodex
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.
not rated 3.0k
+35 today A 39 tokens
copy · 92% MIT
Skill Claude CodeCodex
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
not rated 3.0k
+35 today A 34 tokens
copy · 100% MIT
Skill Claude CodeCodex
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
not rated 3.0k
+35 today A 40 tokens
copy · 80% MIT
Skill Claude CodeCodex
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
not rated 3.0k
+35 today A SkillSpector: pass 26 tokens
copy · 73% MIT
Skill Claude CodeCodex
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.
not rated 3.0k
+35 today A SkillSpector: warn 47 tokens
original MIT
Skill Claude CodeCodex
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.
not rated 3.0k
+35 today A 38 tokens
copy · 86% MIT
Skill Claude CodeCodex
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
not rated 3.0k
+35 today A SkillSpector: pass 32 tokens
copy · 80% MIT
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
not rated 3.0k
+35 today A SkillSpector: warn 37 tokens
copy · 77% MIT
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
not rated 3.0k
+35 today A 26 tokens
copy · 95% MIT
Skill Claude CodeCodex
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
not rated 3.0k
+35 today A 22 tokens
copy · 89% MIT
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
not rated 3.0k
+35 today A SkillSpector: warn 44 tokens
original MIT
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
not rated 3.0k
+35 today A 38 tokens
copy · 97% MIT
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
not rated 3.0k
+35 today A 22 tokens
copy · 83% MIT
Skill Claude CodeCodex needs its repo
Use when executing implementation plans with independent tasks in the current session.
not rated 3.0k
+35 today A SkillSpector: warn 17 tokens
original MIT
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: