flux-tdd

Enforce red-green-refactor cycles on vertical feature slices.

7|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Nairon-AI/flux --skill flux-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flux-tdd
Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-tdd
Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a disciplined test-driven development workflow by structuring work as small, verifiable iterations.

Core Features & Use Cases

  • Red-green-refactor cycles: write one failing test, implement the minimal code to pass, then refactor.
  • Vertical-slice framing: deliver features end-to-end in single-cut iterations that exercise public interfaces.
  • Session-phase governance: enforces planning, execution, and idle resets to maintain momentum across tools and environments.

Quick Start

Begin with a failing test that specifies the desired behavior, then implement the minimal code to pass it, and repeat for subsequent behaviors.

Frequently Asked Questions about flux-tdd

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

FAQPage Schema
How does test-driven development automation work for vertical feature slices?▼

Test-driven development automation enforces red-green-refactor cycles on vertical feature slices, requiring one failing test at a time before implementing minimal code to pass, ensuring end-to-end behavioral validation across iterative development sessions.

How do I start implementing a feature using a red-green-refactor workflow?▼

To start a red-green-refactor workflow, begin by writing a single failing test that specifies the desired behavior, implement the minimal code required to pass that test, then refactor while maintaining the passing state before repeating the cycle.

What is a vertical slice in test-driven feature development?▼

A vertical slice in test-driven feature development delivers an end-to-end feature iteration in a single cut that exercises public interfaces, allowing teams to validate complete behaviors through small, verifiable red-green-refactor cycles.

Can I use test-driven development for bug-fix cycles in professional software engineering?▼

Yes, test-driven development workflows support both feature implementation and bug-fix cycles in professional software engineering, structuring work as small verifiable iterations to ensure behavioral validation throughout the process.

Does structured TDD workflow support planning and session management constraints?▼

Structured TDD workflow enforces session-phase governance including planning, execution, and idle resets to maintain momentum, while applying constraints like one-test-at-a-time progression and minimal code pass criteria.

What are the limitations of enforcing one-test-at-a-time progression in TDD?▼

Enforcing one-test-at-a-time progression limits parallel test creation but ensures disciplined minimal code pass criteria, requiring planning and idle resets to maintain momentum across tools and environments in iterative sessions.