What problem does it solve? Advancing a spec-driven change requires knowing which artifact comes next, what template it follows, and which dependencies to read. This Skill automates that progression by querying the openspec CLI for status and instructions, then creating exactly one artifact per invocation. ## Core Features & Use Cases - Status-Driven Progression: Runs openspec status to determine which artifact is ready, then fetches its instructions and template before writing. - Change Selection: Infers the active change from context, auto-selects when only one exists, or prompts with the most recently modified changes when ambiguous. - Store-Aware Operation: Supports registered OpenSpec stores via --store <id> flags discovered through openspec store list --json. - Use Case: A developer mid-way through a spec-driven change asks to continue; the Skill detects the next ready artifact (e.g., a design doc), reads completed dependencies from disk, writes the artifact to its resolved path, and reports progress. ## Quick Start Ask the assistant to continue working on your current OpenSpec change and create the next artifact.
