Tlc Spec Lean

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.

7,177 stars 568 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tech-leads-club/agent-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tech-leads-club/agent-skills --skill tlc-spec-lean
Manual install
git 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-spec-lean ~/.claude/skills/tlc-spec-lean

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Tech Lead's Club - Spec, Lean

Freeze what must be true. Free the build. Have someone who did not build it look. Derived from
tlc-spec-driven 3.3.0 (Felipe Rodrigues), tlc-plan, and tlc-implement.

```
┌──────┐   ┌───────┐   ┌────────┐
│ PLAN │ → │ BUILD │ → │ REVIEW │
└──────┘   └───────┘   └────────┘
 a human    slice by    a fresh sub-agent, then one fix pass
            slice
```

The common failure of a coding agent is a requirement that never reached the work, followed by a
completion claim. Most of it is decided before any code: a product decision nobody asked, a
sentence of the request no criterion carries, a rule left where no test reaches. So the budget
goes into one plan a human approves, and into one reader who did not write the code. There is no
task breakdown, no checklist of proofs and no gate after the build: the builder takes the plan's
slices one at a time, end to end, and works as it sees fit inside each.

## Rules

These hold even if no reference file is read.

1. **Every product decision is asked before the plan is presented**, with your recommendation.
   An assumption saves no question. Answers are not the approval: the plan that holds them is
   presented again. The user's approval is written in plan.md as
   `**Approved**: <date> - user: "<their words>"` - never one the user did not give.
2. **Rules run where the repo's tests reach.** What changes an outcome - including filtering,
Read the full skill on GitHub

Details

Skill name
tlc-spec-lean
Path
packages/skills-catalog/skills/(development)/tlc-spec-lean/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Tlc Spec Lean skill do?

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.

How do I install the Tlc Spec Lean 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 Spec Lean popular?

It lives in tech-leads-club/agent-skills, which has 7,177 GitHub stars and 568 forks.

Related skills

Frontend Design

7.2k

tech-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).

Frontend & DesignIn 1 list568

Web Design Guidelines

7.2k

tech-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).

Frontend & Design568

AI Cold Outreach

7.2k

tech-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.

AI, LLMs & AgentsIn 1 list568

Audit Reference Originality

7.7k

MengTo/Skills

Audit a website or digital experience against its supplied source references for originality and plagiarism risk. Use when Codex must compare current or historical site output with reference pages, capture packs, screenshots, copy, brands, numbers, images, assets, videos, layouts, motion, or code; raise evidence-backed red flags; distinguish common visual grammar from distinctive copying; and propose concrete fixes without making unsupported legal claims.

Software Development885

Tlc Spec Driven

7.2k

tech-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

Software Development568

Audit Verify Explain Grade 5

7.7k

MengTo/Skills

Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language. Use when the user asks to review, audit, check, verify, explain a change, explain a fix, summarize test results, validate whether something works, or translate technical findings into plain language for non-technical readers.

Software Development885

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.