workflow-patterns — Claude Code skill: what it does, how to install
Guides tasks through Conductor's TDD workflow, from failing tests to phase checks and progress updates. Use it when following a task plan.
/plugin marketplace add wshobson/agents
/plugin install conductor@claude-code-workflowsWhat workflow-patterns does
The skill lays out how to work from plan.md: start with a failing test, follow RED-GREEN-REFACTOR, and complete phases in order. It also covers checks before marking a task complete, target test coverage, and running relevant tests during development.
After each task, update plan.md. Keep each commit to one logical change and leave the code in a working state. Document deviations from the original plan, and do not skip checkpoint verification or approval. Worked examples are in references/details.md.
Install it when your project follows Conductor and you need its workflow and commit guidance. Its instructions are likely unnecessary for tasks outside that process.
What it helps with
- start a task with a failing test
- follow development phases in order
- update
plan.mdafter completing a task - record deviations from the original plan
- check quality gates before marking work complete
Example prompts for the agent
- Implement the task in `plan.md` using Conductor's TDD workflow.
- Check this phase checkpoint and list what must pass before proceeding.
- Finish the task, update `plan.md`, and prepare a separate commit for the logical change.
How to install workflow-patterns
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install conductor@claude-code-workflowsThis installs the whole conductor plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill workflow-patterns -a claude-code3Manually: put the files in place
~/.claude/skills/workflow-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/workflow-patterns/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill workflow-patterns -a codex2Manually: put the files in place
.agents/skills/workflow-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill workflow-patterns -a cursor2Manually: put the files in place
.cursor/skills/workflow-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents workflow-patterns2Manually: put the files in place
.github/skills/workflow-patterns/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/conductor/skills/workflow-patternsManually: put the files in place
.devin/skills/workflow-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about workflow-patterns
How do I install workflow-patterns in Claude Code?
Add the marketplace with /plugin marketplace add wshobson/agents, then install the plugin with /plugin install conductor@claude-code-workflows. To install the skill with the skills CLI, run npx skills add wshobson/agents --skill workflow-patterns -a claude-code.
What does the workflow-patterns skill do?
It guides Conductor's TDD workflow, phase checkpoints, git commits, and verification before a task is marked complete.
Where can I find workflow-patterns examples?
Detailed patterns and worked examples are in references/details.md.
Source text
SKILL.md · Apache-2.0
--- 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.0 --- # 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
© Seth Hobson · Apache-2.0 · wshobson/agents