---
name: patrones-flujo-trabajo-tdd
description: Guia de referencia para implementar tareas con el ciclo TDD rojo-verde-refactor en flujos agenticos, gestionando checkpoints de fase, commits de git y protocolos de verificacion de calidad. Util para equipos de desarrollo que trabajan con frameworks de agentes estructurados.
license: MIT
metadata:
  id: 3d2c42fb
  slug: patrones-flujo-trabajo-tdd
  titulo: "Patrones de Flujo de Trabajo TDD para Agentes"
  servicio: IA-Ingenieria-MLOps
  categoria_recurso: Inspiracion-Formacion
  tipo: referencia
  nivel: intermedio
  idioma: es
  idioma_original: en
  acceso: gratis
  precio_eur: 0
  plataformas: [Claude Code, Codex CLI, Cursor, OpenCode, Gemini CLI]
  dependencias: [conductor-plugin, git]
  licencia: { spdx: MIT, redistribuible: true, uso_comercial: true }
  fuente:
    repo: wshobson/agents
    url: https://github.com/wshobson/agents/tree/main/plugins/conductor/skills/workflow-patterns
    commit: cc37bfd
    autor: wshobson
    nombre_original: workflow-patterns
    duplicados_en: []
  seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-14", motor: "grep-estatico+auditor-llm" }
  ficha:
    que_hace: "Proporciona patrones y buenas practicas para ejecutar el ciclo TDD dentro del framework Conductor de agentes de IA."
    como_lo_hace: "Documenta checkpoints de fase, gestion de commits, puertas de calidad y protocolo de verificacion en formato de guia de referencia consultable por agentes."
  content_hash: "3d2c42fb02f05e7797ec938660cb71511be5d7d8a547019a988d0c220be922a0"
  version: 1.0.0
---

# Workflow Patterns

Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.

## When to Use This Skill

- Implementing tasks from a track's plan.md
- Following TDD red-green-refactor cycle
- Completing phase checkpoints
- Managing git commits and notes
- Understanding quality assurance gates
- Handling verification protocols
- Recording progress in plan files

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

## Best Practices

1. **Never skip RED**: Always write failing tests first
2. **Small commits**: One logical change per commit
3. **Immediate updates**: Update plan.md right after task completion
4. **Wait for approval**: Never skip checkpoint verification
5. **Rich git notes**: Include context that helps future understanding
6. **Coverage discipline**: Don't accept coverage below target
7. **Quality gates**: Check all gates before marking complete
8. **Sequential phases**: Complete phases in order
9. **Document deviations**: Note any changes from original plan
10. **Clean state**: Each commit should leave code in working state
11. **Fast feedback**: Run relevant tests frequently during development
12. **Clear blockers**: Address blockers promptly, don't work around them