What is pm-epic-01-happy?

A test case for a product-management command that turns a complete PRD into an epic and linked child issues. An epic is a large piece of work, while child issues break it into smaller requirements.

Use it to test converting a well-formed PRD into an epic with P0 and P1 issues, acceptance criteria, and success criteria.

It verifies that requirements, acceptance criteria, success metrics, and links are preserved during project planning.

pm-epic-01-happy — Command for Claude Code by evb87-tech/corpus

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-epic-01-happy/github.svg)](https://agentmods.dev/commands/evb87-tech/corpus/pm-epic-01-happy)

Your own site

<a href="https://agentmods.dev/commands/evb87-tech/corpus/pm-epic-01-happy"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-epic-01-happy/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/commands/evb87-tech/corpus/pm-epic-01-happy"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-epic-01-happy.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 847 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.00000	$0.00847
Opus 5.5	$0.00000	$0.00339
Sonnet 5.5	$0.00000	$0.00169
Haiku 4.5	$0.00000	$0.00085

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

Security

Grade A, and why

pm-epic-01-happy 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.

corpus-pm/evals/commands/pm-epic-01-happy.md · 91 lines

How it starts

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

Scénario

Un PRD complet est disponible dans output/ : il contient des exigences P0/P1 avec des critères d'acceptation et une section ## Métriques de succès. Le pm-decomposer crée un epic avec ## Success Criteria et des issues enfants P0/P1 avec critères d'acceptation. Les issues sont liées à l'epic.

Setup

Créer le PRD de test dans output/ :

output/2026-04-28-feature-recherche-avancee.md (voir evals/fixtures/pm-epic-prd-happy.md)

Structure attendue du PRD :

# Recherche avancée dans le journal des décisions

## Problème
Les PMs ne retrouvent pas les décisions passées. Perte de temps estimée : 45 min/semaine.

## Objectifs
Permettre la recherche plein texte et filtrée par tag, date, auteur.

## Hors périmètre
Pas de recherche sémantique (IA) en V1.

## User stories
- En tant que PM, je veux chercher par mot-clé pour retrouver une décision en < 10 s.
- En tant que PM, je veux filtrer par date pour explorer les décisions d'un trimestre.

## Exigences

### P0 — Recherche plein texte
La barre de recherche indexe le titre et le corps de toutes les décisions.

### P0 — Filtres combinables
L'utilisateur peut combiner filtre date + filtre tag.

### P1 — Mise en évidence des résultats
Les termes recherchés sont surlignés dans les résultats.

## Critères d'acceptation
- P0 Recherche plein texte : résultat en < 1 s pour un corpus de 1 000 décisions.
- P0 Filtres : la combinaison date + tag retourne uniquement les décisions correspondantes.
- P1 Mise en évidence : les occurrences sont surlignées en jaune.

## Métriques de succès
- Temps moyen de recherche d'une décision : < 30 s (baseline : 45 min).
- Taux d'adoption de la barre de recherche : > 70 % des PMs en semaine 4.

Prompt

/pm-epic output/2026-04-28-feature-recherche-avancee.md

Pass criteria (rubric)

Un epic est créé dans beads avec :
- Titre : « Recherche avancée dans le journal des décisions ».
- Description incluant une section ## Success Criteria avec les métriques verbatim.
Au moins 3 issues enfants sont créées (2 P0 + 1 P1).
Chaque issue enfant a un champ --acceptance non vide correspondant à ses critères.
Chaque enfant est lié à l'epic via bd dep add.
La note PRD: [[2026-04-28-feature-recherche-avancee]] est ajoutée à l'epic et aux enfants.
Le récapitulatif final liste l'epic ID et les IDs enfants.
bd lint est lancé et ses erreurs éventuelles sont rapportées sans correction automatique.
Aucune écriture dans wiki/ ou raw/.

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

1mo ago First seen · 91 lines · 0 tokens per session scan A 5aed0d3b9eae

Subscribe to this mod's changes

pm-epic-01-happy is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 847 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.

Claude Code LLM Project management claude-code-marketplace claude-code-plugin knowledge-management obsidian

status

Show memex statistics and status including projects, memos, and pending items.

linxule/memex-plugin · 15 tokens

factory

Run one pass of the ticket queue — scan the tracker for human-authorized tickets, claim one, and route it to the right workflow (spec a raw ticket, groom the backlog, hunt a bug, or build an approved spec in its own worktree via /sonu:build). You are the trigger; there is no daemon. Never merges and never authorizes…

PrabhdeepSingh/claude-plugins · 108 tokens

pm-epic-01-happy