openspec-continue-change

Identifies and guides the next OpenSpec artifact in the schema order.

1|Updated Nov 3, 2023
One-click install
npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-continue-change-luifertorres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-continue-change
Source: https://github.com/luifertorres/trading-assistant/tree/main/.cursor/skills/openspec-continue-change
Command: npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-continue-change-luifertorres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Continue working on an OpenSpec change by creating the next artifact, reducing manual steps and keeping the workflow aligned with the canonical schema.

Core Features & Use Cases

  • Guides users through the OpenSpec artifact sequence according to the chosen schema.
  • Reads current change status and prompts for input when needed.
  • Generates the appropriate artifact using the CLI output, templates, and constraints.

Quick Start

Ask me to continue an OpenSpec change and I will generate the next artifact according to the defined workflow.

Frequently Asked Questions about openspec-continue-change

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

FAQPage Schema
How do I continue an OpenSpec change workflow and generate the next artifact?

To continue an OpenSpec change, this skill reads your current change status and guides you to create the next artifact in the defined schema order. It uses CLI output and templates to produce the required artifact while respecting dependencies.

What is the canonical artifact sequence in OpenSpec change management?

The canonical artifact sequence in OpenSpec defines a step-by-step evolution for changes, ensuring artifact dependencies are respected. This skill identifies your current position in that schema and prompts for input to generate the next valid artifact.

How do I use CLI output and templates to produce OpenSpec artifacts?

You use CLI output and generated templates to produce OpenSpec artifacts by following the guided instructions this skill provides. It reads the current workflow state and applies constraints from the CLI to format the next artifact correctly.

Do I need an existing OpenSpec change to use this workflow automation?

Yes, you need an ongoing OpenSpec change. This skill applies to existing workflows where changes evolve step-by-step, reading the current change status to determine and generate the next artifact in the sequence.

Why does my OpenSpec change workflow require respecting artifact dependencies?

OpenSpec change workflows require respecting artifact dependencies to maintain canonical schema alignment. This skill enforces these dependencies by identifying the current change status and only generating the next valid artifact in the defined sequence.

What is the best way to automate OpenSpec change management steps?

The best way to automate OpenSpec change management steps is using this skill to reduce manual actions. It reads your workflow status, prompts for necessary input, and generates the next artifact using CLI constraints and templates.