openspec-sync-specs

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Quality

67%

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-sync-specs/SKILL.md

Quality

Content

68%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, actionable instruction-only workflow with concrete paths and commands. Its main weakness is the absence of an explicit validation/verification checkpoint before applying mutating edits to main specs, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint before writing changes (e.g., re-read the merged main spec and confirm each delta was applied correctly), with a fix-and-retry loop, to lift workflow clarity above the destructive-operation cap.

Consider moving the Delta Spec Format Reference and Output On Success template into a referenced file to tighten the main body toward lean token efficiency.

Tighten the MODIFIED Requirements sub-steps, which repeat handling cases that partly overlap, to reduce minor verbosity.

Dimension	Reasoning	Score
Conciseness	The body is efficient with direct steps and no padding of concepts Claude already knows, though the full delta-spec reference and output template are somewhat long, fitting anchor 4 rather than the every-token-earns-its-place anchor 5.	4 / 5
Actionability	Provides concrete paths, a specific command (openspec list --json), a named tool (AskUserQuestion), and explicit per-section handling rules (ADDED/MODIFIED/REMOVED/RENAMED with FROM:/TO:), giving mostly executable guidance with minor gaps per anchor 4.	4 / 5
Workflow Clarity	The numbered sequence (steps 1-4) is clear, but this is a mutating batch operation on main specs with only an after-the-fact summary and no explicit pre-write validation/feedback loop, so the destructive-operation cap limits it to anchor 3.	3 / 5
Progressive Disclosure	The skill is self-contained with well-organized sections (Input, Steps, Format Reference, Guardrails) and no nested external references, but at ~120 lines with an inlined format reference it sits at anchor 4 rather than the lean single-file anchor 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 a distinct, low-conflict niche. It is held back from top marks by modest action specificity and limited trigger-term breadth.

Suggestions

Add 1-2 more concrete actions to the description (e.g., 'add, modify, remove, or rename requirements') to raise specificity toward comprehensive coverage.

Broaden trigger terms with natural synonyms users might say, such as 'apply a change', 'merge delta specs', or 'promote spec changes', to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the domain (delta/main specs) and 1-2 concrete actions (sync, update main specs) but is not comprehensive, matching anchor 3 rather than the multi-action anchor 4.	3 / 5
Completeness	Explicitly states both what ('Sync delta specs from a change to main specs') and when ('Use when the user wants to update main specs...'), with the when clear but a single trigger phrase, placing it at anchor 4 rather than the multi-trigger anchor 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('delta spec', 'main specs', 'change') users would say, but lacks common synonyms and variations, fitting anchor 3 rather than the broad coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (openspec delta-to-main spec syncing) with distinct triggers and an explicit scope boundary ('without archiving the change'), giving minimal conflict risk per anchor 5.	5 / 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-sync-specs/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.