OpenSpec Feature Workflow
Overview
Use this skill for the OpenSpec half of feature delivery. It creates and completes the change artifacts needed before implementation.
This is an explicit opt-in workflow. Do not use it by default. Only use it when the user explicitly asks for this workflow, names this skill, or a repository policy explicitly requires it.
Workflow
- Derive or confirm a kebab-case change name.
- Create the change under
openspec/changes/<change-name>/. - Run
openspec status --change "<change-name>" --jsonto inspect artifact order. - Read
openspec instructions <artifact> --change "<change-name>" --jsonbefore writing each artifact. - Complete artifacts in dependency order:
proposal.mddesign.mdspecs/.../spec.mdtasks.md
- Re-check status until all apply-required artifacts are done before implementation starts.
When to Use
- The user explicitly asks for proposal/design/tasks before coding
- The user explicitly names
$openspec-feature-workflow AGENTS.mdor team policy explicitly requires this workflow
Artifact Expectations
proposal.md: why and what changeddesign.md: technical approach and trade-offsspecs/.../spec.md: normative requirements and scenariostasks.md: executable implementation checklist
Guardrails
- Do not skip dependency order from
openspec status - Do not copy instruction metadata into artifact files
- Do not start coding until required artifacts are ready


