Menu
Create or customize OpenSpec workflow schemas in this repository using `openspec schema init` and `openspec schema fork`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use whenever Codex operates on an OpenSpec change lifecycle or artifact, including propose/new change, apply/implement tasks, archive/finalize, sync specs, continue/update artifacts, validate/status checks, or work under openspec/changes/*. This is the Linear lifecycle overlay for OpenSpec work: bind Linear issues, maintain openspec/linear.yaml, update Linear issue business context/status, keep technical design/tasks in the repo, and mirror canonical specs into Linear Project Documents after archive.
Create or customize OpenSpec workflow schemas in this repository using `openspec schema init` and `openspec schema fork`. Use when the user wants to add, fork, or validate a schema under `openspec/schemas/`.
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
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.
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
| name | openspec-schema-authoring |
| description | Create or customize OpenSpec workflow schemas in this repository using `openspec schema init` and `openspec schema fork`. |
| license | MIT |
| compatibility | Requires openspec CLI. |
| metadata | {"author":"openspec-schemas","version":"1.0"} |
Use this skill when you want to add or customize an OpenSpec workflow schema in this repository.
Goal: produce a copyable schema folder under openspec/schemas/<schema-name>/ containing schema.yaml and templates/.
Steps
Choose whether you're starting fresh or forking
If you want a brand-new workflow schema, use init.
If you want to customize an existing workflow (recommended), use fork.
Discover available schema sources
List schemas available to fork (both this repo and upstream packages):
openspec schemas --json
Option A: Create a new schema from scratch (init)
Create a new project-local schema folder:
openspec schema init <schema-name>
Common flags:
--description "..." to describe the workflow--artifacts "proposal,specs,design,tasks" to set the artifact IDs (comma-separated)--default to set the schema as the project default--no-default to skip the interactive prompt to set as defaultResult (expected): openspec/schemas/<schema-name>/schema.yaml and openspec/schemas/<schema-name>/templates/.
Option B: Customize an existing workflow (fork)
Copy an existing schema into this repo so you can edit it:
openspec schema fork <source> [new-schema-name]
Sources can be:
minimalist, event-driven)spec-driven, tdd)Result (expected): a new folder under openspec/schemas/<new-schema-name>/ containing schema.yaml + templates/.
Edit schema internals (minimal expectations)
When updating openspec/schemas/<schema-name>/schema.yaml and templates, ensure:
artifacts[].id matches the intended workflow sequenceartifacts[].requires matches dependenciesartifacts[].generates matches output paths that templates will createopenspec/schemas/<schema-name>/templates/ for each artifactValidate the schema locally (required quality gate)
Run validation for every schema you changed:
openspec schema validate <schema-name>
Note: some CLI versions mention openspec schema review, but this repo's workflow standardizes on openspec schema validate.
Debug schema resolution (if validation or behavior is surprising)
Confirm which schema folder the CLI is using:
openspec schema which <schema-name>
Guardrails
openspec schema fork over manual copying.openspec/schemas/.openspec schema validate before opening a PR.