openspec-workflow

name	OpenSpec Workflow
description	Spec-driven development workflow — proposals, requirements, design docs, task breakdowns, and implementation using the OpenSpec framework. Use when: Starting a new feature or change that needs planning, someone says "I want to build X", creating proposals or specs, breaking down requirements into tasks, or transitioning from planning to implementation. Don't use when: Debugging or troubleshooting (use appropriate troubleshooting skill). Don't use for Kubernetes manifest changes (use pr-workflow). Don't use for reviewing existing code (use code-review). Outputs: OpenSpec change folder with proposal.md, specs/, design.md, and tasks.md. Implementation follows directly from tasks.md.
requires	[]

OpenSpec Skill

Document templates and workflow patterns for spec-driven development.

Routing

Use This Skill When

• Starting a new feature or change that needs planning
• Someone says "I want to build X" or "let's add Y"
• Creating proposals, requirements, or design documents
• Breaking down a feature into implementable tasks
• Transitioning from planning to implementation
• Running /opsx:new, /opsx:ff, /opsx:apply, or /opsx:archive

Don't Use This Skill When

• Debugging a runtime issue -> use the appropriate troubleshooting skill
• Changing Kubernetes manifests -> use pr-workflow (dyson)
• Reviewing a PR -> use code-review
• The task is small enough to just do without a spec -> skip planning

Philosophy

OpenSpec is built on these principles: