Verified:GitHub

tlc-spec-driven

Manage software projects through Specify, Design, Tasks, and Implement+Validate phases.

2|Updated Feb 8, 2026

Search Tags:#task management #project planning #software architecture #agile development #spec-driven development #ai coding assistant

Ready to run

npx skills add https://github.com/barateza/mcp-plesk-unified --skill tlc-spec-driven-barateza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/barateza/mcp-plesk-unified/tree/main/.github/skills/tlc-spec-driven
Command: npx skills add https://github.com/barateza/mcp-plesk-unified --skill tlc-spec-driven-barateza

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms how AI agents approach software projects by enforcing a structured methodology (Spec-Driven Development) that ensures every line of code is backed by clear specifications, leading to precise planning, granular execution, and complete traceability.

Core Features & Use Cases

Structured Project Planning: Guides users through specifying requirements, designing architecture, breaking down work into atomic tasks, and implementing with verification.
Session Continuity: Persists project state, decisions, and blockers across sessions, allowing for seamless pausing and resuming of work.
Use Case: A developer can use this Skill to initialize a new project, define its features, break down a complex feature into small, manageable tasks, and then have the AI implement and validate each task, ensuring the final product meets all specifications.

Quick Start

Use the tlc-spec-driven skill to initialize a new project by saying "Initialize project".

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 software architecture using spec-driven development?▼

Spec-driven development planning is facilitated through a four-phase methodology: Specify, Design, Tasks, and Implement+Validate. This approach manages project documentation, feature specifications, and task breakdowns to ensure every line of code is backed by clear specifications.

What is the best way to break down complex features into manageable tasks for AI coding?▼

Breaking down complex features is handled during the Tasks phase of the methodology. It decomposes features into atomic tasks with explicit dependencies, ensuring granular execution and complete traceability before the AI implements and validates each component.

Can I resume project planning and task execution across multiple sessions?▼

Yes, project planning and task execution can be resumed across multiple sessions. The methodology persists project state, architectural decisions, and blockers, allowing for seamless pausing and resuming of software development workflows.

Does spec-driven development work for brownfield projects with existing code?▼

Yes, spec-driven development works for brownfield projects. The methodology supports brownfield analysis, enabling you to specify requirements and design architecture for existing codebases rather than just initializing new projects.

How do I initialize a new project to start structured software development?▼

To initialize a new project for structured software development, you simply issue the initialize project command. This triggers the methodology to set up the initial project state, ready for you to define features and specify requirements.

Is the spec-driven methodology tied to a specific tech stack or framework?▼

No, the spec-driven methodology is stack-agnostic. It supports stack-agnostic development workflows, meaning you can apply the structured planning and implementation phases regardless of your chosen programming languages or frameworks.