t-dream

Organize PRDs, user stories, designs, tasks, and demos into current project context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes and realigns PRDs, user stories, design/task docs, implementation facts, and project structure so the target project keeps a clean current context instead of accumulating stale or misleading information. Use when asked to audit documentation drift, structure drift, traceability gaps, whether PRD/code/test/demo directory organization and module boundaries are reasonable, or to merge/prune/rewrite PRDs into concise current authority sources.

Core Features & Use Cases

  • Build a traceability view from PRD -> user stories -> design/task -> code -> tests/demo.
  • Identify and reduce documentation drift, stale terms, conflicting rules, and outdated concepts.
  • Assess PRD and directory structures for reasonableness and boundary clarity.
  • Merge/prune/rewrite PRDs into concise authority sources to maintain current governance.

Quick Start

Run t-dream on the target project to audit context and generate a governance report.

Frequently Asked Questions about t-dream

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

FAQPage Schema
How do I audit documentation drift in PRDs and project artifacts?

Audit documentation drift by organizing PRDs, user stories, design docs, and implementation facts into a current context. This identifies stale terms, conflicting rules, and outdated concepts across your project artifacts.

What is the best way to build traceability from PRDs to code and tests?

Build traceability by mapping the full path from PRDs to user stories, design tasks, code, and tests. This ensures boundaries and acceptance criteria are clearly defined and maintained across all artifacts.

How do I merge and prune outdated PRDs into a single source of truth?

Merge and prune outdated PRDs by rewriting them into concise, living authority sources. This maintains current governance and prevents your project from accumulating misleading information.

Can I assess directory structure and module boundaries against my PRD?

Assess directory structure and module boundaries by checking whether PRD, code, test, and demo organization is reasonable. This identifies structure drift and ensures boundary clarity across your project.

When should I use a project context governance audit?

Use a project context governance audit when you need to realign PRDs, user stories, and task docs to prevent stale information. It ensures traceability gaps and structure drift are addressed before they mislead the team.

Does traceability gap analysis work for existing design and demo directories?

Traceability gap analysis works across existing design and demo directories by evaluating whether their organization aligns with current PRDs. It detects conflicting rules and outdated concepts within the project structure.