t-prd-check
Validate draft PRD, published PRD baseline, and user stories for quality and consistency.
npx skills add timzaak/web-dev-skills --skill t-prd-check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PRD 草稿与 User Story Quality Check 运行时边界统一参考:`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 需求来源边界统一参考:`${CLAUDE_PLUGIN_ROOT}/protocols/requirement-source-contract.md` 决策连续性和用户决策暴露统一参考:`${CLAUDE_PLUGIN_ROOT}/protocols/decision-continuity-contract.md` ## 目标 - 验证 `.ai/prd` PRD 草稿完整性和规范性 - 评估用户故事质量(INVEST 原则、GWT 格式) - 检查 PRD 与用户故事的一致性 - 检查 PRD 草稿与 `docs/prd` 已发布基线是否存在未说明冲突 - 检查 `.ai/user-sto
What does the t-prd-check skill do?
Validate draft PRD, published PRD baseline, and user stories for quality and consistency.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-prd-check --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 timzaak/web-dev-skills, a repository with 55 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.