workflow-patterns

Coordinate task execution using Conductor's structured TDD workflow.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill workflow-patterns-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-patterns
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/workflow-patterns
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill workflow-patterns-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured guide for implementing tasks using Conductor's TDD workflow, including phase checkpoints, git commit discipline, and a clear verification protocol.

Core Features & Use Cases

  • TDD Task Lifecycle: a step-by-step lifecycle from selecting the next task to completing verification, including marking in progress, red-green-refactor, verifying test coverage, and documenting deviations.
  • Commit & Progress Tracking: guidance on making atomic commits, updating plan.md, and recording task status at each stage.
  • Verification Protocol: instructions for running checks, gating quality, and recording outcomes to ensure consistent delivery.

Quick Start

Follow Conductor's TDD workflow from plan.md through verification to complete a task.

Frequently Asked Questions about workflow-patterns

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

FAQPage Schema
How do I structure a TDD workflow with phase checkpoints and git commits?

A structured TDD workflow coordinates task execution through an 11-step lifecycle, applying red-green-refactor cycles, phase checkpoints, and atomic git commits to ensure verification protocol adherence and consistent delivery.

What is the TDD task lifecycle for Conductor-style task management?

The TDD task lifecycle is an 11-step structured process spanning task selection to final verification, encompassing red-green-refactor execution, test coverage verification, plan updates, and deviation documentation at each phase checkpoint.

How do I track task status and update plan.md during TDD development?

Task status tracking and plan.md updates occur at each phase checkpoint alongside atomic git commits, recording progress, documenting deviations, and ensuring the development plan reflects current lifecycle state throughout TDD execution.

How does the verification protocol gate quality in a TDD workflow?

The verification protocol gates quality by running checks at phase checkpoints, recording outcomes, and enforcing test coverage verification before proceeding, ensuring consistent delivery and strict adherence to the TDD lifecycle.

Can I use this TDD workflow for development tracks without external dependencies?

Yes, this TDD workflow applies to development tracks with zero external dependencies, coordinating task execution through internal phase checkpoints, git commit discipline, and verification protocols rather than relying on external libraries or tools.

When should I document deviations during a TDD task lifecycle?

Deviations should be documented at each phase checkpoint during the TDD task lifecycle, occurring alongside plan.md updates and task status recording, ensuring all variations from the planned approach are captured before final verification.