t-decision

Evaluate feature readiness for the t-tools workflow and generate a Markdown decision brief.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams decide whether a feature should enter the t-tools workflow before technical research or PRD, ensuring early scope control and governance.

Core Features & Use Cases

  • Structured six-question decision framework that clarifies problem statements, alternatives, and kill criteria to guide verdicts.
  • Outputs a decision brief under .ai/decision/<feature>.md and an HTML preview under .ai/preview/decision/<feature>.html for traceability and stakeholder review.
  • Reads and incorporates context from existing PRD, user stories, tech research, and governance documents to ground the decision and prevent scope drift.

Quick Start

Run /t-decision <feature> to generate a decision brief and publish the HTML preview.

Frequently Asked Questions about t-decision

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

FAQPage Schema
What is a product decision gate in workflow governance?

A product decision gate is a structured checkpoint that evaluates evidence, scope, and problem alternatives to determine whether a feature should proceed to technical research or PRD creation.

How do I create a decision brief with evidence before starting tech research?

You create a decision brief by running the decision command on a feature, which evaluates existing user stories and governance context to output a Markdown brief and HTML preview.

Can I use existing PRD and user stories to inform feature gating decisions?

Yes, the decision process reads context from existing PRD, user stories, tech research, and governance files to ground the verdict and prevent scope drift before entering the workflow.

What's the best way to structure feature scope control for product management?

The best way to structure scope control is applying a six-question decision framework that clarifies problem statements, alternatives, and kill criteria to deliver explicit verdicts across related docs.

When do I need a structured decision brief for a product feature?

You need a structured decision brief when a feature requires early scope control and governance, ensuring stakeholders review traceable evidence before committing to technical research or PRD development.

Why does my product feature need a governance check before PRD creation?

A governance check is needed before PRD creation to ensure gating decisions are explicitly supported by evidence and scope considerations, preventing unvalidated features from entering the development workflow.