anionDevelopment
Official@anionDevelopment
anionDevelopment provides OpenSpec change-management skills and repository-convention knowledge for spec-driven development of the GRYLibrary codebase.
Agent Skills by anionDevelopment
Showing 9 vetted skills indexed across 2 GitHub repositories.
anionDevelopmentopenspec-apply-change
Implements tasks from an OpenSpec change using the openspec CLI workflow.
anionDevelopmentopenspec-explore
Explores ideas and clarifies requirements through OpenSpec change artifacts and codebase investigation.
anionDevelopmentopenspec-update-change
Revises existing OpenSpec change planning artifacts and reconciles them for coherence.
anionDevelopmentopenspec-archive-change
Archives completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.
anionDevelopmentopenspec-propose
Generates complete OpenSpec change proposals with specs, design, and tasks artifacts.
anionDevelopmentopenspec-sync-specs
Merge delta spec changes into main OpenSpec capability specifications.
anionDevelopmentproduct-knowledge
Explains GRYLibrary structure, API server components, and build verification workflows.
anionDevelopmentwork-with-common-project-structure
Explains the common project structure conventions for organizing codeunits and build pipelines.
anionDevelopmentautomation-using-scriptcollection
Documents ScriptCollection commands for building, testing, and releasing common-project-structure repositories.
Frequently Asked Questions About anionDevelopment
FAQPage SchemaWhat tasks can I perform using anionDevelopment's skills?▼
You can propose new OpenSpec changes with full design, spec, and task artifacts, explore ideas and clarify requirements, implement change tasks, revise planning artifacts, sync delta specs into main specs, and archive completed changes. Additional skills document GRYLibrary structure and ScriptCollection conventions.
Who should use these OpenSpec skills?▼
Developers practicing spec-driven development who plan changes before coding. They suit engineers working in repositories using OpenSpec change workflows, plus contributors to GRYLibrary or projects following the common project structure who need guidance on where code belongs and how to verify changes.
How do I run these skills in practice?▼
The OpenSpec skills invoke Bash commands scoped to openspec:*, so the openspec CLI must be installed and available in your environment. Once installed, each skill triggers on intent: proposing, exploring, implementing, updating, syncing, or archiving a change.
Are these skills free and open source?▼
Yes. All seven OpenSpec skills are released under the MIT license, permitting free use, modification, and redistribution. The product-knowledge, common-project-structure, and ScriptCollection skills are informational repository-convention documents with no stated license restrictions in their frontmatter.
What prerequisites do these skills require?▼
The seven OpenSpec skills require the openspec CLI, as stated in their compatibility field, and run only Bash(openspec:*) commands. The informational skills require no runtime dependencies; they simply provide context on GRYLibrary structure, common project conventions, and ScriptCollection usage.