tlc-plan SKILL.md skillA
tlc-plan from tech-leads-club/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tech-leads-club/agent-skills/tlc-plan@v1.1.1Pins v1.1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(development)/tlc-plan/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.1, committed Oct 31, 2026
- First version recorded
- Sep 9, 2026
- Size
- 7,349 bytes
- Repository stars
- 7,124
- License
- a license file GitHub does not identify
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. ## Rules 1. Every criterion is one observable outcome with a concrete value - a status code, a field, a bound, a label - that one run settles. "Gracefully", a percentile or "the columns exist" is not a criterion. 2. Ask every gray area before presenting the plan: a decision that is the user's, has more than one defensible answer, and is not settled by the code. An assumption never stands in for a question …
Read the whole file at its exact version.
How to install
mdr add tech-leads-club/agent-skills/tlc-plan@sha256:c7ce0c204bab59adThe line at the top of this page pins the label v1.1.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_w6wawua3b4czuxvw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 9, 2026 and Oct 31, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.1 latest | 2026-10-31 | b9caf0c | 7,349 B | A | view · diff |
| v1.1.0 | 2026-10-26 | eec0410 | 7,262 B | A | view · diff |
| v1.0.0 | 2026-10-25 | 3be478b | 6,911 B | A | view · diff |
| v0.2.0 | 2026-09-10 | bfd1c0d | 21,089 B | A | view · diff |
| v0.1.1 | 2026-09-09 | f68d2e5 | 15,501 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7349 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tech-leads-club/agent-skills · 7,124 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w6wawua3b4czuxvw GET https://markdownregistry.com/api/v1/resolve?ref=tech-leads-club/agent-skills/tlc-plan GET https://markdownregistry.com/api/v1/blob/c7ce0c204bab59adb578adadea0e6a92a8486efa87b69ac5306f37ab16fe2fd2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.