OpenSpec Change Planning from *.plan.md

Guide the process of turning an implementation plan (*.plan.md) into an OpenSpec change workflow. This is an interactive SKILL. It verifies CLI availability, initializes OpenSpec when needed, and then creates or updates a change with proposal, design, tasks, and spec deltas.

What is covered in this Skill?

• Input analysis from *.plan.md (scope, change-id candidate, affected capabilities)
• Installation and availability checks for OpenSpec CLI
• Recommended installation paths on macOS, Linux, and Windows using npm
• OpenSpec project bootstrapping with openspec init
• Existing-project workflow using openspec list, openspec status, openspec show
• Validation and completion flow with openspec validate --all and openspec archive
• Example-root workflow at examples/requirements-examples/problem1/requirements/openspec

Constraints

Always execute OpenSpec commands from the parent directory that contains the openspec/ folder. Do not invent requirements not present in the *.plan.md; convert plan intent into explicit OpenSpec change artifacts.