spec-consistency

spec-consistency is a skill for Claude Code, Codex from samibs/skillfoundry. It costs 25 tokens per session (407 once invoked), scanned A, original, MIT.

A requirements-tracking guide that checks whether the software being built still matches its product requirements document (PRD). It follows requirements through implementation and records changes in scope.

In plain words
What is it for?
Use it to trace PRD sections to code, verify acceptance criteria, maintain a requirements matrix, and report specification drift.
Why use it?
It helps catch missing requirements, undocumented changes, and differences between the agreed specification and the delivered software.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to trace PRD sections to code, verify acceptance criteria, maintain a requirements matrix, and report specification drift.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/samibs/skillfoundry/spec-consistency
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 samibs/skillfoundry --skill spec-consistency
Clone the repo
git clone --depth 1 https://github.com/samibs/skillfoundry

Made for: Claude Code, Codex.

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.

agentmods badge for spec-consistency

README.md
[![agentmods](https://agentmods.dev/badge/skills/samibs/skillfoundry/spec-consistency.svg)](https://agentmods.dev/skills/samibs/skillfoundry/spec-consistency)
Your own site
<a href="https://agentmods.dev/skills/samibs/skillfoundry/spec-consistency"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/spec-consistency.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 407 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00407
Opus 5 $0.00013 $0.00204
Sonnet 5 $0.00005 $0.00081
Haiku 4.5 $0.00003 $0.00041

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

Security

Grade A, and why

spec-consistency 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 4d 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.

.agents/skills/spec-consistency/SKILL.md · 69 lines

What it actually says

Spec Consistency Agent

Identity

PRD guardian. Drift detector. Requirements tracer.

Persona: See agents/spec-consistency.md for full persona definition.

Mission

Ensure implementation matches PRD specifications and detect drift.

Core Responsibilities

  1. Trace requirements from PRD to implementation
  2. Detect specification drift during development
  3. Validate acceptance criteria completion
  4. Alert on undocumented scope changes
  5. Maintain requirements traceability matrix
  6. Block merges when implementation artifact format (e.g., CSV vs JSON) diverges from PRD or story contract

Hard Constraints

  • MUST validate every PRD section has implementation
  • MUST detect drift within 24 hours
  • MUST maintain traceability for compliance
  • MUST document all scope changes

Inputs

  • PRDs from genesis/ folder
  • Code changes from coder
  • Deployment records from production-orchestrator
  • Story files from docs/stories/**

Outputs

  • Traceability matrix
  • Drift detection alerts
  • Scope change documentation
  • Compliance validation report

Decision Authority

  • Can require scope change approval
  • Can block undocumented changes
  • Can mandate PRD updates

Escalation Rules

  • Undocumented scope change → BLOCK, require approval
  • PRD section without implementation → ALERT
  • Implementation without PRD requirement → ESCALATE
  • Drift detected → notify stories + requirements authority for PRD amendment before work resumes

Self-check Procedures

  • Daily traceability matrix validation
  • Weekly drift detection sweep
  • Monthly compliance audit

Failure Detection

  • Drift detected >24 hours after occurrence
  • Traceability gaps
  • Scope creep without documentation

Test Requirements

  • Drift detection accuracy tests
  • Traceability completeness tests
  • Scope change validation tests
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.

  1. 4d ago First seen · 69 lines · 25 tokens per session scan A ca837e208da0

Subscribe to this mod's changes

spec-consistency is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 407 once invoked, about $0.0001 per session on Opus 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-09-03.

Related

Other skills, from other repositories

clean-code-review

Run a comprehensive Clean Code audit against the codebase — module size, function complexity, long parameter lists, TODO/FIXME markers, commented-out code, duplication (DRY), Boy Scout delta, dead exports, test smells, shell-parity (PS/Bash twins), dep boundaries (cross-package imports), frozen-arrays drift…

srnichols/plan-forge · 92 tokens

code-review

Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…

srnichols/plan-forge · 70 tokens

stakeholder-briefing

Generate a per-organisation stakeholder briefing for Plan Forge from the canonical template, optionally drafting the prospect-specific sections from a source directory of customer materials. Use when an internal champion needs to walk a colleague or VP through the decision to adopt Plan Forge.

srnichols/plan-forge · 55 tokens

azure-sweep

Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.

srnichols/plan-forge · 0 tokens

forge-quench

Systematically reduce .NET/C# code complexity while preserving exact behavior — measure, understand, propose, prove, report. Use after a feature is complete and tests pass, when code works but is harder to maintain than it should be.

srnichols/plan-forge · 51 tokens

ui-scaffold

Scaffold a new Blazor page with proper layering — service interface, page component (markup + code-behind split), DTO, validation, error handling, and bUnit test. Enforces architecture-principles + blazor-fluent-ui conventions. Use when adding any new UI surface to a Blazor Server app.

srnichols/plan-forge · 68 tokens