creevey
Official@creevey
Creevey provides OpenSpec change-management skills covering proposal, exploration, implementation, verification, updating, archiving, and spec synchronization for specification-driven development.
Agent Skills by creevey
Showing 7 vetted skills indexed across 1 GitHub repositories.
openspec-apply-change
Implements tasks from an OpenSpec change using the openspec CLI workflow.
openspec-explore
Explores ideas, investigates codebases, and clarifies requirements before creating OpenSpec change proposals.
openspec-verify-change
Verify implementation matches OpenSpec change artifacts before archiving.
openspec-update-change
Revise OpenSpec change planning artifacts and reconcile them for coherence.
openspec-archive-change
Archives completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.
openspec-propose
Generates complete OpenSpec change proposals with specs, design, and task artifacts.
openspec-sync-specs
Merge delta spec changes into main OpenSpec capability specifications.
Frequently Asked Questions About creevey
FAQPage SchemaWhat tasks can I perform with creevey's OpenSpec skills?▼
You can propose new changes with full design, spec, and task artifacts, explore ideas and clarify requirements, implement change tasks, update planning artifacts, verify implementations against change artifacts, archive completed changes, and sync delta specs into main specs.
Who are these OpenSpec skills designed for?▼
They target software engineers and technical leads practicing specification-driven development who need structured change proposals, requirement clarification, implementation tracking, and spec synchronization across a project's change lifecycle.
What is required to run these skills?▼
Every skill requires the openspec CLI to be installed, as each skill's allowed-tools configuration invokes Bash(openspec:*) commands. There are no other stated dependencies beyond the openspec command-line environment.
Are creevey's OpenSpec skills free to use?▼
Yes. All seven skills are released under the MIT license, permitting free use, modification, and distribution. They are authored by openspec at version 1.0.
How do the skills fit together in a change lifecycle?▼
Start with openspec-propose or openspec-explore to define a change, implement with openspec-apply-change, revise plans via openspec-update-change, validate with openspec-verify-change, then finalize using openspec-archive-change or openspec-sync-specs.