Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.
Use openspec schema subcommands to create and manage custom workflow schemas. Schemas define what artifacts exist and their dependencies. The default spec-driven schema provides proposal -> specs -> design -> tasks, but custom schemas allow different workflows.
openspec schema which).openspec schema init my-workflow
# Interactive: prompts for description, artifacts, default
# Non-interactive:
openspec schema init rapid --description "Rapid iteration" --artifacts "proposal,tasks" --default
Creates openspec/schemas/my-workflow/ with schema.yaml and templates/.
openspec schema fork spec-driven my-workflow
Copies the spec-driven schema for customization.
openspec schema validate my-workflow
# Or validate all:
openspec schema validate
openspec schema which spec-driven
# Shows: package, project, or user source
openspec schema which --all
openspec/schemas/<name>/
├── schema.yaml # Artifact definitions and dependencies
└── templates/
├── proposal.md # Template for each artifact
├── specs.md
├── design.md
└── tasks.md
name: research-first
artifacts:
- id: research
generates: research.md
requires: []
- id: proposal
generates: proposal.md
requires: [research]
- id: tasks
generates: tasks.md
requires: [proposal]
openspec/schemas/<name>/ (local, version controlled)~/.local/share/openspec/schemas/<name>/ (global)spec-driven)openspec/schemas/<name>/ with schema.yaml and templates./opsx:new my-change --schema my-workflow.openspec/config.yaml).openspec schemas for available schemas; check openspec schema which <name> for resolution.openspec schema validate <name> --verbose for details.openspec schemas --json for artifact IDs per schema.确保开发环境已安装必要的依赖和工具。
根据项目需求进行基础配置。
按照示例代码实现核心功能。
运行测试确保功能正常。
完成开发后进行部署和监控。