tlc-spec-driven

Manage projects with adaptive phase planning and persistent context across sessions.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/rodrigotoledo/trading-exchange --skill tlc-spec-driven-rodrigotoledo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/rodrigotoledo/trading-exchange/tree/main/packages/skills-catalog/skills/%28development%29/tlc-spec-driven
Command: npx skills add https://github.com/rodrigotoledo/trading-exchange --skill tlc-spec-driven-rodrigotoledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Problem: Teams struggle to plan, align, and execute multi-phase software initiatives without losing memory or traceability across sessions.

Core Features & Use Cases

  • Adaptive Phases: Specify, Design, Tasks, Execute scale depth automatically by complexity.
  • Traceable Artifacts: SPEC.md, ROADMAP.md, STATE.md, and per-task traceability to requirements.
  • Safe, Atomic Delivery: Atomic commits, session handoffs, and persistent memory for continuity across sessions.

Quick Start

Initialize a new project by running the TLC Spec-Driven workflow to create a project blueprint and begin the adaptive cycle.

Frequently Asked Questions about tlc-spec-driven

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

FAQPage Schema
How do I maintain project context and traceability across multiple coding sessions?

To maintain project context across sessions, use a spec-driven workflow that enforces persistent memory through traceable artifacts like SPEC.md, ROADMAP.md, and STATE.md. This approach ensures continuity by mapping each task back to its original requirements.

What is adaptive phase planning for software projects?

Adaptive phase planning is a project management approach where phases—Specify, Design, Tasks, and Execute—automatically scale their depth based on the complexity of the initiative. It enforces traceability and safe, atomic commits throughout the workflow.

How do I plan new features for an existing codebase without losing alignment?

You can plan new features for an existing codebase by mapping the current structure and running an adaptive cycle. This generates a project blueprint with per-task traceability to ensure all execution aligns with the original requirements.

Does a spec-driven workflow support atomic commits and session handoffs?

Yes, spec-driven workflows support safe, atomic delivery by enforcing atomic commits and session handoffs. This provides persistent memory for continuity, ensuring no progress or context is lost between multi-phase development sessions.

When do I need to use traceable artifacts like ROADMAP.md and STATE.md?

You need traceable artifacts like ROADMAP.md and STATE.md when managing multi-phase software initiatives that require strict alignment. They provide persistent context and track progress to prevent memory loss across sessions.