t-prd

Name: t-prd
Availability: InStock
Author: timzaak

Create and update PRD drafts with HTML previews for new features.

64|6|Updated Apr 17, 2026

Search Tags:#prd #workflow-automation #user-stories #pr-draft #html-preview #decision-brief #domain-scoping

Ready to run

npx skills add https://github.com/timzaak/web-dev-skills --skill t-prd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: t-prd
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-prd
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update PRD drafts and HTML previews for new features, aligning decision briefs, user stories, and formal PRDs into a single, traceable workflow.

Core Features & Use Cases

Draft PRD creation or updates under .ai/prd/<domain>/[feature].md with linked user stories and decisions.
HTML Preview generation under .ai/preview/<domain>/[feature].html for quick stakeholder review.
Reference flow integration: consume Decision Briefs and Tech Research to shape PRD content and boundary definitions.
Gatekeeping and handoff readiness: ensure decisions, scope, and acceptance criteria are captured before handoffs to design or engineering.

Quick Start

Run /t-prd <feature> to create or update a PRD draft and generate its HTML Preview for review.

Frequently Asked Questions about t-prd

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

FAQPage Schema

How do I create a PRD draft and generate an HTML preview for a new feature?▼

To create a PRD draft and HTML preview, run the command targeting a specific feature. The workflow automates draft creation under `.ai/prd/` and generates an HTML preview under `.ai/preview/` for stakeholder review.

How does PRD workflow automation align user stories and decision briefs?▼

PRD workflow automation aligns user stories and decision briefs by consuming them as reference inputs. It maps existing user stories and decision briefs to the PRD content, ensuring domain scope and boundary definitions are consistently enforced.

What is the best way to maintain traceability between PRDs and user stories?▼

The best way to maintain traceability is to enforce linkages between PRD drafts and existing user stories within the workflow. This ensures scope, acceptance criteria, and decisions are captured before handing off to design or engineering teams.

Do I need decision briefs and tech research to start drafting a PRD?▼

Yes, decision briefs and tech research are consumed as reference inputs to shape PRD content and define boundaries. Integrating these references ensures the generated PRD maintains proper domain scope and alignment with prior decisions.

Can I update an existing PRD draft without losing previous domain scope and linkages?▼

Yes, updating an existing PRD draft preserves domain scope and linkages. The workflow applies to features mapped to existing user stories and decisions, ensuring updates maintain traceability and do not break prior boundary definitions.

When should I use an automated PRD generator for handoff readiness?▼

Use an automated PRD generator when you need gatekeeping before design or engineering handoffs. It ensures all decisions, scope definitions, and acceptance criteria are formally captured and previewed for quick stakeholder review.