OPSX Eight-Stage Problem-Solving Workflow

Combines solve-workflow's eight-stage PDCA discipline with OpenSpec/OPSX artifact persistence. The goal: never let the AI skip analysis, proposal, review, or verification, and never let the key conclusions live only in chat context.

Output templates: see reference.md for each stage's format.

Positioning

Use this skill for engineering changes that are worth persisting: requirements, root cause, behavior changes, technical trade-offs, task lists, and verification results should all be written to openspec/changes/<change-name>/, then merged into openspec/specs/ via archive on completion.

Division of labor:

• OpenSpec: the source of truth and archive system — answers "what, and why".
• solve-workflow-style gates: stage gating — answers "when is it allowed to move to the next step".

Not a replacement for plain solve-workflow:

• Quick fixes, single-file lightweight edits, or tasks needing no long-term traceability — prefer solve-workflow.
• Tasks involving long-term behavioral contracts, team review, concurrent changes, requirement audits, or later traceability — use this skill.