What problem does it solve? Starting a structured spec-driven change requires knowing the correct openspec CLI commands, schema selection, and artifact workflow order, which is error-prone when done manually. ## Core Features & Use Cases - Change Scaffolding: Creates a new kebab-case change directory using openspec new change with optional schema selection. - Artifact Status Inspection: Runs openspec status and openspec instructions to show the artifact sequence and the template for the first ready artifact. - Store-Aware Operation: Discovers registered OpenSpec stores with openspec store list --json and applies a sticky --store <id> flag to all scoped commands. - Use Case: A developer wants to add user authentication to a project; the skill derives the name add-user-auth, scaffolds the change, and presents the proposal template without writing any artifacts. ## Quick Start Ask the assistant to start a new OpenSpec change for the feature or fix you want to build, and it will scaffold the change and show the first artifact template.