workflow-patterns

Execute software tasks with TDD red-green-refactor cycles and phase checkpoints.

11|4|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/wpank/ai --skill workflow-patterns-wpank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-patterns
Source: https://github.com/wpank/ai/tree/main/skills/meta/workflow-patterns
Command: npx skills add https://github.com/wpank/ai --skill workflow-patterns-wpank

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of inconsistent and untraceable task execution by providing a rigorous, step-by-step methodology for software development.

Core Features & Use Cases

  • Test-Driven Development (TDD): Enforces the red-green-refactor cycle for robust code.
  • Phase Checkpoints: Ensures quality and user approval before proceeding between development phases.
  • Use Case: When implementing a new feature, this Skill guides you through writing tests first, implementing the minimum code to pass, refactoring, verifying coverage, and committing with clear traceability, ensuring a high-quality, well-documented outcome.

Quick Start

Follow the TDD task lifecycle to implement the next pending task in your plan.

Frequently Asked Questions about workflow-patterns

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

FAQPage Schema
How do I implement test-driven development with structured git commits?

Test-driven development with structured commits is implemented by following a red-green-refactor cycle, enforcing phase checkpoints, and verifying minimum 80% test coverage before committing code.

What is the best way to enforce code quality checkpoints during feature implementation?

Code quality checkpoints during feature implementation are enforced through explicit verification protocols that require user approval and minimum 80% test coverage before advancing between development phases.

How does the red-green-refactor cycle work for systematic task execution?

The red-green-refactor cycle for systematic task execution works by writing failing tests first, implementing minimum code to pass them, refactoring, and then committing with clear traceability.

Can I use this TDD workflow if my project doesn't have 80% test coverage yet?

This TDD workflow requires a minimum 80% test coverage gate to proceed past checkpoints, meaning existing code must meet this threshold before advancing through the implementation phases.

Why do I need phase checkpoints in my testing workflow?

Phase checkpoints in your testing workflow are needed to ensure code quality and user approval before proceeding between development phases, solving the challenge of inconsistent and untraceable task execution.

Does this systematic implementation workflow require any specific testing frameworks?

This systematic implementation workflow does not list any specific testing framework dependencies, allowing you to apply the TDD phase checkpoints and coverage gates to your existing testing stack.