CtrlK
BlogDocsLog inGet started
Tessl Logo

openspec-continue-change

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly structured orchestration workflow with executable commands, clear sequencing, and verification checkpoints. Minor verbosity in the Store-selection and guardrail sections is the only drag on conciseness.

Suggestions

Tighten the Store-selection paragraph into a shorter rule (one sentence + the flag list) to trim repeated explanation.

Consolidate the duplicated "context and rules are constraints, not content" guidance into a single Guardrails bullet instead of restating it inline.

DimensionReasoningScore

Conciseness

It assumes Claude's competence and gives concrete commands with no concept-explaining fluff, but the Store-selection paragraph and repeated context/rules guardrail re-statements add some verbosity that could be tightened.

2.5 / 3

Actionability

It provides concrete executable commands (e.g. `openspec status --change "<name>" --json`, `openspec instructions <artifact-id> ...`) with specific JSON fields to parse and exact behaviors, making guidance copy-paste ready.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with explicit status-based branches, a validation checkpoint (verify the artifact file exists before marking progress), a re-read-from-disk guardrail, and a STOP-after-one control.

3 / 3

Progressive Disclosure

The skill is a single well-organized SKILL.md with no bundle files and clearly signaled sections (Steps, Output, Guidelines, Guardrails); per the simple-skill note this warrants a 3.

3 / 3

Total

11.5

/

12

Passed

Description

95%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states both what the skill does and when to use it, with natural trigger phrasing and a distinct niche. The only soft spot is specificity, where the action vocabulary is somewhat limited (create/progress/continue).

DimensionReasoningScore

Specificity

"creating the next artifact" names a concrete action in a specific domain (OpenSpec change), with "progress their change" and "continue their workflow" as reinforcing verbs; not a full enumeration of distinct actions, so it sits between anchors 2 and 3.

2.5 / 3

Completeness

It states what the skill does (create the next artifact for an OpenSpec change) and includes an explicit "Use when the user wants to..." clause answering when to invoke it.

3 / 3

Trigger Term Quality

Natural phrasing like "progress their change", "create the next artifact", and "continue their workflow" maps to terms users would actually say, giving good coverage of natural variations.

3 / 3

Distinctiveness Conflict Risk

It targets a narrow niche (OpenSpec change workflow) with distinct, domain-specific triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

11.5

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Fission-AI/OpenSpec
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.