القائمة
Check that the intent-driven Codex overlay is compatible with the installed OpenSpec CLI. Use after installing/updating OpenSpec or the template.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
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.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
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.
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.
Use when documenting, drafting, reviewing, or updating ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision history.
| name | openspec-check-overlay |
| description | Check that the intent-driven Codex overlay is compatible with the installed OpenSpec CLI. Use after installing/updating OpenSpec or the template. |
| license | MIT |
| compatibility | Requires OpenSpec CLI 1.3.x or compatible public commands. |
Project context preflight before workflow actions: before this skill takes a workflow action, follow the project-constitution skill. Read root CONSTITUTION.md when present, enforce relevant project rules, stop on material conflicts, and follow the strict missing-constitution bootstrap/diagnostic policy. For architecture-sensitive work, also read ARCHITECTURE.md, adr/README.md, and relevant in-force adr/*.md. Read .secrets.local.env only when the current workflow actually needs a listed external system, and never reveal secret values.
Validate the project-local intent-driven overlay without patching OpenSpec. Prefer scripts/check-overlay when present; otherwise follow the manual steps below.
Show the OpenSpec version:
openspec --version
List schemas and confirm intent-driven is project-local:
openspec schemas --json
Validate the schema:
openspec schema validate intent-driven
List active changes with a command valid in OpenSpec 1.3.x:
openspec list --json
Create a temporary smoke change using the intent-driven schema:
openspec new change zz-smoke-intent-overlay-<unique> --schema intent-driven
openspec status --change zz-smoke-intent-overlay-<unique> --json
# after writing minimal proposal/specs/grill/design/design-review/adr/test-plan/tasks artifacts:
openspec instructions apply --change zz-smoke-intent-overlay-<unique> --json
Report the compatibility layer for any failure:
intent-driven schema invalidCleanup policy:
zz-smoke-intent-overlay-* change that it created in the same run.--keep-smoke when the user wants to inspect the smoke change.openspec status --json; OpenSpec 1.3.x requires --change.openspec/changes/**, openspec/specs/**, or adr/**.