Tlc Prd
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.
Install
/plugin marketplace add tech-leads-club/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tech-leads-club/agent-skills --skill tlc-prdgit clone --depth 1 https://github.com/tech-leads-club/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/packages/skills-catalog/skills/(development)/tlc-prd ~/.claude/skills/tlc-prdPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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. ## Critical rules 1. **No technology is proposed.** Not a library, not a provider, not a pattern, not a schema, not an API. If the problem section argues for one, the framing is already a solution. Knowing what already exists is allowed: a commitment, a substitute people use today, a constraint. Proposing is not.
Details
- Skill name
tlc-prd- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(development)/tlc-prd/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Tlc Prd skill do?
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.
How do I install the Tlc Prd skill?
Claude Code plugin: /plugin marketplace add tech-leads-club/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tlc Prd popular?
It lives in tech-leads-club/agent-skills, which has 7,177 GitHub stars and 568 forks.
Related skills
Frontend Design
7.2ktech-leads-club/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit).
Web Design Guidelines
7.2ktech-leads-club/agent-skills
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).
AI Cold Outreach
7.2ktech-leads-club/agent-skills
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
Tlc Spec Driven
7.2ktech-leads-club/agent-skills
Feature planning and implementation with 4 adaptive phases (Specify, Design, Tasks, Execute). Auto-sizes depth by complexity. Asks every product decision before the spec is approved, writes testable requirements in EARS notation, atomic tasks with a gate and a commit each, and one check per criterion with the test that proves it. Captures that come with the request bind, and each screen is judged against them. Ships deterministic Python scripts so the gates are enforced by code, not memory; the project's own tests run once at the end, and an independent Verifier (author != verifier) judges eac
Tlc Plan
7.2ktech-leads-club/agent-skills
Turns a request, ticket, PRD, design or thread into one plan a human approves and a builder can act on without the conversation: asks every gray area until no product decision is left to the builder, then writes the problem, EARS criteria with concrete values, the path and the data it touches (drawn in mermaid), the interface, and only the decisions that are hard to reverse. Captures that come with the request bind. Use when the user says "plan this", "plan feature", "specify feature", "write the plan", "cut this PRD into tasks", or "tlc-plan". Do NOT use to implement (that is tlc-implement),
Tlc Spec Lean
7.2ktech-leads-club/agent-skills
Spec-driven feature work that freezes what must be true and frees how it is built: one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors; then the build, one vertical slice at a time, each committed; then one review by a fresh sub-agent and one fix pass. Use when the user says "tlc-spec-lean", "plan feature", "specify feature", "build this plan", or "review this work". Do NOT use for standalone design documents unattached to a feature, architecture decomposition analysis, or work that already has a task list or checklist to execute.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.