What is feature-spec-review-panel?

A review process that examines a feature specification—a document describing a planned product change—from seven viewpoints, including engineering, design, legal, and customers.

Use it to review a feature document from all seven perspectives, or select only the viewpoints you need; an extended review adds architecture, data, operations, performance, security, and testing.

It reveals missing details, conflicting assumptions, and risks before the specification is discussed with stakeholders.

feature-spec-review-panel — Skill for Claude Code by ramybarsoum

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 ramybarsoum/prodkit --skill feature-spec-review-panel

Clone the repo

git clone --depth 1 https://github.com/ramybarsoum/prodkit

Made for: Claude Code.

Or install prodkit, the plugin that ships this one along with the rest of its 10 skills.

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/ramybarsoum/prodkit/feature-spec-review-panel/github.svg)](https://agentmods.dev/skills/ramybarsoum/prodkit/feature-spec-review-panel)

Your own site

<a href="https://agentmods.dev/skills/ramybarsoum/prodkit/feature-spec-review-panel"><img src="https://agentmods.dev/badge/skills/ramybarsoum/prodkit/feature-spec-review-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ramybarsoum/prodkit/feature-spec-review-panel"><img src="https://agentmods.dev/badge/skills/ramybarsoum/prodkit/feature-spec-review-panel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,564 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.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.01564
Opus 5	$0.00020	$0.00782
Sonnet 5	$0.00008	$0.00313
Haiku 4.5	$0.00004	$0.00156

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

Security

Grade A, and why

feature-spec-review-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 9d 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/feature-spec-review-panel/SKILL.md · 174 lines

How it starts

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

Note: This skill is an alias for feature-doc-review-panel. "Feature Spec" and "Feature Doc" are treated identically. The canonical term is "Feature Doc" but this skill exists for backward compatibility.

Interaction style: Use the AskUserQuestion tool for all structured questions in this skill. Group related questions together (2-3 per call) rather than asking one at a time.

Purpose

Get comprehensive feedback on your Feature Spec/Doc from 7 different perspectives in parallel: Engineering, Design, Executive, Legal, UX Research, Skeptic, and Customer Voice.

Catches gaps, challenges assumptions, and surfaces conflicts before stakeholder review.

Usage

/feature-spec-review-panel - Review a Feature Spec with all 7 sub-agents
/feature-spec-review-panel [file-path] - Review specific Feature Spec by path
/feature-spec-review-panel --perspectives "eng,design,exec" - Review with subset of agents
/feature-spec-review-panel --extended - Include 6 additional perspectives (architecture, data, devops, performance, security, testing)

Execution Steps

Step 1: Locate the Feature Spec/Doc

If a file path was provided as an argument, use that. Otherwise:

Search for Feature Specs/Docs in the workspace: Glob("**/FEATURE-DOC.md"), Glob("**/feature-doc*.md"), Glob("**/feature-spec*.md"), Glob("projects/**/FEATURE-DOC.md")
If multiple found, ask the user which one to review using AskUserQuestion
If none found, ask the user to provide the path or paste the content

Read the full document content. Store it as DOC_CONTENT.

Step 2: Load context files (if they exist)

Attempt to read these context files. Skip any that don't exist:

reference/company/product-principles.md (product principles to evaluate against)
reference/company/business-info.md (company context)
reference/strategy/ (any strategy docs)

Combine available context into CONTEXT_SUMMARY (keep it under 500 words).

Step 3: Determine which perspectives to run

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

9d ago First seen · 174 lines · 41 tokens per session scan A 5576f0ac21e6

Subscribe to this mod's changes

feature-spec-review-panel is a skill published in the GitHub repository ramybarsoum/prodkit (4 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,564 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.

Claude Code Planning ai-tools claude claude-code-plugin feature-specs pm-tools

alive:session-history

Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…

alivecontext/alive · 76 tokens

alive:world

The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.

alivecontext/alive · 63 tokens

feature-spec-review-panel