openspec-continue-change

Automate OpenSpec change artifact creation and dependency management.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Draft-Official/draft-web --skill openspec-continue-change-draft-official
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/Draft-Official/draft-web/tree/main/.claude/skills/openspec-continue-change
Command: npx skills add https://github.com/Draft-Official/draft-web --skill openspec-continue-change-draft-official

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of progressing an OpenSpec change by automating artifact creation and management.

Core Features & Use Cases

  • Workflow Continuation: Enables users to continue developing or refining an OpenSpec change from where they left off.
  • Artifact Management: Automates the creation of specification documents, proposals, design plans, and task breakdowns based on current project status.
  • Use Case: A product team working on a new API can use this Skill to generate structured specifications and task lists incrementally, ensuring consistent progress and documentation.

Quick Start

Use this Skill to continue working on your active change, generate the next artifact, or review current progress.

Frequently Asked Questions about openspec-continue-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate specification document creation for iterative software projects?

Automating specification document creation is handled by reading existing artifacts and guiding you step-by-step to generate the next required proposal, design plan, or task breakdown. This ensures consistent progress and completeness for your iterative development workflow.

What is the best way to continue an OpenSpec change workflow from where I left off?

Continuing an OpenSpec change workflow involves seamlessly progressing your active change by reading current project status. The Skill automates dependency management and artifact creation, allowing you to resume refining specifications incrementally without losing prior context.

Can I manage task breakdowns and design plans incrementally for a new API?

Managing task breakdowns and design plans incrementally is fully supported for new APIs. The Skill generates structured specifications and task lists based on current project status, ensuring product teams maintain consistent documentation and progress throughout the iterative design process.

Do I need existing artifacts to use this workflow automation Skill?

Existing artifacts are required as the Skill reads your current project status to determine the next steps. It relies on previously created specification documents to guide you through the change workflow and automate the generation of subsequent artifacts accurately.

Why does my project workflow require step-by-step guidance for artifact creation?

Step-by-step guidance for artifact creation ensures consistency and completeness across your specification and design processes. By automating dependency management and reading existing artifacts, the Skill prevents structural gaps and maintains strict continuity throughout your iterative software project.

Limitations of automating specification management for active changes?

Automating specification management relies on existing artifacts, meaning it cannot generate initial workflows from scratch. It is specifically designed to continue and refine active changes, requiring a pre-existing project status to determine the correct next artifact and guide the progression accurately.