workflow-patterns

Name: workflow-patterns
Availability: InStock
Author: kurokeita

Enforce TDD phase checkpoints and git commit discipline for Conductor workflows.

1|Updated Jan 17, 2026

Search Tags:#git #workflow #TDD #verification #checkpoints #plan.md

Ready to run

npx skills add https://github.com/kurokeita/ai-agent --skill workflow-patterns-kurokeita

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-patterns
Source: https://github.com/kurokeita/ai-agent/tree/main/skills/workflow-patterns
Command: npx skills add https://github.com/kurokeita/ai-agent --skill workflow-patterns-kurokeita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through Conductor's TDD workflow by enforcing phase checkpoints and disciplined git commits.

Core Features & Use Cases

TDD Task Lifecycle: Follow the 11-step process for each task starting from the next pending entry in plan.md.
Phase checkpoints & Git discipline: Manage task states, commit statuses, and note changes in the plan and git history.
Verification protocol: Apply QA gates, ensure coverage, and document deviations as tasks progress.

Quick Start

Run through the 11-step lifecycle on the current track's plan.md to advance the next task to In Progress and commit the status update.

Frequently Asked Questions about workflow-patterns

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

FAQPage Schema

How do I enforce TDD checkpoints and track task state in git commits?▼

TDD checkpoints are enforced by following an 11-step lifecycle that advances tasks from plan.md, applying phase verification gates and committing task state updates directly to git history for progress tracking.

What is the red-green-refactor workflow process for tasks listed in plan.md?▼

The red-green-refactor workflow processes the next pending task in plan.md through structured phases, applying QA verification gates and documenting task state changes within both the plan file and git commits.

How do I document TDD task progress and QA verification results?▼

TDD task progress and QA results are documented by updating task statuses and noting deviations within plan.md, while simultaneously recording phase checkpoints and commit statuses in the git history.

Can I use this workflow for tasks not derived from a track's plan.md?▼

No, this TDD workflow specifically applies to tasks derived from a track's plan.md, relying on that file to identify the next pending entry and document the required task state and verification updates.

Does this TDD workflow require any external dependencies or testing frameworks?▼

No external dependencies are required; the workflow operates by enforcing phase checkpoints and disciplined git commits, relying solely on plan.md for task tracking and git history for verification documentation.

What's the best way to start a TDD cycle using this workflow?▼

To start a TDD cycle, run through the 11-step lifecycle on the current track's plan.md, which advances the next pending task to In Progress and commits the initial status update to git.