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

72%

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 a well-structured, highly actionable workflow with concrete commands, explicit validation checkpoints, and named tool usage. Its main weaknesses are minor redundancy between the inline steps and the later guidelines/guardrails sections, and a lightly specified error-recovery loop.

Suggestions

Consolidate the duplicated constraint guidance (context/rules are constraints, use template as structure) so it appears once, trimming the 'Artifact Creation Guidelines' section to lift conciseness toward anchor 5.

Spell out a short fix-and-retry loop for the case where an artifact's status does not advance to 'done' (e.g., re-read dependencies, regenerate, re-check status) to strengthen workflow clarity to anchor 5.

Consider merging 'Guardrails' into the relevant steps or trimming overlap with step 4 to tighten the single-file organization.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with minimal over-explanation, but the 'Artifact Creation Guidelines' and 'Guardrails' sections partly restate constraints already given in step 4 (context/rules as constraints, use template), giving minor instances that could be trimmed, matching anchor 4.	4 / 5
Actionability	Provides copy-paste-ready executable commands (openspec new change, openspec status --json, openspec instructions --json), names the exact JSON fields to parse, and specifies the tools to use (TodoWrite, AskUserQuestion), matching anchor 5 for fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints (re-run openspec status --json to confirm applyRequires artifacts are done, verify each file exists before proceeding) and a feedback loop (AskUserQuestion on unclear input), matching anchor 4; it falls short of 5 because the fix-and-retry loop when status does not advance is only lightly spelled out.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Input, Steps, Output, Artifact Creation Guidelines, Guardrails) with no nested references and content appropriately kept inline for a cohesive single-file workflow, matching anchor 4; it does not reach 5 because the slight duplication between step 4 and the later guideline/guardrail sections is a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

62%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 and explicitly covers both what the skill does and when to use it, with a distinct tool-scoped niche. It is slightly held back by leaning on a single metaphor rather than enumerating concrete actions and by limited synonym/variation coverage in its trigger terms.

Suggestions

Enumerate one or two more concrete actions (e.g., 'scaffold a change, generate each artifact in dependency order, and verify apply-readiness') to lift specificity above anchor 3.

Broaden trigger-term coverage with natural synonyms a user might say (e.g., 'scaffold', 'set up', 'spin up', 'OpenSpec change') rather than relying on the single 'fast-forward' phrase.

Add a short list of alternate trigger phrasings to the 'when' clause to strengthen completeness toward anchor 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('OpenSpec artifact creation') and a concrete action ('create all artifacts needed for implementation'), but relies on the single 'fast-forward' metaphor rather than enumerating multiple specific actions; not comprehensive, matching anchor 3.	3 / 5
Completeness	Explicitly answers both 'what' (fast-forward through artifact creation) and 'when' (use when the user wants to quickly create all artifacts without stepping through each), matching anchor 4 where both are present though the trigger could use more varied phrasing.	4 / 5
Trigger Term Quality	Includes relevant natural phrasing ('quickly create all artifacts', 'without stepping through each one individually') plus domain terms (OpenSpec, artifacts, implementation), but lacks common variations/synonyms and file extensions, so it does not reach anchor 4.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific tool and a distinct workflow mode (fast-forward vs. stepping through each artifact), giving a clear niche with low overlap risk; minor overlap possible with sibling openspec skills, matching anchor 4.	4 / 5
	Total	14 / 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-ff-change/SKILL.md
Commit: f8e9b1b

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