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 ./.claude/skills/openspec-ff-change/SKILL.md

Quality

Content

82%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 content is highly actionable with executable CLI commands and a well-sequenced workflow including status feedback loops. Its main weaknesses are mild redundancy between the steps and guidelines sections and validation that checks file existence rather than artifact correctness.

Suggestions

Consolidate the repeated "context/rules are constraints, not content" guidance into one place to reduce redundancy and tighten conciseness.

Add a content-oriented validation checkpoint (e.g., confirm the artifact satisfies the instruction schema) rather than only verifying the file exists, to strengthen workflow clarity for this batch operation.

Move or deduplicate the Artifact Creation Guidelines so it complements rather than repeats step 4, improving progressive-disclosure organization.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and no concept over-explanation, but the "context and rules are constraints for YOU" point and "read dependency artifacts for context" are repeated across steps and the guidelines section, minor trimming that keeps it just below a 5.	4 / 5
Actionability	It provides copy-paste-ready commands (openspec new change, status --json, instructions --json) plus explicit JSON fields to parse and named tools (TodoWrite, AskUserQuestion), fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	A clear numbered sequence with a status re-check loop and a file-existence verification guardrail provides most checkpoints and a feedback loop, but validation is limited to file existence rather than artifact content correctness, a minor gap below the explicit-validation anchor at 5.	4 / 5
Progressive Disclosure	The self-contained body has clear sections (Input, Steps, Output, Guidelines, Guardrails) and no nested references, but the Artifact Creation Guidelines section largely reiterates step 4 content, leaving a minor organization gap versus the well-split anchor at 5.	4 / 5
	Total	17 / 20 Passed

Description

71%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.

The description clearly answers both what the skill does and when to use it with an explicit trigger clause, and its OpenSpec-specific framing keeps conflict risk low. It is held back from the top tier by limited action enumeration and few trigger-term synonyms.

Suggestions

Enumerate a couple more concrete actions (e.g., scaffold the change directory, generate tasks/specs) to lift specificity toward 4-5.

Add natural trigger synonyms users might say (e.g., "scaffold a change", "prepare artifacts for implementation") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the OpenSpec artifact-creation domain and the concrete action of "quickly create all artifacts needed for implementation," but does not enumerate multiple distinct actions, fitting the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	Explicitly answers both what ("Fast-forward through artifact creation" / "create all artifacts needed for implementation") and when via a concrete "Use when..." trigger clause, matching the anchor for clear explicit answers to both.	5 / 5
Trigger Term Quality	Includes the natural trigger phrase "quickly create all artifacts needed for implementation" and "without stepping through each one individually," but lacks common synonyms or variations a user might say, matching the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	The OpenSpec-specific niche gives it a clear, distinct trigger with minimal conflict risk, but it could overlap with related OpenSpec skills (e.g. apply/init), fitting the mostly-distinct anchor rather than the minimal-conflict anchor at 5.	4 / 5
	Total	15 / 20 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: dwmkerr/openspec-flow
Path: .claude/skills/openspec-ff-change/SKILL.md
Commit: e670a56

Reviewed: 4 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.