Tlc Prd
Interviews an idea into a PRD file covering situation, problem, success, boundary, and...
Install
npx skills add tech-leads-club/agent-skills --skill tlc-prd -g -a claude-code -y- Repository
- tech-leads-club/agent-skills7.1k
- Category
- Design
- Updated
- 3d ago
- License
- CC-BY-4.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Interviews an idea into a PRD file covering situation, problem, success, boundary, and journey states, and stops before any technical design. Use when the user says "write the PRD", "create the PRD", "PRD", "product spec", "product requirements", "tlc-prd", or "what does the product need to decide". Do NOT use for designing a solution, choosing technology, publishing the document, or cutting the PRD into tasks.
TLC PRD
Find out where this effort actually is. Understand the problem. Decide whether to solve it. Write that down as a PRD file, and stop.
SITUATION ────→ PROBLEM ───────→ VERDICT ───────→ FILE
(where this (no solution (a stop, or a (.prd/<slug>.md,
effort is) proposed yet) short record) nothing else)
These are not a script, they are the prerequisite order. Ask whatever is answerable given what is settled, and stop when nothing answerable is left. Whether has where we are as a prerequisite. Marching the sections as a form is how a PRD asks an effort that never shipped what its problem costs today.
The failure that matters is converging early: proposing a solution on turn two, hearing "sure", and manufacturing a decision. Everything below exists to make that harder.
The artifact is one Markdown file a product person can read and hand to someone else without having been in the room. It records the bet. It does not record how to build it.
