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.
npx skills add ramybarsoum/prodkit --skill feature-doc-review-panelgit clone --depth 1 https://github.com/ramybarsoum/prodkitWrote 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.
[](https://agentmods.dev/skills/ramybarsoum/prodkit/feature-doc-review-panel)<a href="https://agentmods.dev/skills/ramybarsoum/prodkit/feature-doc-review-panel"><img src="https://agentmods.dev/badge/skills/ramybarsoum/prodkit/feature-doc-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.
<a href="https://agentmods.dev/skills/ramybarsoum/prodkit/feature-doc-review-panel"><img src="https://agentmods.dev/badge/skills/ramybarsoum/prodkit/feature-doc-review-panel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01478 |
| Opus 5 | $0.00020 | $0.00739 |
| Sonnet 5 | $0.00008 | $0.00296 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
feature-doc-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 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interaction style: Use the
AskUserQuestiontool 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 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-doc-review-panel- Review a Feature Doc with all 7 sub-agents/feature-doc-review-panel [file-path]- Review specific Feature Doc by path/feature-doc-review-panel --perspectives "eng,design,exec"- Review with subset of agents/feature-doc-review-panel --extended- Include 6 additional perspectives (architecture, data, devops, performance, security, testing)
Execution Steps
Step 1: Locate the Feature Doc
If a file path was provided as an argument, use that. Otherwise:
- Search for Feature Docs in the workspace:
Glob("**/FEATURE-DOC.md"),Glob("**/feature-doc*.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 Feature Doc content. Store it as FEATURE_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
Default 7 (core panel):
| Perspective | Sub-Agent File | Key |
|---|---|---|
| Engineering | _system/sub-agents/engineer-reviewer.md |
eng |
| Design | _system/sub-agents/designer-reviewer.md |
design |
| Executive | _system/sub-agents/executive-reviewer.md |
exec |
| Legal | _system/sub-agents/legal-advisor.md |
legal |
| UX Research | _system/sub-agents/uxr-analyst.md |
uxr |
| Skeptic | _system/sub-agents/skeptic.md |
skeptic |
| Customer Voice | _system/sub-agents/customer-voice.md |
customer |
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.
- 8d ago First seen · 171 lines · 41 tokens per session scan A 9e83ca7fc0ca
feature-doc-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,478 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.
Other skills, from other repositories
respect
2-mode UI respect skill — brief (generate RESPECT.md design brief before coding) and checkpoint (final pre-ship gate enforcing user-respect via α/β/γ gate matrix). Use --mode brief when starting any UI screen; use --mode checkpoint before shipping. RESPECT.md absence blocks craft-lint (exit 2).
design-token
A two-step process for documenting a product’s visual direction and design rules. It first gathers and filters design references into a brief, then turns that direction into reusable design tokens such as colors, spacing, and typography choices.
customer-journey-map
Visualize every touchpoint a customer has with a product or service — stages, actions, emotions, pain points, opportunities.
double-diamond
Design problems with two diamond phases: Discover/Define (right problem), Develop/Deliver (right solution).
design-spatial
Spatial composition and layout for frontend design. Load with design when composing pages/dashboards/components, or whenever generated UI looks off — overlapping/colliding elements, weak hierarchy, or generic ("looks like every startup site"). The core idea: a model can't trust its own layout, so render it, critique…
design-system
Mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems. (Aesthetic direction lives in design-thinking; anti-trend/anti-slop…