spec-panel

spec-panel is a command for Claude Code from SuperClaude-Org/SuperClaude_Framework. It costs 17 tokens per session (3,586 once invoked), scanned A, original, MIT.

A command that reviews a software specification from several expert viewpoints and suggests improvements. A specification is a written description of what a system should do and how it should work.

In plain words
What is it for?
Use it to review requirements, architecture, testing plans, or compliance details, then produce a clearer revised specification.
Why use it?
It helps find missing requirements, unclear wording, and quality problems before development begins.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the superclaude plugin — 5 skills, 30 commands, 20 agents, 1 hook, 2 MCP servers shipped together

Good fit Use it to review requirements, architecture, testing plans, or compliance details, then produce a clearer revised specification.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/superclaude-org/superclaude_framework/spec-panel
About the project

SuperClaude Framework is a configuration framework that organizes Claude Code into a structured development environment with specialized commands, AI agents, behavioral modes, and integrations. It is for developers who want guided workflows covering activities from brainstorming through deployment. The catalogue entries are its commands, agents, skills, instructions, integrations, settings, hooks, and plugin components.

SuperClaude-Org/SuperClaude_Framework · 23,905 stars · on GitHub · superclaude.netlify.app

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.

Clone the repo
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Framework

Made for: Claude Code.

Or install superclaude, the plugin that ships this one along with the rest of its 5 skills, 30 commands, 20 agents, 1 hook, 2 MCP servers.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/spec-panel/github.svg)](https://agentmods.dev/commands/superclaude-org/superclaude_framework/spec-panel)
Your own site
<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/spec-panel"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/spec-panel/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-panel

Your own site · 80×15
<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/spec-panel"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/spec-panel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,586 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.00017 $0.03586
Opus 5.5 $0.00007 $0.01434
Sonnet 5.5 $0.00003 $0.00717
Haiku 4.5 $0.00002 $0.00359

Measured 1mo ago against content hash b348ea881172, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-panel 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/superclaude/commands/spec-panel.md · 430 lines

How it starts

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

/sc:spec-panel - Expert Specification Review Panel

Triggers

  • Specification quality review and improvement requests
  • Technical documentation validation and enhancement needs
  • Requirements analysis and completeness verification
  • Professional specification writing guidance and mentoring

Usage

/sc:spec-panel [specification_content|@file] [--mode discussion|critique|socratic] [--experts "name1,name2"] [--focus requirements|architecture|testing|compliance] [--iterations N] [--format standard|structured|detailed]

Behavioral Flow

  1. Analyze: Parse specification content and identify key components, gaps, and quality issues
  2. Assemble: Select appropriate expert panel based on specification type and focus area
  3. Review: Multi-expert analysis using distinct methodologies and quality frameworks
  4. Collaborate: Expert interaction through discussion, critique, or socratic questioning
  5. Synthesize: Generate consolidated findings with prioritized recommendations
  6. Improve: Create enhanced specification incorporating expert feedback and best practices

Key behaviors:

  • Multi-expert perspective analysis with distinct methodologies and quality frameworks
  • Intelligent expert selection based on specification domain and focus requirements
  • Structured review process with evidence-based recommendations and improvement guidance
  • Iterative improvement cycles with quality validation and progress tracking

Expert Panel System

Core Specification Experts

Karl Wiegers - Requirements Engineering Pioneer

  • Domain: Functional/non-functional requirements, requirement quality frameworks
  • Methodology: SMART criteria, testability analysis, stakeholder validation
  • Critique Focus: "This requirement lacks measurable acceptance criteria. How would you validate compliance in production?"

Gojko Adzic - Specification by Example Creator

  • Domain: Behavior-driven specifications, living documentation, executable requirements
  • Methodology: Given/When/Then scenarios, example-driven requirements, collaborative specification
  • Critique Focus: "Can you provide concrete examples demonstrating this requirement in real-world scenarios?"

Read the full file on GitHub · 430 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.

  1. 1mo ago Changed · +2 lines b348ea881172
  2. 1mo ago First seen · 428 lines · 17 tokens per session scan A 02b57ca07a4e

Subscribe to this mod's changes

spec-panel is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,905 stars, last pushed 20d ago), licensed MIT. It adds 17 tokens to every session and 3,586 once invoked, about $0.0001 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.