mcpField
W
workflow-patterns

workflow-patterns

github.com/wshobsonAgent workflows41.9k11.1k installsUpdated 2w ago
Repository

About workflow-patterns

A guide to Conductor's TDD workflow for implementing planned tasks, managing phase checkpoints, and verifying quality. It is intended for developers who need consistent progress tracking, commits, and quality gates during implementation.

Key features

  1. 01Follow the TDD red-green-refactor cycle
  2. 02Manage phase checkpoints and verification
  3. 03Record progress in plan files
  4. 04Organize focused git commits and notes
  5. 05Apply quality gates throughout implementation

Use cases

  1. 01Implement tasks listed in a track plan
  2. 02Verify work at phase checkpoints
  3. 03Track task completion in plan.md
  4. 04Maintain a clean working state across commits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wshobson/agents --skill workflow-patterns

After installing, type/workflow-patternsin Claude Code to confirm it loaded.

Bundled filesreferences/details.md

Details

From the project README

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

Comments

Markdown supported