Tlc Implement
Implements work already planned - a plan.md from tlc-plan, or a small ticket - by freezing it into checks with proofs, building, and proving every check with a script and an independent Verifier before declaring done. Use when the user says "implement this plan", "build this ticket", "implement this spec", "write the checks", "verify work", or "tlc-implement". Do NOT use when nobody has decided what to build, or to plan a feature that needs one (that is tlc-plan).
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-implementgit 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-implement ~/.claude/skills/tlc-implementPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# TLC Implement Freeze the obligations. Free the build. Prove it with someone who did not build it. ``` ┌────────┐ ┌───────┐ ┌────────┐ │ CHECKS │ → │ BUILD │ → │ VERIFY │ └────────┘ └───────┘ └────────┘ obligations yours always ``` The common failure of a coding agent is a requirement that never became an active obligation, followed by a completion claim. What works against it is a small, frozen, external obligation set and a verifier that is not the author, so the budget goes there and not into choreographing the model. How you build is yours. The input is an approved `.specs/features/<feature>/plan.md` from **tlc-plan** - approved means its `**Approved**: <date> - user: "<their words>"` line, which `validate_checks.py` requires - and it is the whole brief: you may have none of the conversation that produced it. A change under roughly three files with no one-way door needs no plan: write `checks.md` with an `## Intent` paragraph instead. Anything larger with no plan, or a plan with an open `blocks` question, goes back to **tlc-plan**. ## Rules These hold even if no reference file is read. Each one lives here; the references point back. 1. Every check is one observable claim with a concrete value plus the proof that settles it: a test or command whose exit code decides, or, for a state a capture draws, a picture of it judged against the capture (rule 9).
Details
- Skill name
tlc-implement- Repository
- tech-leads-club/agent-skills
- Path
packages/skills-catalog/skills/(development)/tlc-implement/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Tlc Implement skill do?
Implements work already planned - a plan.md from tlc-plan, or a small ticket - by freezing it into checks with proofs, building, and proving every check with a script and an independent Verifier before declaring done. Use when the user says "implement this plan", "build this ticket", "implement this spec", "write the checks", "verify work", or "tlc-implement". Do NOT use when nobody has decided what to build, or to plan a feature that needs one (that is tlc-plan).
How do I install the Tlc Implement 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 Implement 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 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 Discover
7.2ktech-leads-club/agent-skills
Thinks through new or large projects: turns a vague idea into a design doc with a clear product problem and the technical solution. Use when exploring a new project, planning or designing a big project or system, or asked for a "design doc". Do NOT use for clear features or projects (use tlc-spec-lean or tlc-spec-driven).
Tlc Prd
7.2ktech-leads-club/agent-skills
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.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.