Agent skill · AI & Agents

prd-implementation-precheck

Use this skill at Step 1 (PRD pre-check) and Step 2 (TDD alignment) of the v2 12-step SOP to find blockers and warnings in PRD / TDD before any implementation work begins. Produces a structured gap list pointing to missing scope boundaries, undefined acceptance criteria, unresolved cross-team dependencies, vague metrics, and stage breakdown gaps. Chinese trigger examples: "PRD 预检", "PRD 检查", "TDD 对齐检查", "需求文档审查", "PRD 缺口扫描", "Step 1", "Step 2". Do NOT use to write the PRD itself (use `prd` Skill), do NOT use as substitute for compliance precheck (Step 0 is separate). Success = zero blockers,

Bill Blasco95★ · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add charliehzm/medharness --skill prd-implementation-precheck --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Version: 1.0
Requires: Requires file read of PRD/TDD. No external services required.
Path: .claude/skills/prd-implementation-precheck/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 96 · +1 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PRD Implementation Precheck The Step 1 / Step 2 gate. Catches PRD / TDD ambiguity **before** OpenSpec is generated, so we don't have to retrofit later. ## Core mental model A PRD is implementation-ready when: - Every feature has a **defined boundary** (in/out of scope, both stated) - Every acceptance criterion has a **measurable test hook** - Every cross-team dependency has a **named owner** - E

More from medharness
All skills →
About this skill
What does the prd-implementation-precheck skill do?

Use this skill at Step 1 (PRD pre-check) and Step 2 (TDD alignment) of the v2 12-step SOP to find blockers and warnings in PRD / TDD before any implementation work begins. Produces a structured gap list pointing to missing scope boundaries, undefined acceptance criteria, unresolved cross-team dependencies, vague metrics, and stage breakdown gaps. Chinese trigger examples: "PRD 预检", "PRD 检查", "TDD 对齐检查", "需求文档审查", "PRD 缺口扫描", "Step 1", "Step 2". Do NOT use to write the PRD itself (use `prd` Skill), do NOT use as substitute for compliance precheck (Step 0 is separate). Success = zero blockers,

How do I install it?

Run `npx skills add charliehzm/medharness --skill prd-implementation-precheck --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From charliehzm/medharness, a repository with 96 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going