openspec-continue-change

Generate the next OpenSpec change artifact from a schema-driven template.

4|3|Updated Jan 16, 2023
One-click install
npx skills add https://github.com/sgiath/secp256k1 --skill openspec-continue-change-sgiath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/sgiath/secp256k1/tree/main/.opencode/skills/openspec-continue-change
Command: npx skills add https://github.com/sgiath/secp256k1 --skill openspec-continue-change-sgiath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams keep OpenSpec changes flowing by automatically generating the next artifact in the change workflow, reducing manual overhead and ensuring consistency.

Core Features & Use Cases

  • Automates the transition to the next artifact by evaluating the change status and selecting the next pending artifact.
  • Integrates with the OpenSpec CLI to fetch instructions and generate artifact files based on a template.
  • Enforces dependency awareness by reading completed artifacts before creation and by applying contextual constraints (without exposing them in the artifact).

Quick Start

Tell me which OpenSpec change to continue, and I will generate the next artifact file using the approved template.

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 the next artifact creation in an OpenSpec change workflow?

Automating OpenSpec change workflows involves evaluating the current change status to identify ready-to-create artifacts and applying schema-driven templates to generate the next artifact file automatically.

What is the process for continuing an OpenSpec change to the next artifact?

Continuing an OpenSpec change requires reading completed artifacts for dependency awareness, selecting the next pending artifact, and generating the file using an approved template without exposing contextual rules.

How do OpenSpec change workflows handle dependency awareness when generating artifacts?

OpenSpec artifact generation enforces dependency awareness by reading completed artifacts before creation and applying contextual constraints internally, ensuring generated files exclude contextual rules from the final output.

Does the OpenSpec CLI need to be installed to generate artifact files from templates?

Generating OpenSpec artifact files based on templates integrates with the OpenSpec CLI to fetch instructions, requiring the CLI environment to evaluate change status and apply schema-driven templates properly.

Can I exclude contextual rules from generated OpenSpec artifact files?

Excluding contextual rules from generated OpenSpec artifact files is enforced automatically during creation, applying constraints internally while ensuring the final artifact file remains clean and schema-driven.