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

80%

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

85%

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

The body is highly actionable with executable commands, JSON field contracts, and a well-sequenced workflow including validation feedback loops. Its only weakness is mild redundancy where the context/rules guidance is stated twice.

Suggestions

De-duplicate the 'context and rules are constraints, not file content' guidance: state it once in the Artifact Creation Guidelines and reference it from step 4a instead of repeating it.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and action-oriented, but the 'context and rules are constraints for YOU, not content for the file' guidance is restated in both step 4a and the Artifact Creation Guidelines section, so not every token earns its place.	2 / 3
Actionability	Provides fully executable commands (openspec new/status/instructions with --json), names the exact JSON fields to parse, and specifies tools (AskUserQuestion, TodoWrite) and outputPath, making it copy-paste ready.	3 / 3
Workflow Clarity	A clear 5-step sequence with an explicit feedback loop: re-run 'openspec status' after each artifact, confirm every applyRequires artifact is 'done', and verify each file exists before proceeding.	3 / 3
Progressive Disclosure	Self-contained with no bundle files and no nested references; content is organized into well-signaled sections (Input, Steps, Output, Guidelines, Guardrails) appropriate for a single-file workflow skill.	3 / 3
	Total	11 / 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 clearly establishes a niche and answers both what and when with an explicit trigger, scoring well on completeness and distinctiveness. It is held back by jargon-forward framing and a single composite action rather than multiple concrete actions.

Suggestions

Lead with a concrete action verb in third person (e.g., 'Generates all OpenSpec implementation artifacts in one pass') and list the specific artifacts it produces.

Add natural user phrasing to the trigger, e.g., 'Use when the user asks to scaffold an OpenSpec change, set up a change, or create all artifacts at once.'

Dimension	Reasoning	Score
Specificity	Names the domain ('OpenSpec artifact creation') and a composite action ('create all artifacts needed for implementation'), but does not enumerate multiple distinct concrete actions like the score-3 anchor ('extract text, fill forms, merge documents').	2 / 3
Completeness	Explicitly answers both what ('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	Includes a 'Use when the user wants to quickly create all artifacts' trigger, but the leading phrase 'Fast-forward through OpenSpec artifact creation' is jargon-heavy and lacks common natural variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (OpenSpec artifact creation) and the 'without stepping through each one individually' clause distinguishes it from a step-through variant, making conflicts unlikely.	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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-ff-change/SKILL.md
Commit: be872c1

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.