Skip to content
Skills Library
Programming · Building & coding

test-driven-development-tdd-workflow

/test-driven-development-tdd-workflow

Use this skill when developing software iteratively following the strict Red-Green-Refactor development cycle.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill when developing software iteratively following the strict Red-Green-Refactor development cycle.

Original author description

Use this skill when developing software iteratively following the strict Red-Green-Refactor development cycle.

How it works

  1. When to use
  2. Prerequisites
  3. Step-by-step workflow
  4. Commands / code examples
  5. Common mistakes & pitfalls
  6. Verification checklist
  7. Related skills
Original SKILL.md headings · 39 lines, 236 words
SKILL.md preview
---
name: test-driven-development-tdd-workflow
description: Use this skill when developing software iteratively following the strict Red-Green-Refactor development cycle.
---
# Test-Driven Development (TDD) Workflow

## When to use
Use this skill when you need to developing software iteratively following the strict Red-Green-Refactor development cycle.

## Prerequisites
- Deep familiarity with relevant domain standards, developer tooling, or testing frameworks.
- Access to testing repository, mobile simulator, or operational workspace.

## Step-by-step workflow
1. **Analyze requirements and constraints**: Review code quality gates, mobile runtime targets, or architecture patterns.
2. **Design implementation strategy**: Draft explicit interfaces, test cases, or declarative configurations.
3. **Execute implementation**: Build and integrate components according to domain best practices.
4. **Validate correctness**: Run automated test suites, verify build outputs, and inspect diagnostic logs.
5. **Establish maintenance guardrails**: Configure CI/CD quality checks, alerts, and documentation.

## Commands / code examples
```bash
# Operational command and verification workflow for test-driven-development-tdd-workflow
echo "Executing verification check for test-driven-development-tdd-workflow"
```

## Common mistakes & pitfalls
- Bypassing automated testing or linting checks under delivery pressure.
- Neglecting to isolate side effects, leading to flaky tests or fragile architectures.
- Introducing tight coupling between distinct architectural domains or deployment units.

## Verification checklist
- [ ] Implementations adhere strictly to domain conventions and standards.
- [ ] Automated verification passes cleanly with zero warnings or errors.
- [ ] Edge cases, error paths, and resource lifecycles are explicitly handled.
- [ ] Documentation and architectural decision records are updated.

## Related skills
- unit-testing-principles-aaa-pattern
- domain-driven-design-bounded-contexts
- ci-cd-github-actions-workflows
- git-interactive-rebase-squash-clean-history

Versions

The database has no other skills named test-driven-development-tdd-workflow.

Database snapshot: 13.11.2026 · package version 4204b057c2cd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100test-driven-development
    Use when writing code that adds or changes behavior (building a feature, fixing a bug, changing a business rule) or when the user asks for TDD, test-first, red-green-refactor, or tests alongside a change.
  • 90tdd
    Implements features using strict test-driven development — red-green-refactor cycle. Writes a failing test first, then minimal code to pass, then refactors. Use when building features that need high reliability.
  • 100tdd-workflow
    Test-Driven Development workflow enforcement with RED-GREEN-REFACTOR cycle. Use only when the user explicitly asks for test-first work or improved test coverage.
  • 95tdd-workflow
    Test-Driven Development workflow enforcement skill. Use when explicitly asked for TDD methodology, test-first development, red-green-refactor cycle, or TDD implementation. Triggers on keywords like "start TDD", "test-driven development", "write tests first", or in Chinese "開始…
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
  • 100tdd
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.