t-prd-publish
After implementation and acceptance, summarize the draft PRD against delivered facts, then revise the existing formal PRD.
npx skills add timzaak/web-dev-skills --skill t-prd-publish --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 发布总结与正式文档修正 运行时边界统一参考:`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 需求来源边界统一参考:`${CLAUDE_PLUGIN_ROOT}/protocols/requirement-source-contract.md` 决策连续性和用户决策暴露统一参考:`${CLAUDE_PLUGIN_ROOT}/protocols/decision-continuity-contract.md` 若草稿、正式 PRD、用户故事或规范之间冲突,以明确澄清为继续条件:停止、说明冲突并等待决策。 ## 目标 在实现、测试和 Demo 验收完成后,基于 `.ai/prd/<domain>/<feature>.md` 草稿、`.ai/user-stories/<domain>/<feature>.md` draft
What does the t-prd-publish skill do?
After implementation and acceptance, summarize the draft PRD against delivered facts, then revise the existing formal PRD.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-prd-publish --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.