t-prd-publish

Summarize draft PRD discrepancies against delivered artifacts and update the formal PRD.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-prd-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-prd-publish
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-prd-publish
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-prd-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a feature is implemented, tested, and demonstrated, this skill summarizes the draft PRD against delivered facts and updates the formal PRD accordingly, ensuring documentation stays aligned with reality and releases.

Core Features & Use Cases

  • Diff and summarize: compare draft PRD with actual delivery artifacts and extract the gaps that affect scope or wording.
  • Publish-ready revision: generate and apply updates to docs/prd/<domain>/<feature>.md, creating the formal PRD if missing and updating the PRD index when needed.
  • Traceability: preserve references to user stories, designs, and test results so revisions are fully evidenced.

Quick Start

Run /t-prd-publish [feature] to publish the draft PRD and refresh the formal PRD with delivered evidence.

Frequently Asked Questions about t-prd-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update an official PRD to match the delivered feature scope?

To update an official PRD, compare the draft against delivered artifacts to summarize discrepancies, then generate and apply revisions to the docs/prd directory while preserving valid existing text.

What is the best way to align a draft PRD with delivered artifacts?

Aligning a draft PRD involves reading user stories and designs, verifying there are no conflicts with actual delivery, and producing a publish-ready revision that updates the formal documentation with evidence.

How do I publish a PRD revision and preserve traceability to user stories?

Publishing a PRD revision updates the formal document and preserves references to user stories, designs, and test results, ensuring revisions are fully evidenced and aligned with reality.

Can I create a formal PRD if the official documentation file is missing?

Yes, you can create a formal PRD if the file is missing. The process generates and applies updates to the docs/prd path and updates the PRD index when needed to establish the official record.

Does publishing a PRD overwrite the valid existing text in official docs?

No, publishing a PRD does not overwrite valid existing text. The process scopes and aligns the draft with the official document specifically to preserve existing valid content during the update.

When do I need to refresh the formal PRD after feature implementation?

You need to refresh the formal PRD after a feature is implemented, tested, and demonstrated, ensuring documentation stays aligned with reality and releases by summarizing delivery gaps.