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 theagenticguy/erpaval --skill product-discoverygit clone --depth 1 https://github.com/theagenticguy/erpavalWrote 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/theagenticguy/erpaval/product-discovery)<a href="https://agentmods.dev/skills/theagenticguy/erpaval/product-discovery"><img src="https://agentmods.dev/badge/skills/theagenticguy/erpaval/product-discovery.svg" alt="Measured on agentmods" 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.00242 | $0.02716 |
| Opus 5 | $0.00121 | $0.01358 |
| Sonnet 5 | $0.00048 | $0.00543 |
| Haiku 4.5 | $0.00024 | $0.00272 |
Grade A, and why
product-discovery 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slash-command argument convention. Kiro auto-exposes every skill as a slash command. When invoked as
/product-discovery <source>, the body's$ARGUMENTSsubstitution resolves to the source path or topic. Typical sources are a path to raw content like a brief, notes, or tickets, or a one-line topic. The argument is optional. With no arguments the orchestrator prompts the user.
Contents
| Reference | When to load |
|---|---|
references/orchestrator.md |
Running the pipeline. Five routes, parallel Phase 2, critic review, deliver. |
references/write-protocol.md |
Canonical write-protocol block. Copied into every subagent prompt. |
references/frameworks/INDEX.md |
Routing guide. Discovery and spec decision tables. Composition rules. |
references/frameworks/*.md |
Per-framework files. One per framework. |
references/methodology/discovery-rounds.md |
Six-phase discovery methodology. |
references/inference-heuristics.md |
Signal-to-inference tables for the PRD-route Intent Profile. |
references/quality/prd.md |
Per-section PRD quality bar. Cross-section consistency checks. |
references/roles/product-analyst.md |
PRD route. Vision, personas, user stories, IA, milestones. |
references/roles/system-architect.md |
PRD route. NFRs, data models, API contracts, edge cases. |
references/roles/research-scout.md |
PRD route. Market context and open questions. |
references/roles/discovery-lead.md |
Discovery-round route. Problem framing and Double Diamond cadence. |
references/roles/hmw-framer.md |
HMW-only route. Also the hard-dep entry point for erpaval CL-RIGOR fuzzy. |
references/roles/jtbd-interviewer.md |
JTBD-only route. Job stories from PM-provided source material. |
references/roles/ears-specifier.md |
EARS-only route. Also the hard-dep entry point for erpaval CL-RIGOR contract-unclear. |
references/roles/prd-synthesizer.md |
PRD route Phase 3. Composes the final PRD from three parallel work logs. |
references/roles/discovery-critic.md |
Phase 3.5 critic. Rubric-graded review of any synthesized artifact. |
assets/prd-template.md |
15-section PRD skeleton with [FILL] markers. |
assets/worklog-skeleton.md |
Per-role work-log skeleton with embedded write-protocol. |
assets/discovery-memo.md |
Discovery-round output shape. |
assets/double-diamond-workbook.md |
Double Diamond four-stage workbook. |
assets/hmw-skeleton.md |
HMW brainstorms file. Lives at brainstorms/NNN-<slug>-requirements.md. |
assets/jtbd-skeleton.md |
JTBD job-stories file. |
assets/ears-spec-skeleton.md |
EARS spec file. Lives at specs/NNN-<slug>/spec.md. |
What ships with it
27 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/discovery-memo.md 4.6 KB
- assets/double-diamond-workbook.md 4.1 KB
- assets/ears-spec-skeleton.md 2.2 KB
- assets/hmw-skeleton.md 1.5 KB
- assets/jtbd-skeleton.md 3.3 KB
- assets/prd-template.md 12 KB
- assets/worklog-skeleton.md 5.8 KB
- references/frameworks/ears.md 5.4 KB
- references/frameworks/gherkin.md 4.5 KB
- references/frameworks/how-might-we.md 4.6 KB
- references/frameworks/INDEX.md 7.9 KB
- references/frameworks/jtbd-job-stories.md 4.1 KB
- references/frameworks/user-stories-invest.md 4.0 KB
- references/inference-heuristics.md 9.2 KB
- references/methodology/discovery-rounds.md 6.2 KB
- references/orchestrator.md 19 KB
- references/quality/prd.md 5.2 KB
- references/roles/discovery-critic.md 5.7 KB
- references/roles/discovery-lead.md 4.7 KB
- references/roles/ears-specifier.md 6.0 KB
- references/roles/hmw-framer.md 5.6 KB
- references/roles/jtbd-interviewer.md 5.0 KB
- references/roles/prd-synthesizer.md 6.1 KB
- references/roles/product-analyst.md 4.3 KB
- references/roles/research-scout.md 7.1 KB
- references/roles/system-architect.md 6.4 KB
- references/write-protocol.md 1.8 KB
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 · 213 lines · 242 tokens per session scan A 68b7f3e1cd46
product-discovery is a skill published in the GitHub repository theagenticguy/erpaval (28 stars, last pushed 3mo ago), licensed MIT. It adds 242 tokens to every session and 2,716 once invoked, about $0.0012 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-30.
Other skills, from other repositories
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
req-analyze
A requirements-analysis tool that breaks a problem into needs, stakeholders, and priorities before a technical solution is chosen.
recap-ask
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap- .md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).