tlc-spec-driven

Plan and implement software projects with adaptive depth across four phases.

Updated Aug 3, 2025
One-click install
npx skills add https://github.com/edmilson-torres/wails-template --skill tlc-spec-driven-edmilson-torres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/edmilson-torres/wails-template/tree/main/.opencode/skills/tlc-spec-driven
Command: npx skills add https://github.com/edmilson-torres/wails-template --skill tlc-spec-driven-edmilson-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

TLC Spec-Driven helps teams plan and implement software projects with adaptive depth, ensuring clear scope, traceability, and high-quality commits.

Core Features & Use Cases

  • Specifies features with traceable IDs, auto-sizes Design and Tasks phases based on complexity, and executes with atomic commits.
  • Maps to existing codebases, plans roadmaps, and supports quick ad-hoc tasks, UAT, and session handoffs.

Quick Start

Give a feature description to start the adaptive workflow and see a complete plan from specification to execution.

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 features with traceable IDs and atomic commits?

Spec-driven project planning automates feature delivery by assigning traceable IDs and enforcing atomic commits throughout the development workflow. It auto-sizes the design and tasks phases based on complexity, ensuring clear scope and high-quality version control.

What is the best way to map existing codebases for project planning?

Mapping existing codebases during project planning involves analyzing the current architecture to plan roadmaps and establish persistent memory across sessions. This ensures future feature implementations align with the established code structure.

How does adaptive depth work in spec-driven project management?

Adaptive depth in spec-driven project management auto-sizes the design and tasks phases based on feature complexity. This allows the workflow to scale appropriately, supporting both quick ad-hoc tasks and detailed new project roadmaps.

Can I use spec-driven planning for quick ad-hoc tasks instead of full projects?

Spec-driven planning supports quick ad-hoc tasks alongside full project roadmaps. The adaptive workflow adjusts the planning depth based on the complexity of the feature description provided, preventing overhead for simple updates.

How do I maintain project traceability across multiple development sessions?

Maintaining project traceability across sessions requires persistent memory that links feature specifications to their execution. This is achieved by enforcing traceable IDs and atomic commits, ensuring continuous context during session handoffs and user acceptance testing.