tlc-spec-driven

Guide software projects through requirements, architecture, tasks, and verification phases.

Updated May 6, 2026
One-click install
npx skills add https://github.com/wilfoz/plan_game --skill tlc-spec-driven-wilfoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/wilfoz/plan_game/tree/main/.claude/skills/tlc-spec-driven
Command: npx skills add https://github.com/wilfoz/plan_game --skill tlc-spec-driven-wilfoz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines software project planning and execution by using a flexible, four-phase process that adapts to scope and complexity, reducing overhead and increasing traceability.

Core Features & Use Cases

  • Requirements Gathering: Captures clear, traceable specifications with user stories and acceptance criteria.
  • Design & Architecture: Defines system architecture, component interfaces, and data models, with optional visual diagrams.
  • Task Breakdown: Creates granular, atomic tasks with dependencies and verification steps suitable for automation.
  • Implementation & Verification: Guides iterative coding with automated testing, gate checks, and session continuation.
  • Small Changes & Quick Fixes: Supports rapid, scoped modifications through a streamlined "Quick Mode" process.
  • Session Management: Enables pausing and resuming work seamlessly with detailed handoff documentation.

Quick Start

Describe your project scope or feature in natural language, such as "Initialize new project" or "Refactor login flow," and the skill will guide you through specification, design, task creation, and implementation tailored to complexity.

Frequently Asked Questions about tlc-spec-driven

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

FAQPage Schema
How do I break down software requirements into atomic tasks for project planning?

Software requirements are broken down into atomic tasks using a structured four-phase process that captures specifications, defines architecture, and creates granular tasks with dependencies and automated verification steps. This approach ensures traceability and reduces overhead.

What is the best way to plan and execute incremental codebase changes with traceability?

Planning incremental codebase changes with traceability is achieved through adaptive phases that guide iterative coding, automated testing, and gate checks. The process supports small modifications via a streamlined Quick Mode while maintaining clear quality assurance.

Can I pause and resume software development workflows without losing context?

You can pause and resume software development workflows seamlessly using built-in session management features. It enables detailed handoff documentation and session continuity, allowing you to stop work and pick up exactly where you left off without losing context.

How do I define system architecture and component interfaces for a new software project?

System architecture and component interfaces are defined during the design phase by establishing data models and optional visual diagrams. This phase follows requirement gathering, ensuring the architecture directly supports traceable user stories and acceptance criteria.

Does this project planning approach work for both new projects and analyzing existing codebases?

This project planning approach works for both initiating new projects and analyzing existing codebases. It adapts to scope and complexity, supporting feature planning, executing small changes, and guiding structured implementation with precise verification mechanisms.