What is speq-spec-merge?

A procedure for merging temporary specification changes into a permanent specification library. It uses change markers to add, replace, or remove scenarios.

Use it after a plan creates delta specifications, to merge them into the library, validate the result, and flag when the library may need reorganization.

It helps apply planned specification changes consistently and prevents accidental changes when existing features or scenarios already exist.

speq-spec-merge — Skill for Claude Code by marconae/speq-skill

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add marconae/speq-skill --skill speq-spec-merge

Clone the repo

git clone --depth 1 https://github.com/marconae/speq-skill

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/marconae/speq-skill/speq-spec-merge/github.svg)](https://agentmods.dev/skills/marconae/speq-skill/speq-spec-merge)

Your own site

<a href="https://agentmods.dev/skills/marconae/speq-skill/speq-spec-merge"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-spec-merge/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/marconae/speq-skill/speq-spec-merge"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-spec-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,218 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.02218
Opus 5.5	$0.00017	$0.00887
Sonnet 5.5	$0.00008	$0.00444
Haiku 4.5	$0.00004	$0.00222

Measured 14d ago against content hash 4f9dbf16352b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speq-spec-merge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/speq-spec-merge/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec Merge

Load Plan Context

Read: specs/_plans/<plan-name>/plan.md
List: specs/_plans/<plan-name>/**/spec.md
Read: specs/_plans/<plan-name>/architecture.md (if it exists)

Run speq feature list to see the current permanent spec library.

If architecture.md exists in the plan, run steps 1 and 2 of "Apply Architecture Delta" before any feature merge.

Apply Deltas

For each delta spec at specs/_plans/<plan-name>/<domain>/<feature>/spec.md:

specs/<domain>/<feature>/spec.md exists?
├─ No  → Copy delta (strip markers)
└─ Yes → Merge using markers below

A delta block's anchor is the first non-empty line inside the block. ### Scenario: <name> and ## Background match exactly; # Feature: <name> matches by the prefix # Feature, so a description delta MAY rename the feature.

Scenario-anchor markers (### Scenario: <name> wrapped in the marker):

Marker	Action
`DELTA:NEW`	Append scenario
`DELTA:CHANGED`	Replace scenario with same name
`DELTA:REMOVED`	Delete scenario with same name

Prose-anchor markers (## Background or # Feature: <name> wrapped in the marker):

Marker	Action
`DELTA:CHANGED`	Replace the whole section (heading plus body) in place. Any line the block omits is deleted from the permanent spec
`DELTA:NEW`	Rejected — Background and the description are required sections that always exist
`DELTA:REMOVED`	Rejected — removing a required section produces an invalid spec

After each merge:

Strip all  markers
Validate: speq feature validate <domain>/<feature>
If validation fails, stop and report. Do not guess fixes

Apply Architecture Delta

The optional file specs/_plans/<plan-name>/architecture.md changes specs/architecture.md. The speq CLI does not see it, so you apply it by hand. Its format is defined in /speq-plan's references/architecture-delta-template.md. The target format is defined in /speq-plan's references/architecture-template.md.

Read the full file on GitHub · 131 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

14d ago Changed · -1 lines · +5 tokens per session 4f9dbf16352b
25d ago Changed · +3 tokens per session 3083ce834180
1mo ago Changed · -6 lines 89d029ec52ec
1mo ago Changed · +29 lines 24ae0549fbf2
1mo ago Changed · +17 lines d620c0df3c11
2mo ago Changed · +1 lines a4b3e4e57f0e
2mo ago First seen · 91 lines · 34 tokens per session scan A 433c496a21be

Subscribe to this mod's changes

speq-spec-merge is a skill published in the GitHub repository marconae/speq-skill (54 stars, last pushed 15d ago), licensed MIT. It adds 42 tokens to every session and 2,218 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Planning Writing and docs agent-skills agentic-ai artificial-intelligence skills spec-driven-development

speq-spec-merge next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speq-spec-mergemarconae/speq-skill	Skill	54	15d ago	MIT	A	42	Claude Code
skillevaluatorNVIDIA/SkillEvaluator	Skill	651	today	Apache-2.0	A	56	Claude Code, Codex
create-custom-graderNVIDIA/SkillEvaluator	Skill	651	today	Apache-2.0	A	35	Claude Code, Codex
contract-builderMageByte-Zero/spec-superflow	Skill	880	6d ago	MIT	A	33	Claude Code
memory-audit-pattern-extractionDataojitori/nocturne_memory	Skill	1.4k	4d ago	MIT	A	48	Claude Code
workflow-startMageByte-Zero/spec-superflow	Skill	880	6d ago	MIT	A	61	Claude Code
need-explorerMageByte-Zero/spec-superflow	Skill	880	6d ago	MIT	A	44	Claude Code