workflow-patterns

Guide engineers through Conductor's TDD workflow with phase checkpoints and verification protocols.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill workflow-patterns-emilneuraz-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-patterns
Source: https://github.com/emilneuraz-ai/neuraz-web/tree/main/.agents/skills/.agents/skills/workflow-patterns
Command: npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill workflow-patterns-emilneuraz-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides software teams to implement tasks using Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, and applying a formal verification protocol to ensure quality.

Core Features & Use Cases

  • TDD task lifecycle guidance from plan.md to completed tasks
  • Phase checkpoint management and commit hygiene across tasks
  • Verification protocol enforcement to meet QA gates
  • Documentation alignment through task comments and plan updates

Quick Start

Follow the 11-step lifecycle to move the next task from plan.md to verified completion.

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 workflow checkpoints during software development?

TDD workflow checkpoints are enforced by guiding engineers through phase verification protocols, managing red-green-refactor cycles, and requiring task-level git commits before completing tracked phases.

What is the best way to track task progress using plan.md for TDD?

Tracking task progress with plan.md involves moving tasks through an 11-step lifecycle, updating documentation alignment through task comments, and coordinating phase verification gates to ensure quality assurance.

How does git commit discipline work within a TDD task lifecycle?

Git commit discipline within a TDD lifecycle enforces task-level commits across phases, ensuring that progress is documented and verified at each checkpoint before advancing to the next development stage.

Do I need a specific framework to manage red-green-refactor cycles and verification gates?

Managing red-green-refactor cycles requires a task-driven development environment supporting plan.md task tracking and formal verification protocols to satisfy phase quality assurance gates.

Why use phase checkpoints instead of continuous integration for task verification?

Phase checkpoints provide formal verification gates at specific points in the TDD lifecycle, ensuring task-level commit hygiene and documentation alignment, whereas continuous integration focuses on build stability.