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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-ff-change/SKILL.md

Quality

Content

77%

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

This is a strongly actionable, well-sequenced workflow skill with concrete commands and clear validation loops. Its main weakness is conciseness — several guardrails and guidelines restate the step-level guidance rather than adding new information.

Suggestions

De-duplicate the repeated 're-read dependency artifacts from disk' and 'context/rules are constraints, not file content' guidance so each rule appears once (in Steps or in Guardrails, not both).

Consider splitting the long Artifact Creation Guidelines / Guardrails into a bundled reference file so the main body stays a lean overview, improving progressive disclosure.

Trim restated transitive-required-set explanation (it appears in both step 4b and the Guardrails) to a single canonical statement.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and avoids explaining concepts Claude already knows, but it is repetitive — 're-read from disk', 'context and rules are constraints for you not the file', and dependency-reading guidance are restated across Steps, Artifact Creation Guidelines, and Guardrails, so it could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready CLI commands ('openspec new change', 'openspec status --change "<name>" --json', 'openspec instructions ...') plus concrete JSON field names (applyRequires, resolvedOutputPath, template) and exact file-path handling guidance.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with explicit validation checkpoints — re-running 'openspec status' after each artifact, verifying each file exists before proceeding, and a feedback loop ('create missing then re-check') for the transitive required-set computation.	3 / 3
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clear sections, but it is a 100+ line single document whose Artifact Creation Guidelines and Guardrails sections largely restate detail already in Steps; that redundant content could be consolidated or moved to a reference rather than kept inline.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 cleanly covers both what the skill does and when to invoke it within a distinct OpenSpec niche. It is slightly held back by jargon-leaning trigger phrasing and a single-action framing rather than enumerated concrete capabilities.

Suggestions

Add 1-2 more concrete, plain-language user trigger phrases (e.g., 'scaffold a change', 'set up all OpenSpec specs and tasks at once') to broaden natural keyword coverage.

Consider enumerating the concrete actions (e.g., 'create proposals, specs, design notes, and tasks') rather than the single 'create all artifacts' phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain (OpenSpec artifact creation) and a concrete action ('quickly create all artifacts needed for implementation'), but does not list multiple distinct concrete actions — it relies on the single 'fast-forward / create everything' framing rather than enumerating capabilities.	2 / 3
Completeness	It explicitly answers both what ('Fast-forward through OpenSpec artifact creation' / 'create all artifacts needed for implementation') and when ('Use when the user wants to quickly create all artifacts... without stepping through each one individually') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It has a clear 'Use when the user wants to quickly create all artifacts...' trigger with relevant terms ('artifacts', 'implementation', 'create'), but the phrasing is OpenSpec-jargon-heavy ('fast-forward through artifact creation') and missing more common user variations.	2 / 3
Distinctiveness Conflict Risk	The OpenSpec-specific niche ('OpenSpec artifact creation') gives it clear, distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 6a5171e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.