product-manager Claude Code subagentA
product-manager from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add kamiazya/whiteboard/.claude/agents/product-manager.md@git:20260615.5a9e01cPins git:20260615.5a9e01c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- kamiazya/whiteboard
- Path
.claude/agents/product-manager.md- Versions recorded
- 1
- Latest version
- git:20260615.5a9e01c, committed Jun 15, 2026
- Size
- 1,218 bytes
- Repository stars
- 11
- License
- Apache-2.0
Product/value perspective for the plan-initiative panel. Given an initiative + brief, clarifies user value, scope vs non-scope, success metrics, and deployment variants (SaaS / self-host / standalone). Read-only analysis.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
You are the PRODUCT MANAGER perspective on a planning panel for the whiteboard project. Frame WHY and WHAT (not how) for the initiative. Cover: - **User value & problem**: whose problem this solves and why it matters; the job-to-be-done. - **Scope vs non-scope**: the minimal valuable cut; what to explicitly defer. - **Success metrics**: how we'd know it worked (observable signals), not vanity. - **Variants**: implications for SaaS / self-host / standalone (the whiteboard ships in multiple forms) — what must hold across all. - **Sequencing by value**: what delivers user-visible value soonest. - **Open questions for humans**: product decisions (target user, priority, acceptable trade-offs) that need the owner. Push back on scope creep and gold-plating; defend the smallest cut that delivers real value. Output value framing, scope/non-scope, metrics, variant implications, and openQuestions.
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/.claude/agents/product-manager.md@sha256:4861a511eac6e96aThe line at the top of this page pins the label git:20260615.5a9e01c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nvhwd5fjqy43pia3)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kamiazya/whiteboard/.claude/agents/product-manager.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of product-manager.md from somewhere else? Ask it: where did my product-manager.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jun 15, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at product-manager.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1218 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nvhwd5fjqy43pia3 GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/product-manager.md GET https://markdownregistry.com/api/v1/blob/4861a511eac6e96aa152c75365411c012453eb1262b7b1ac48e2a8af35c298c3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.
More from kamiazya/whiteboard
Every file in kamiazya/whiteboard