القائمة
Use when working with OpenSpec in Hermes: customize OpenSpec project config, rules, templates, and schemas.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when working with OpenSpec in Hermes: implement tasks from an OpenSpec change and keep task checkboxes updated.
Use when working with OpenSpec in Hermes: archive one completed change, optionally syncing specs first.
Use when working with OpenSpec in Hermes: archive multiple completed changes and handle spec conflicts.
Use when working with OpenSpec in Hermes: manage OpenSpec CLI setup, validation, browsing, workspaces, context stores, initiatives, and shell integration.
Use when working with OpenSpec in Hermes: create the next ready artifact based on the schema dependency graph.
Use when working with OpenSpec in Hermes: run the expanded OpenSpec scaffold, fast-forward, apply, verify, and optional archive workflow end to end.
| name | openspec-customize |
| description | Use when working with OpenSpec in Hermes: customize OpenSpec project config, rules, templates, and schemas. |
| version | 1.0.0 |
| author | TheSmuks + Hermes Agent |
| license | MIT |
| platforms | ["windows","macos","linux"] |
| metadata | {"hermes":{"category":"software-development","tags":["openspec","sdd","spec-driven-development","hermes"],"homepage":"https://github.com/Fission-AI/openspec"}} |
Use when the user wants custom OpenSpec behavior, schemas, templates, artifact rules, or project context.
Ensure the OpenSpec CLI exists with openspec --version. If missing, install it with npm install -g @fission-ai/openspec@latest.
Edit openspec/config.yaml:
schema: spec-driven
context: |
Tech stack: ...
Conventions: ...
rules:
proposal:
- Include rollback plan
specs:
- Use Given/When/Then scenarios
Context applies to all artifacts. Rules apply only to the matching artifact.
openspec schema init <name> --description "..." --artifacts "proposal,specs,design,tasks" --defaultopenspec schema fork spec-driven <name>openspec schema validate <name>openspec schema which <name> or openspec schema which --all --jsonProject schemas live in openspec/schemas/<name>/ and are version-controlled. Always validate schemas and run a sample status/instructions check before saying customization is ready.