tlc-spec-driven

Manage software projects through Specify, Design, Tasks, and Execute phases.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/P4rzi/PROT-RISK --skill tlc-spec-driven-p4rzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlc-spec-driven
Source: https://github.com/P4rzi/PROT-RISK/tree/main/.github/skills/tlc-spec-driven
Command: npx skills add https://github.com/P4rzi/PROT-RISK --skill tlc-spec-driven-p4rzi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines software development by providing an adaptive, phase-based workflow that automatically adjusts its rigor based on project complexity, ensuring efficiency and precision from initial planning to final execution.

Core Features & Use Cases

  • Adaptive Planning: Utilizes 4 phases (Specify, Design, Tasks, Execute) that auto-size based on complexity, applying full rigor for complex features and skipping ceremony for simple ones.
  • Requirement Traceability: Ensures clear links from requirements to tasks and commits.
  • Atomic Tasks & Commits: Breaks down work into granular, verifiable tasks, each resulting in an atomic Git commit.
  • Persistent Memory: Maintains context and state across sessions, allowing for seamless pausing and resuming of work.
  • Use Case: Kickstart a new project by initializing its vision and roadmap, then iteratively develop features by specifying requirements, designing architecture, breaking down tasks, and executing them with rigorous verification and atomic commits.

Quick Start

Use the tlc-spec-driven skill to initialize a new project by describing its vision and goals.

Frequently Asked Questions about tlc-spec-driven

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

FAQPage Schema
How do I manage software development projects with an adaptive workflow?

Managing software development projects with an adaptive workflow involves auto-sizing four phases: Specify, Design, Tasks, and Execute. This approach applies full rigor for complex features while skipping ceremony for simple ones, ensuring efficient project planning and execution.

How do I break down feature requirements into atomic Git commits?

Breaking down feature requirements into atomic Git commits involves granular task decomposition and requirement traceability. Each verifiable task results in an atomic commit, ensuring clear links from initial requirements through to the final codebase implementation.

What is the best way to maintain project context across sessions?

Maintaining project context across sessions requires persistent session memory. This mechanism stores state and context locally, allowing you to seamlessly pause and resume software development work without losing prior planning or task progress.

Can I initialize a new project and analyze an existing codebase with this workflow?

Yes, you can initialize a new project to establish its vision and roadmap, or analyze an existing codebase. The workflow supports both new project initialization and ad-hoc task management for ongoing software development.

Does this workflow automation approach work for simple tasks or is it only for complex features?

This workflow automation works for both simple tasks and complex features. It auto-sizes its rigor based on project complexity, applying full planning phases for complex features and skipping unnecessary ceremony for simple ad-hoc tasks.