tlc-spec-driven

Plans and implements features through adaptive Specify, Design, Tasks, and Execute phases with deterministic validation scripts.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JosueTeo220/SEAZONE.TEST.FRONT --skill tlc-spec-driven-josueteo220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/JosueTeo220/SEAZONE.TEST.FRONT/tree/main/.cursor/skills/tlc-spec-driven
Command: npx skills add https://github.com/JosueTeo220/SEAZONE.TEST.FRONT --skill tlc-spec-driven-josueteo220

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Feature work with AI agents often drifts: vague requirements, skipped tests, batched commits, and self-approved implementations. This Skill enforces a spec-driven workflow where requirements are written in testable EARS notation, tasks are atomic with one Conventional Commit each, and an independent Verifier (author != verifier) validates the result with evidence-or-zero rules before anything is declared done. ## Core Features & Use Cases - Adaptive 4-Phase Pipeline: Specify, Design, Tasks, Execute, with depth auto-sized by complexity so small changes skip ceremony and large features get full specs, designs, and task breakdowns. - Deterministic Validation Scripts: Python scripts enforce structural gates for specs, tasks, commit messages, and completion state, so quality rules are checked by code rather than model memory. - Independent Verifier and Lessons Layer: A fresh verifier sub-agent runs spec-anchored outcome checks plus a mutation-based discrimination sensor, then distills grounded failures into a self-improving project-local lessons playbook. - Use Case: Ask the agent to specify and implement a new API endpoint; it writes a traceable spec, breaks work into atomic tasks, commits each task separately, and produces a validation report citing file:line evidence for every acceptance criterion. ## Quick Start Ask the agent to specify and implement your next feature using the spec-driven workflow, for example by saying "specify feature: add password reset endpoint".

Frequently Asked Questions about tlc-spec-driven

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and implement a feature with spec-driven development?

Trigger the Specify phase with a request like "specify feature: X". The skill writes testable requirements in EARS notation, optionally produces a design and atomic task breakdown, then executes each task with its own gate check and Conventional Commit.

How does the skill verify that an implementation matches the spec?

After the last task, an independent Verifier sub-agent re-derives coverage from the spec using evidence-or-zero rules, runs a discrimination sensor that injects behavior-level mutations to confirm tests catch them, and writes a PASS/FAIL validation report with file:line evidence.

Does the spec-driven workflow work with any programming language or framework?

Yes, the workflow is stack-agnostic and tool-agnostic. The shipped validation scripts are pure standard-library Python with zero dependencies, and the spec, tasks, and commit conventions apply to any codebase.

When should I not use this spec-driven skill?

Do not use it for pure architecture decomposition analysis or standalone technical design documents, as stated in its own description. It is built for planning, implementing, and validating features end to end.

What commit message format does the skill enforce?

It enforces Conventional Commits 1.0.0 via the check_commit.py script, validating type, scope, lowercase imperative description, and BREAKING CHANGE footers. It can optionally be wired as a git commit-msg hook.

How does the lessons layer improve future feature work?

The Verifier distills grounded failures such as surviving mutants or spec-precision gaps into one-sentence lessons via lessons.py. Lessons promote from candidate to confirmed after recurring across distinct features and are loaded at Specify and Design time.