AutoGineer
Generated banner for Workflow Patterns
Generated logo for Workflow Patterns

Workflow Patterns

Seth HobsonCommunityCreated by Seth Hobson

  • Skill
  • Guidelines
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a comprehensive framework for executing development tasks within the Conductor ecosystem. It enforces a strict TDD lifecycle—Red, Green, Refactor—and mandates specific procedures for git commits, documentation, and phase-based verification. By following these patterns, developers ensure consistent code quality, maintain accurate progress tracking in plan files, and adhere to established quality gates.

What it does

  • Defines an 11-step TDD task lifecycle for consistent implementation
  • Provides standardized formats for git commit messages and git notes
  • Outlines a phase completion protocol for verification and coverage checks
  • Establishes best practices for maintaining project plan files and tracking progress
  • Enforces quality gates including minimum test coverage requirements
  • Guides the documentation of technical deviations and dependency changes

When to use it

  • When starting a new task from a project's plan.md file
  • During the implementation phase of a software development track
  • When performing phase checkpoints to verify system integrity
  • When committing code changes to ensure traceability and context
  • When conducting quality assurance checks before moving to the next development phase

Advantages

  • Ensures high code quality through mandatory TDD and coverage checks
  • Maintains clear project history with structured git commits and notes
  • Provides a repeatable process that reduces ambiguity in task execution
  • Keeps project documentation and progress tracking synchronized with code changes

Usage examples

“How do I correctly mark a task as in progress in my plan.md?”
The agent will instruct you to update the task status to [~] in plan.md and commit that specific status change before beginning implementation.
“What is the required format for a git commit message for a new feature?”
The agent will provide the standard format including type (feat), scope, summary, bulleted changes, and footer references for the task and track.
“I have finished all tasks in Phase 1. What should I do now?”
The agent will guide you through the Phase Completion Protocol, including identifying changed files, verifying test coverage, running the full suite, and generating manual verification steps.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/workflow-patterns/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip workflow-patterns.zip -d .agents/skills

Documentation by Seth Hobson

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

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/conductor/skills/workflow-patterns · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download workflow-patterns.zip