openspec-continue | partme-ai-full-stack-skills | ClaudePluginHub

Skill

openspec-continue

From partme-ai-full-stack-skills

Creates the next ready artifact (proposal, specs, design, tasks) in an OpenSpec change's dependency graph via /opsx:continue for incremental, reviewable development.

developer-tools

Install

$

npx claudepluginhub partme-ai/full-stack-skills --plugin t2ui-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

168.3k

Stats

Stars328

Forks62

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

artifact-creation

dependency-chain

incremental-change

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

Query the dependency graph
- Run openspec status --change <name> --json to see which artifacts are done, ready, or blocked.
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".
Create one artifact
- Read dependency files for context.
- Run openspec instructions <artifact> --change <name> --json to get enriched instructions and templates.
- Create the first ready artifact (e.g. proposal, then specs, then design, then tasks).
Show what's unlocked
- After creating an artifact, report what becomes available next.
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