tlc-spec-driven

Plans and implements software projects through adaptive specify, design, tasks, and execute phases.

1|Updated Apr 25, 2025
One-click install
npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill tlc-spec-driven-gabr1elaugus700
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/Gabr1elaugus700/WorkaPool/tree/main/.cursor/skills/tlc-spec-driven
Command: npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill tlc-spec-driven-gabr1elaugus700

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding agents often jump straight into code without clear requirements, producing scope creep, untraceable changes, and lost context between sessions. This Skill structures project and feature work into an adaptive pipeline that applies full planning rigor to complex features while skipping ceremony for small fixes. ## Core Features & Use Cases - Adaptive 4-Phase Pipeline: Specify, Design, Tasks, and Execute phases that auto-size based on scope, from quick fixes (≤3 files) to complex multi-component features. - Requirement Traceability: Captures testable acceptance criteria with unique IDs (e.g., AUTH-01) and tracks them from spec through design, tasks, and atomic Conventional Commits. - Persistent Memory & Handoff: Maintains STATE.md for decisions, blockers, and deferred ideas, plus pause/resume handoffs so work continues seamlessly across sessions. - Use Case: Ask the agent to map an existing codebase into 7 brownfield documents (stack, architecture, conventions, concerns), then specify a new authentication feature, break it into atomic tasks, and implement each with verification and one commit per task. ## Quick Start Tell the agent "Initialize project" to define your vision and roadmap, or say "Specify feature user-authentication" to begin planning a feature with traceable requirements.

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 an AI coding agent?

Say "Specify feature [name]" and the agent captures requirements with traceable IDs, optionally designs architecture, breaks work into atomic tasks, then implements each task with verification and one Conventional Commit per task.

How do I document an existing codebase before adding features?

Say "Map codebase" to generate 7 brownfield documents in .specs/codebase/ covering stack, architecture, conventions, structure, testing, integrations, and concerns like tech debt and fragile areas.

Does this workflow work with any tech stack or AI agent?

Yes, it is stack-agnostic and works with any language or framework. It has been tested with Claude Code, Cursor, GitHub Copilot, Antigravity, and Opencode, and works with any agent supporting custom instructions.

Can I use it for small bug fixes without full planning?

Yes, say "Quick fix: [description]" for changes touching up to 3 files. Quick mode skips the pipeline but still requires a verification step and an atomic Conventional Commit.

What happens if I close my session in the middle of a task?

Say "Pause work" before ending to create a HANDOFF.md with completed tasks, current progress, and next steps. In the next session, say "Resume work" to continue exactly where you left off.

When should I not use this spec-driven workflow?

Do not use it for architecture decomposition analysis or standalone technical design documents, which belong to dedicated architecture or design-doc skills. It also avoids forcing full phases on trivially small changes.