workflow-patterns

★ 37,559

by wshobson · part of wshobson/agents

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

🧩 One of 7 skills in the wshobson/agents package — works on its own, and pairs well with its siblings.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

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

Never skip RED: Always write failing tests first
Small commits: One logical change per commit
Immediate updates: Update plan.md right after task completion
Wait for approval: Never skip checkpoint verification
Rich git notes: Include context that helps future understanding
Coverage discipline: Don't accept coverage below target
Quality gates: Check all gates before marking complete
Sequential phases: Complete phases in order
Document deviations: Note any changes from original plan
Clean state: Each commit should leave code in working state
Fast feedback: Run relevant tests frequently during development
Clear blockers: Address blockers promptly, don't work around them