intent-driven-dev/openspec-schemas
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 92 18d ago A 31 tokens
MIT
92Stars on the repository
32Mods indexed here, across every type
18d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
intent-driven-dev/openspec-schemas
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 92 18d ago A 31 tokens
MIT
intent-driven-dev/openspec-schemas
Skill Claude CodeCodex
Archive multiple completed changes at once. Use when archiving several parallel changes.
not rated 92 18d ago A 23 tokens
MIT
intent-driven-dev/openspec-schemas
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 92 18d ago A 39 tokens
MIT
intent-driven-dev/openspec-schemas
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 92 18d ago A 39 tokens
MIT
intent-driven-dev/openspec-schemas
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 92 18d ago A 40 tokens
MIT
intent-driven-dev/openspec-schemas
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 92 18d ago A 47 tokens
MIT
intent-driven-dev/openspec-schemas
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 92 18d ago A 38 tokens
MIT
intent-driven-dev/openspec-schemas
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 92 18d ago A 32 tokens
MIT
intent-driven-dev/openspec-schemas
Skill Claude CodeCodex
Use whenever Codex operates on an OpenSpec change lifecycle or artifact, including propose/new change, apply/implement tasks, archive/finalize, sync specs, continue/update artifacts, validate/status checks, or work under openspec/changes/. This is the Linear lifecycle overlay for OpenSpec work: bind Linear issues…
not rated 92 18d ago A 101 tokens
MIT
intent-driven-dev/openspec-schemas
Skill Claude CodeCodex
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork. Use when the user wants to add, fork, or validate a schema under openspec/schemas/.
not rated 92 18d ago A 52 tokens
MIT
intent-driven-dev/openspec-schemas
Skill Claude CodeCodex
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
not rated 92 18d ago A 30 tokens
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: