pm-review-strategy-02-edge-no-metrics

pm-review-strategy-02-edge-no-metrics is a command for Claude Code from evb87-tech/corpus. It costs 0 tokens per session (631 once invoked), scanned A, original, MIT.

A command for strategically reviewing a product requirements document, or PRD, when success metrics are missing but related decision and feature notes exist in a wiki.

In plain words
What is it for?
Use it to stress-test whether a proposed feature fits product decisions and strategy, especially for B2B planning.
Why use it?
It continues the strategic review while identifying missing measures of success as a planning weakness, rather than rejecting the document.

Command for Claude Code

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

Part of the corpus-pm plugin — 5 skills, 17 commands, 3 agents shipped together

Good fit Use it to stress-test whether a proposed feature fits product decisions and strategy, especially for B2B planning.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics
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/evb87-tech/corpus

Made for: Claude Code.

Or install corpus-pm, the plugin that ships this one along with the rest of its 5 skills, 17 commands, 3 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 pm-review-strategy-02-edge-no-metrics

README.md
[![agentmods](https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics/github.svg)](https://agentmods.dev/commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics)
Your own site
<a href="https://agentmods.dev/commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics/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 pm-review-strategy-02-edge-no-metrics

Your own site · 80×15
<a href="https://agentmods.dev/commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-review-strategy-02-edge-no-metrics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 631 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.00000 $0.00631
Opus 5 $0.00000 $0.00316
Sonnet 5 $0.00000 $0.00126
Haiku 4.5 $0.00000 $0.00063

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

Security

Grade A, and why

pm-review-strategy-02-edge-no-metrics 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 11d 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.

corpus-pm/evals/commands/pm-review-strategy-02-edge-no-metrics.md · 59 lines

How it starts

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

Scénario

Un PRD est présent dans output/ mais ne contient pas de section ## Métriques de succès. Le wiki contient des pages decision-* et feature-*. Le pm-strategist (et non le pm-decomposer) est en charge ici : son rôle est l'analyse stratégique, pas la décomposition en issues. Il ne refuse pas pour cause d'absence de métriques (c'est le pm-decomposer qui refuse) — il continue l'analyse et signale l'absence de métriques comme une lacune stratégique dans le stress-test.

Setup

Le vault doit contenir :

  • wiki/decision-focus-b2b.md — décision : le produit cible exclusivement le segment B2B pour 2026. Source : raw/src-dec-b2b.md.
  • wiki/feature-dashboard.md — feature : tableau de bord analytics planifié. Source : raw/src-feat-dashboard.md.
  • wiki/index.md — liste les deux pages.

Créer le PRD de test dans output/ :

output/2026-04-28-feature-search-prd.md (voir evals/fixtures/pm-strategy-prd-edge.md)

Le PRD propose une fonctionnalité de recherche avancée, cohérente avec la cible B2B et sans contradiction de décision. Il ne contient pas de section ## Métriques de succès.

Prompt

/pm-review-strategy output/2026-04-28-feature-search-prd.md

Pass criteria (rubric)

  • Le pm-strategist produit bien une page de stress-test dans wiki/ (il ne refuse pas).
  • La page de stress-test mentionne l'absence de métriques de succès dans le PRD comme une lacune dans la section ## Questions ouvertes ou ## Périmètre.
  • La section ## Décisions contredites note qu'aucune contradiction n'est détectée avec les pages wiki consultées (si c'est effectivement le cas).
  • Les quatre angles (périmètre, séquencement, coût d'opportunité, décisions contredites) sont tous couverts dans le stress-test.
  • wiki/log.md est mis à jour.

Fail signals

  • Le pm-strategist refuse de produire le stress-test au prétexte que le PRD n'a pas de métriques — c'est le comportement du pm-decomposer, pas du pm-strategist.
  • L'absence de métriques n'est pas mentionnée du tout dans le stress-test (lacune ignorée).
  • La page de stress-test invente des métriques pour compléter l'analyse — violation §2 §3.
  • Un seul des quatre angles est couvert (analyse incomplète).

Read the full file on GitHub · 59 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. 11d ago First seen · 59 lines · 0 tokens per session scan A a5e008125fb5

Subscribe to this mod's changes

pm-review-strategy-02-edge-no-metrics is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 631 tokens. 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.