feature

Name: feature
Availability: InStock
Author: SleepyDreamsDev

Automate end-to-end TDD feature delivery from planning to ship.

Updated Aug 23, 2026

Search Tags:#automation #workflow #testing #tdd #specification #kaizen #gherkin

Ready to run

npx skills add https://github.com/SleepyDreamsDev/claude-tdd-starter --skill feature-sleepydreamsdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/SleepyDreamsDev/claude-tdd-starter/tree/main/core/.claude/skills/feature
Command: npx skills add https://github.com/SleepyDreamsDev/claude-tdd-starter --skill feature-sleepydreamsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end TDD feature delivery is complex and error-prone; this Skill automates the full cycle from planning to ship, reducing manual workload and ensuring repeatable quality.

Core Features & Use Cases

End-to-end TDD cycle: plan, write tests, implement, refactor, and ship across multiple workspaces.
Gherkin spec generation and automated test scaffolding to accelerate specification-driven development.
Kaizen retrospective and automated validation to maintain quality after each delivery.

Quick Start

Provide a feature description and run the /feature command to start autonomous TDD delivery.

Frequently Asked Questions about feature

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

FAQPage Schema

How do I automate end-to-end TDD feature delivery from planning to deployment?▼

Automating end-to-end TDD feature delivery requires handling plan loading, Gherkin spec generation, RED+GREEN testing, and Kaizen validation in a single workflow. This approach reduces manual workload and ensures repeatable quality across multiple workspaces and feature sizes.

What is the best way to generate Gherkin specs for test-driven development?▼

Generating Gherkin specs for TDD is best handled through automated scaffolding from a feature description. This accelerates specification-driven development by structuring acceptance criteria upfront, enabling strict TDD cadence and automated validation before implementation begins.

Can I apply strict TDD cadence across multiple workspaces and feature sizes?▼

Applying strict TDD cadence across multiple workspaces and feature sizes is supported by autonomous end-to-end workflows. It enforces plan-driven criteria, automated security checks, and RED+GREEN cycles universally, ensuring repeatable quality regardless of project scale.

How do I run a Kaizen retrospective after completing a TDD feature cycle?▼

Running a Kaizen retrospective after a TDD feature cycle involves automated validation and quality checks post-delivery. This process maintains repeatable quality by analyzing the completed workflow, ensuring security checks passed, and identifying improvements for future cycles.

What are the limitations of automating the full TDD cycle from plan loading to ship?▼

Limitations of automating the full TDD cycle include the necessity of providing accurate initial feature descriptions for plan loading. While it handles RED+GREEN and Kaizen autonomously, complex edge cases may require manual intervention to ensure specification accuracy.