메뉴
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/`.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
Create or customize OpenSpec workflow schemas in this repository using `openspec schema init` and `openspec schema fork`.
| name | openspec-schema-authoring |
| description | 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/`. |
| license | MIT |
| compatibility | Requires openspec CLI. |
| metadata | {"author":"openspec","version":"1.0","generatedBy":"1.0.0"} |
Create or customize an OpenSpec workflow schema in this repository.
Goal: produce a repository-local schema folder under openspec/schemas/<schema-name>/ containing schema.yaml and templates/.
Steps
Decide whether to initialize or fork
init for a brand-new schema.fork to customize an existing schema (preferred when starting from a known workflow).Discover available schemas to fork
openspec schemas --json
Option A: Initialize a new schema
openspec schema init <schema-name>
Common flags:
--description "..." to describe the workflow--artifacts "proposal,specs,design,tasks" to set artifact IDs--default to set as project default--no-default to skip the interactive default promptExpected result: openspec/schemas/<schema-name>/schema.yaml and openspec/schemas/<schema-name>/templates/.
Option B: Fork an existing schema
openspec schema fork <source> [new-schema-name]
Sources can be:
Expected result: openspec/schemas/<new-schema-name>/schema.yaml and openspec/schemas/<new-schema-name>/templates/.
Edit schema internals
Ensure:
artifacts[].id matches intended workflow sequenceartifacts[].requires matches dependenciesartifacts[].generates matches artifact output pathsopenspec/schemas/<schema-name>/templates/ for each artifactValidate changed schemas (required)
openspec schema validate <schema-name>
This is the supported schema quality gate for OpenSpec CLI 1.3.1. Do not
use openspec schema review; that command is not available in this CLI.
Debug schema resolution if behavior is unexpected
openspec schema which <schema-name>
Done Criteria
openspec/schemas/<schema-name>/.schema.yaml and templates/ are both present.openspec schema validate <schema-name> passes.Guardrails
openspec schema fork over manual copying.openspec/schemas/.