Skills wshobson agents Conductor
workflow-patterns
- Use it when:
- You're implementing tasks from a Conductor track's plan.md and want a strict TDD loop with checkpoints.
- It does:
- Runs an 11-step lifecycle per task: write failing tests, make them pass, refactor, check coverage, commit, attach a git note, record the commit SHA.
- You get:
- Small focused commits, a plan.md updated as you go, and a phase checkpoint that stops for your approval before continuing.
- Part of:
- wshobson's Conductor context-driven-development plugin.
Skill 3 of 3 in the Conductor bundle, after track-management.
Only works inside its bundle: Works task by task through a track's plan.md, in the format track-management defines, updating its status markers and recording each commit's SHA there. Install Conductor instead.
Part of wshobson's Conductor plugin; it drives the implementation step and expects a Conductor-scaffolded project — the plan.md tracks created by the plugin's context-driven-development and track-management skills.
TL;DR
The implementation step of wshobson's Conductor methodology (context → spec & plan → implement). For each pending task in a track's plan.md it follows red-green-refactor: write tests that fail, write the minimum code to pass, then refactor while tests stay green, checking coverage against an 80% target. It commits with a typed, scoped message, attaches a rich git note of decisions and files changed, and records the commit SHA back in plan.md. When a phase's tasks are done it runs a verification protocol — list changed files, confirm tests exist, run the full suite, lint and type-check, generate manual verification steps — then waits for explicit user approval before a checkpoint commit. It also covers deviations (scope added or cut, technical changes), error recovery, and TDD variations by task type. The quality gates, git conventions and checkpoint mechanics live in a reference file.
Summarizes the skill at 4bde316.
npx skills add https://github.com/wshobson/agents --skill workflow-patterns skills.sh pageSource on GitHubAll skills from wshobson/agents
- Total Downloads
- 11,400 on skills.sh, Nov 9, 2026
- Repo stars
- 42,334 wshobson/agents
- First seen
- Jan 20, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 182 |
| Sep 28 | 309 |
| Oct 5 | 436 |
| Oct 12 | 209 |
| Oct 19 | 179 |
| Oct 26 | 180 |
| Nov 2 | 165 |
| Nov 9 | 152 |
| Category |
Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From wshobson/agents at 4bde316. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: workflow-patterns
description: 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.
version: 1.0.0Workflow 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