spec-challenge

spec-challenge is a skill for Claude Code from Aimeerrhythm/enterprise-change-workflow. It costs 45 tokens per session (2,177 once invoked), scanned A, original, MIT.

An adversarial review step for design specifications and solution plans that looks for weaknesses before implementation.

In plain words
What is it for?
It reviews plans for high-risk changes automatically after planning and can also be run manually, with each finding presented for confirmation.
Why use it?
It helps uncover overlooked risks or gaps in a plan while changes are still easier to make.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the ecw plugin — 15 skills, 3 commands, 7 agents shipped together

Good fit It reviews plans for high-risk changes automatically after planning and can also be run manually, with each finding presented for confirmation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aimeerrhythm/enterprise-change-workflow/spec-challenge
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 Aimeerrhythm/enterprise-change-workflow --skill spec-challenge
Clone the repo
git clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflow

Made for: Claude Code.

Or install ecw, the plugin that ships this one along with the rest of its 15 skills, 3 commands, 7 agents.

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-challenge

README.md
[![agentmods](https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/spec-challenge/github.svg)](https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/spec-challenge)
Your own site
<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/spec-challenge"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/spec-challenge/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.

agentmods 80×15 button for spec-challenge

Your own site · 80×15
<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/spec-challenge"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/spec-challenge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,177 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.00045 $0.02177
Opus 5 $0.00023 $0.01089
Sonnet 5 $0.00009 $0.00435
Haiku 4.5 $0.00005 $0.00218

Measured 8d ago against content hash 149c88d813d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

spec-challenge 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 8d 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.

skills/spec-challenge/SKILL.md · 187 lines

How it starts

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

Spec Challenge — Adversarial Plan Review

After a plan/design document is produced, dispatch the spec-challenge agent for independent adversarial review. Present the review report to the user, who confirms handling for each item.

Announce at start: "Using ecw:spec-challenge for adversarial plan review."

Output language: Read ecw.ymlproject.output_language. Pass to dispatched agent prompt. Report headings and labels follow this language.

Flow

digraph spec_challenge {
  rankdir=TB;

  "Collect review materials" [shape=box];
  "Dispatch spec-challenge agent" [shape=box];
  "Present review report" [shape=box];
  "Per-item user confirmation" [shape=box];
  "Author executes per user decisions" [shape=box];
  "Output response summary" [shape=box];
  "User final confirmation" [shape=box];
  "Review passed" [shape=doublecircle];

  "Collect review materials" -> "Dispatch spec-challenge agent";
  "Dispatch spec-challenge agent" -> "Present review report";
  "Present review report" -> "Per-item user confirmation";
  "Per-item user confirmation" -> "Author executes per user decisions";
  "Author executes per user decisions" -> "Output response summary";
  "Output response summary" -> "User final confirmation";
  "User final confirmation" -> "Review passed";
}

Key Rule: User Drives Decisions

After spec-challenge report returns, AI must NOT respond on its own. Follow these steps strictly:

  1. Present — Display the full spec-challenge review report verbatim
  2. Per-item confirmation — For each fatal flaw (F1, F2, ...), use AskUserQuestion to let user choose handling:
    • ✅ Agree to modify — AI executes the modification
    • ❌ Disagree — User provides rationale, or AI drafts technical rebuttal for user confirmation
    • ❓ Needs discussion — Enter discussion until user decides
  3. Batch confirm improvements — Improvement suggestions (I1, I2, ...) can be presented at once, letting user multi-select which to adopt/defer
  4. Execute — AI executes per user-confirmed decisions
  5. Final confirmation — Output response summary, review passes after user confirms

Read the full file on GitHub · 187 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 187 lines · 45 tokens per session scan A 149c88d813d8

Subscribe to this mod's changes

spec-challenge is a skill published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 2,177 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

g-review

Run the review gate on the current branch diff. Runs the test suite, captures the diff, and dispatches code-lead, which verifies done conditions and reviews the diff itself. Issues MERGE READY or HOLD.

onlygian/G-Forge · 46 tokens

g-audit

Full-codebase or targeted code quality audit. Detects SOLID violations, code smells, architectural drift, dead code, and test coverage gaps. Targeted scope produces an inline report. Whole-codebase scope produces a prioritised roadmap milestone.

onlygian/G-Forge · 52 tokens

g-refactor

Guided refactor workflow — identify target, pre-analyse, spec, approve, execute, review. Accepts a scope path, an audit milestone file, or runs interactively. Safe-by-default: checks test coverage before execution and runs the full review gate after.

onlygian/G-Forge · 0 tokens

g-blast-radius

Analyse the blast radius of a planned change. Inputs a file path, feature name, or list of paths from a plan. Outputs the set of dependent files (forward and reverse references), a per-file volatility score (commit frequency proxy), and a total blast-radius rating (low / moderate / wide). Read-only.

onlygian/G-Forge · 68 tokens

cross-verify

A cross-checking skill that reviews decisions, designs, documents, and implementations from four viewpoints.

idean3885/claude-ops-agent · 0 tokens

decompose

Break a large goal into 3–8 sequenced tasks, each one /eng → /tdd cycle. Writes to specs/{slug}.todos.md when a spec exists, root TODOS.md otherwise. /decompose — decompose a feature or goal /decompose re-entry — resume where you left off (auto-detected).

iamvonpasion/hashb · 71 tokens