105 tagged OpenSpec, measured the same way as everything else here.
Browse within: architectural-decision-records 31spec-driven-development 31ai-workflow 25c4model 19context-engineering 19git-worktrees 19opencode 19dev-pipeline 15sdd 15compound-engineering 14software-engineering 14Orchestration 13codegen 13aicoding 12
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.
Skill Claude CodeCodex
Review uncommitted or committed changes in the current branch and generate a code review report. Use when the user wants to review their changes before or after committing.
Skill Claude CodeCodex
Preserve change artifacts (proposal, design, tasks) into structured archive and update knowledge base. Final phase of OpenSpec workflow.
Skill Claude CodeCodex
Guide for injecting custom MCP tools, skills, and hook points into the OpenSpec workflow for team-specific processes.
Skill Claude CodeCodex
Create design.md with technical architecture and tasks.md with executable breakdown from an approved proposal. Second phase of OpenSpec workflow.
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.
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.
intent-driven-dev/openspec-schemas
Skill Claude CodeCodex
Archive multiple completed changes at once. Use when archiving several parallel changes.
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: