Tlc Plan
Turns a request, ticket, PRD, design or thread into one plan a human approves and a...
Install
npx skills add tech-leads-club/agent-skills --skill tlc-plan -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 1,585 tokens
- Runs scripts
- Yes, review before use
What it does
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), for a standalone design document, or when nobody has decided what to build.
TLC Plan
Ask until nothing is the builder's to decide. Write it down so a stranger can build it.
┌─────┐ ┌───────┐ ┌──────┐ ┌─────────┐
│ ASK │ → │ SHAPE │ → │ CHECK│ → │ APPROVE │ → tlc-implement
└─────┘ └───────┘ └──────┘ └─────────┘
The common failure of a coding agent is a requirement that never became an obligation, followed by a completion claim. It starts here: a gray area the plan settled by guessing, a capture treated as a suggestion, a sentence of the request that landed nowhere. This skill produces the one document a human reads and objects to before any code exists, and it is the whole brief for whoever builds, often a different agent with none of this conversation.
