developer

Enforce Test-Driven Development with Red-Green-Refactor cycles for code changes.

1|Updated Feb 2, 2026

Search Tags:#unit tests #TDD #refactoring #test-driven development #red-green-refactor #software-engineering

Ready to run

npx skills add https://github.com/micaelmalta/agentic --skill developer-micaelmalta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/micaelmalta/agentic/tree/main/skills/developer
Command: npx skills add https://github.com/micaelmalta/agentic --skill developer-micaelmalta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill promotes a disciplined development approach by enforcing Test-Driven Development, ensuring tests define expected behavior before coding to prevent regressions and miscommunications early in the software lifecycle.

Core Features & Use Cases

TDD-driven development: write tests that define expected behavior before implementing code.
Structured workflow: follow Red-Green-Refactor cycles for features, bug fixes, and refactors.
Guided planning and execution: provides a protocol for incremental, testable changes in any language or framework.

Quick Start

Start by writing a failing test that expresses the desired behavior, then implement the minimal code to make the test pass, and finally refactor while keeping tests green.

Frequently Asked Questions about developer

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

FAQPage Schema

How do I enforce test-driven development when implementing new features?▼

Enforcing test-driven development requires writing failing tests that define expected behavior before coding, then implementing minimal code to pass tests, and refactoring while keeping tests green. This workflow prevents regressions and miscommunications early.

How does the red-green-refactor cycle work for software refactoring?▼

The red-green-refactor cycle works by first writing a failing test for the desired behavior, implementing minimal code to make it pass, and then improving code structure while keeping tests green, ensuring robust incremental changes.

Can I use test-driven development for bug fixes and refactoring in any language?▼

Yes, test-driven development for bug fixes and refactoring is language-agnostic. The workflow provides a protocol for incremental, testable changes across any language or framework by iterating on tests and code.

What is the best way to start a TDD workflow for a new feature?▼

The best way to start a TDD workflow is to write a failing test expressing the desired behavior, implement the minimal code required to make it pass, and finally refactor the implementation while ensuring tests remain green.

Why write unit tests before implementation instead of after?▼

Writing unit tests before implementation defines expected behavior upfront, preventing regressions and miscommunications early in the software lifecycle. This disciplined approach ensures tests guide minimal, robust code development.