pm-tech-spec-review SKILL.md skillA
pm-tech-spec-review from vandanaajaydubey111/great-pm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vandanaajaydubey111/great-pm/pm-tech-spec-review@git:20260721.86de099Pins git:20260721.86de099 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vandanaajaydubey111/great-pm
- Path
skills/pm-tech-spec-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260721.86de099, committed Jul 21, 2026
- Size
- 4,989 bytes
- Repository stars
- 3
- License
- MIT
Review an engineering technical spec through a PM lens — does it cover every PRD requirement, does it preserve user/UX intent, does it quietly add or drop scope, what are the product risks, what's missing for launch. Produces a priority-tagged findings list + clarifying questions for engineering. Use after eng drafts a tech spec / design doc / architecture proposal and before code lands.
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
# PM-lens Technical Spec Review Engineers write specs to answer "how do we build it?" A PM-lens review answers a different question the spec rarely asks itself: **"does this build still deliver what we promised the user, all of it, and nothing we didn't agree to?"** This sits between PRD sign-off and implementation — the cheapest place to catch a scope drift or a lost requirement. This is distinct from: - **Code review** (does the code work / is it well-built) — that's `code-reviewer`. - **PRD clarity check** (is the PRD itself complete/testable) — that's `prd-authoring` / spec-reviewer's mechanical pass. - This skill: **does the engineering plan honour the PRD's product intent.** ## Inputs - The technical spec / design doc / architecture proposal / API shape. - The original PRD or requirements it claims to implement. - The success metrics the feature is meant to move (if defined). ## The review lenses Run the spec against each lens. Every finding gets a **priority tag**: `P0` (blocks build — a requirement is lost or intent is broken), `P1` (must resolve before launch), `P2` (worth raising, not blocking). **1. Requirements coverage matrix** …
Read the whole file at its exact version.
How to install
mdr add vandanaajaydubey111/great-pm/pm-tech-spec-review@sha256:a6457db448a32a36The line at the top of this page pins the label git:20260721.86de099, 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_bxcqtiefbyq7jesq)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 21, 2026.
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 (4989 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
vandanaajaydubey111/great-pm · 3 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bxcqtiefbyq7jesq GET https://markdownregistry.com/api/v1/resolve?ref=vandanaajaydubey111/great-pm/pm-tech-spec-review GET https://markdownregistry.com/api/v1/blob/a6457db448a32a361d4a6477144f2ed9029817b73c7334d1b596ded693cad039
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 vandanaajaydubey111/great-pm
Every file in vandanaajaydubey111/great-pm