skills.rest
jvm-skills
jvm-skillsOFFICIAL
Explore all skills by this author →
GitHub

tdd-task

Enforce a test-driven development workflow with plan, red, green, and refactor steps.

135|25|Updated Feb 20, 2026
Search Tags:#workflow#tdd#refactor#unit-testing#integration-testing#quality-assurance#test-driven-development
One-click install
npx skills add https://github.com/jvm-skills/jvm-skills --skill tdd-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-task
Source: https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/tdd-task
Command: npx skills add https://github.com/jvm-skills/jvm-skills --skill tdd-task

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires test, commit, restart, simplify, frontend, e2e-test.

What problem does it solve?

This Skill enforces a Test-Driven Development workflow by ensuring a failing test is written before implementing code changes, promoting robust, maintainable software.

Core Features & Use Cases

  • Enforces TDD cycle: plan, write a failing test, implement, refactor, verify, and beautify.
  • Broad applicability: suitable for feature additions, bug fixes, and refactors across unit, integration, and UI layers.
  • Use Case: a developer adds a small feature and writes a failing test first, then implements until the test passes and the code is cleaned up.

Quick Start

Create a failing test for the intended change, then implement the code to pass it.

Frequently Asked Questions about tdd-task

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

FAQPage Schema
How do I enforce a test-driven development workflow for feature additions and bug fixes?▼

Test-driven development is enforced by requiring a failing test before implementing code changes. The workflow follows plan, red, green, and refactor steps to ensure robust, maintainable software across unit, integration, and UI layers.

What is the correct step-by-step process for writing a failing test before implementation?▼

The correct test-driven development process starts with planning, then writing a failing test, implementing code until the test passes, refactoring, and finally verifying and beautifying the code.

Does test-driven development work for both unit testing and integration testing on JVM-based projects?▼

Yes, test-driven development works for JVM-based software tasks across unit, integration, and UI layers. It targets typical scenarios including feature additions, bug fixes, and refactors.

What's the best way to integrate a test-first development cycle with existing CI practices?▼

The best way to integrate test-first development with existing CI practices is by following the specified end-to-end workflow of plan, red, green, and refactor steps to ensure tests guide implementation.

When should I avoid using a strict test-driven development approach for refactoring?▼

A strict test-driven development approach focuses on writing failing tests before feature implementation. While it supports refactoring during the cycle, standard refactoring tasks without new features may not require an initial failing test.

Related Skills

Explore More Software Engineering Skills→
XGanQAQXGanQAQ
1

test-setup

Create test directories, engine runners, and GitHub Actions workflows.

Community
Advanced
hochoa13hochoa13

test-driven-development

Enforce a strict RED-GREEN-REFACTOR cycle for all code implementation.

Community
Advanced
nahisahonahisaho
12

test-engineer

Design and implement unit, integration, and E2E tests for frontend and backend codebases.

Community
Advanced
futureteafuturetea

code-simplifier

Simplify and optimize Go code while preserving behavior and following gofmt conventions.

Community
Intermediate