CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-ff-change

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually. Also use when the user says "openspec ff" or "opsx ff".

Quality

82%

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

73%Weight 40%Scale 1-5

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 well-sequenced, highly actionable workflow with strong validation checkpoints and feedback loops appropriate to a batch artifact-creation task. Its main weakness is token efficiency: several rules are stated twice across the Steps, Artifact Creation Guidelines, and Guardrails sections, and the store/project-check prose could be tightened or moved out of the main line of the workflow.

Suggestions

Deduplicate the guidance repeated across Steps, Artifact Creation Guidelines, and Guardrails (context/rules handling, re-reading dependencies, and file-existence verification each appear twice) into a single location.

Tighten the Store selection and Project check paragraphs — they are dense multi-clause sentences; splitting or trimming them would reduce token cost without losing the operational rules.

Consider moving the detailed store-resolution and root-error-handling edge cases into a reference file, keeping the core five-step workflow lean in SKILL.md.

DimensionReasoningScore

Conciseness

The body is operational and free of explanations of concepts Claude already knows, but it carries noticeable repetition and padding: the rule that 'context and rules are constraints for YOU, not content for the file' appears in both step 4a and the Artifact Creation Guidelines section, 'read dependency artifacts from disk' is restated in the Guardrails, and the store-selection and project-check paragraphs run long. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the level-4 anchor's 'minor instances.'

3 / 5

Actionability

Provides concrete, executable commands ('openspec new change "<name>"', 'openspec status --change "<name>" --json', 'openspec instructions <artifact-id> --change "<name>" --json'), specifies the JSON fields to parse (applyRequires, artifacts, requires, resolvedOutputPath), and gives a naming example ('add user authentication' → 'add-user-auth'). Minor gaps keep it from fully copy-paste-ready coverage: artifact content is delegated to the CLI's template/instruction fields rather than shown, so the common case is covered indirectly.

4 / 5

Workflow Clarity

A clear numbered 5-step sequence with explicit validation checkpoints and feedback loops for a batch operation: check the project root before any write, re-run 'openspec status --change "<name>" --json' after creating each artifact, verify each artifact file exists before proceeding, and explicit stop conditions for the required set (done, skipped, or deliberately skipped). This matches the level-5 anchor's 'explicit validation steps; feedback loops for error recovery' for a batch workflow.

5 / 5

Progressive Disclosure

A single-file skill with no bundle files (no references/, scripts/, or assets/ exist) and no external references to verify. Content is organized under clear, well-signaled sections (Store selection, Project check, Input, Steps, Output, Artifact Creation Guidelines, Guardrails) with nothing buried or nested. It falls short of a clean 5 only because the lengthy store-selection and error-handling prose is inlined where a reference file could keep the core workflow leaner — a minor organization gap matching the level-4 anchor.

4 / 5

Total

16

/

20

Passed

Description

82%Weight 40%Scale 1-5

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

A strong description: it states what the skill does, when to use it, and provides concrete, natural trigger phrases tied to the OpenSpec CLI. The main gap is specificity — it describes the overall effect ('create all artifacts') without naming any of the concrete artifacts or sub-actions involved.

Suggestions

Name one or two concrete artifacts or outputs (e.g., proposal, specs, tasks) in the description to lift specificity beyond a single generic action.

Add a natural variation such as 'fast-forward' or 'generate all artifacts in one pass' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('OpenSpec artifact creation') and one concrete action ('quickly create all artifacts needed for implementation without stepping through each one individually'), but does not enumerate the specific artifacts or actions it performs. It matches the anchor for domain plus 1-2 concrete actions without comprehensive coverage, and falls short of the level-4 anchor's 'several specific actions.'

3 / 5

Completeness

Explicitly answers both questions: what it does ('Fast-forward through OpenSpec artifact creation... create all artifacts needed for implementation') and when to use it ('Use when the user wants to quickly create all artifacts... Also use when the user says "openspec ff" or "opsx ff"') with concrete trigger phrases. This matches the level-5 anchor; the level-4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Includes natural, explicit trigger phrases users would actually say: 'openspec ff', 'opsx ff', and 'quickly create all artifacts needed for implementation'. Good keyword coverage, though a few natural variations (e.g., 'fast-forward', 'generate all artifacts') are missing, so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific tool (OpenSpec) with distinct trigger phrases ('openspec ff', 'opsx ff') that no generic or neighboring skill would claim, giving it a clear niche with minimal conflict risk. It is clearly distinguishable from generic artifact- or spec-creation skills.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Fission-AI/OpenSpec

Path

skills/openspec-ff-change/SKILL.md

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.