mcpField
O
openspec-continue

openspec-continue

github.com/full-stack-skillsAgent workflows188 installsUpdated 4w ago
Repository

About openspec-continue

openspec-continue is an Agent skill for creating OpenSpec change artifacts incrementally, one ready artifact per invocation. It suits workflows where users review and edit proposals, specs, designs, and tasks as they are created.

Key features

  1. 01Check artifact dependency status
  2. 02Identify artifacts ready to create
  3. 03Create one artifact per invocation
  4. 04Show newly unlocked artifacts

Use cases

  1. 01Build OpenSpec change artifacts step by step
  2. 02Review and edit each artifact before continuing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-continue

After installing, type/openspec-continuein Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

OpenSpec Continue Skill

Use /opsx:continue to create the next artifact in the dependency chain. This builds a change incrementally — one artifact at a time — giving the user control to review and edit before proceeding.

When to Use

  • The user wants incremental, step-by-step artifact creation.
  • After creating a change with openspec-new and wanting to build artifacts one at a time.
  • The user says "continue", "next artifact", "create specs", "create design".

Prerequisites

  • An active change exists (created via openspec-new or /opsx:new).

Workflow

  1. Query the dependency graph

    • The agent runs openspec status --change <name> --json to see which artifacts are done, ready, or blocked.

  2. Identify ready artifacts

    • In the default spec-driven schema: proposal -> specs / design -> tasks.
    • Dependencies are enablers: once a dependency is done, its dependents become "ready".

  3. Create one artifact

    • Read dependency files for context.
    • Create the first ready artifact (e.g. proposal, then specs, then design, then tasks).
    • Use openspec instructions <artifact> --change <name> --json to get enriched instructions and templates.

  4. Show what's unlocked

    • After creating an artifact, show what becomes available next.

  5. Repeat

    • User reviews, optionally edits, then runs /opsx:continue again for the next artifact.

Artifact Dependency Graph (spec-driven schema)

proposal (root, no dependencies)
    |
    +---> specs (requires: proposal)
    |
    +---> design (requires: proposal)
            |
            +---> tasks (requires: specs + design)

Outputs

  • One artifact file created per invocation (e.g. proposal.md, specs/**/*.md, design.md, tasks.md).

Next Steps

  • Run /opsx:continue again for the next artifact.
  • When all planning artifacts are done: use openspec-apply to implement tasks.
  • Or use openspec-ff to fast-forward remaining artifacts.

Troubleshooting

  • "No artifacts ready": All artifacts are either complete or blocked. Check openspec status --change <name>.
  • "Change not found": Specify the change name explicitly: /opsx:continue add-dark-mode.

References

Comments

Markdown supported