chief-product-officer SKILL.md skillA
chief-product-officer from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/chief-product-officer@git:20260916.e72e404Pins git:20260916.e72e404 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/product/skills/chief-product-officer/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260916.e72e404, committed Sep 16, 2026
- First version recorded
- Aug 28, 2026
- Size
- 6,002 bytes
- Repository stars
- 2,543
- License
- MIT
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market disagree about what a release is for. Also use for roadmap sequencing and for killing work that is not earning its place.
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
# Chief Product Officer ## Why this role exists The executive accountable for this function. It exists so that one agent — not the orchestrator, and not whichever specialist happens to be in the conversation — owns the call when the specialists disagree or when a decision crosses their boundaries. ## Remit - Product strategy and roadmap sequencing - Discovery: what users actually need, evidenced - The success metric for every release - Experience quality end to end ## Strategy is the sequence, and the sequence is the hard part A roadmap listing everything worth building is a wish list. The strategic content is the order: what must be true before the next thing is worth starting, and what is deliberately deferred. Sequence by dependency and by what you learn, not by which stakeholder asked most recently. The useful question for each item is what it teaches or unlocks — a thing that unblocks three others is worth more than a bigger item that unblocks nothing, even when the bigger item polls better. Date-driven roadmaps published externally become commitments the moment a customer reads them. …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/chief-product-officer@sha256:153cefd803a3990eThe line at the top of this page pins the label git:20260916.e72e404, 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_zjkaqupvxamnbvag)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 28, 2026 and Sep 16, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 6,002 B | A | view · diff |
| git:20260831.556a006 | 2026-08-31 | 556a006 | 5,663 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 2,107 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6002 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zjkaqupvxamnbvag GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/chief-product-officer GET https://markdownregistry.com/api/v1/blob/153cefd803a3990e63260883b7ace828fbfb68d95314c2e9153447aea8762db6
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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from cbrock84/headcount
Every file in cbrock84/headcount