skills.rest
inho-team
inho-teamOFFICIAL
Explore all skills by this author →
GitHub

Qtest-driven-development

Enforce a red-green-refactor cycle with tests before implementation.

6|Updated Mar 14, 2026
Search Tags:#workflow#tdd#qa#red-green-refactor#software-engineering#test-driven-development
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qtest-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Qtest-driven-development
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qtest-driven-development
Command: npx skills add https://github.com/inho-team/qe-framework --skill qtest-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD coach: write failing tests first, implement minimal code, then refactor. This guidance enforces test-first development workflow at feature inception and during maintenance.

Core Features & Use Cases

  • Enforces red-green-refactor cycle and ensures tests drive implementation.
  • Guides teams on when to write tests before code and how to structure development workflow around tests.
  • Use Case: starting a new feature with tests to prevent scope creep and regressions.

Quick Start

Start a feature by writing a failing test, then implement the minimal code to pass, and finally refactor.

Frequently Asked Questions about Qtest-driven-development

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

FAQPage Schema
How do I implement test-driven development using the red-green-refactor cycle?▼

Test-driven development using the red-green-refactor cycle requires writing a failing test first, implementing minimal code to pass that test, and then refactoring to remove duplication and improve clarity.

What is the best way to start a new feature with test-first development to prevent scope creep?▼

The best way to start a new feature with test-first development is to write failing tests before writing any code, which enforces a test-driven workflow and prevents scope creep and regressions.

When do I need to write failing tests before code during software maintenance?▼

You need to write failing tests before code during both feature inception and ongoing maintenance to ensure tests drive implementation and maintain reliable quality assurance across software projects.

Does test-driven development guidance apply to ongoing maintenance and software project audits?▼

Yes, test-driven development guidance applies during feature inception, ongoing maintenance, and audits across software projects needing reliable, test-first workflows and quality assurance.

Can I use this TDD workflow guidance for team adoption of test-first development?▼

Yes, you can use this TDD workflow guidance to coach teams on adopting test-driven development by enforcing a strict red-green-refactor cycle and ensuring tests precede implementation.

Why does test-driven development require minimal implementations to pass failing tests?▼

Test-driven development requires minimal implementations to pass failing tests so that the tests strictly drive the code design, followed by a refactor step to remove duplication and improve clarity.

Related Skills

Explore More Software Engineering Skills→
qq824045252-ship-itqq824045252-ship-it

superpowers-test-driven-development

Write failing tests before implementing features to enforce the red-green-refactor cycle.

Community
Advanced
csharpfritzcsharpfritz
18

Testing Expert

Generate unit tests and analyze code coverage for software projects.

Community
Intermediate
p1tl0rdp1tl0rd
8

tdd-ros2

Establish test-first workflows for ROS 2 nodes using gtest and pytest.

Community
Advanced
anexpnanexpn
1

dev-spec

Guide development tasks through interactive specification, planning, and task breakdown.

Community
Basic