Workflow Patterns
Unverified●29/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add workflow-patternsWho is stuck, and on what
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 whole source
Frontmatter — 3 properties
| 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 |
| 1 | --- |
| 2 | name: workflow-patterns |
| 3 | 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. |
| 4 | version: 1.0.0 |
| 5 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 6 | |
| 7 | # Workflow Patterns |
| 8 | |
| 9 | 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. |
| 10 | |
| 11 | ## When to Use This Skill |
| 12 | |
| 13 | - Implementing tasks from a track's plan.md |
| 14 | - Following TDD red-green-refactor cycle |
| 15 | - Completing phase checkpoints |
| 16 | - Managing git commits and notes |
| 17 | - Understanding quality assurance gates |
| 18 | - Handling verification protocols |
| 19 | - Recording progress in plan files |
| 20 | |
| 21 | ## Detailed patterns and worked examples |
| 22 | |
| 23 | Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. |
| 24 | |
| 25 | ## Best Practices |
| 26 | |
| 27 | 1. **Never skip RED**: Always write failing tests first |
| 28 | 2. **Small commits**: One logical change per commit |
| 29 | 3. **Immediate updates**: Update plan.md right after task completion |
| 30 | 4. **Wait for approval**: Never skip checkpoint verification |
| 31 | 5. **Rich git notes**: Include context that helps future understanding |
| 32 | 6. **Coverage discipline**: Don't accept coverage below target |
| 33 | 7. **Quality gates**: Check all gates before marking complete |
| 34 | 8. **Sequential phases**: Complete phases in order |
| 35 | 9. **Document deviations**: Note any changes from original plan |
| 36 | 10. **Clean state**: Each commit should leave code in working state |
| 37 | 11. **Fast feedback**: Run relevant tests frequently during development |
| 38 | 12. **Clear blockers**: Address blockers promptly, don't work around them |
| 39 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Task Coordination StrategiesDecompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.◐◐◐◐◐●35/40Ebay Seller Tools·····●34/40Tough Decision Advisor: Every Angle ConsideredHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.●····●32/40DHDNA Profiler — Cognitive Pattern ExtractionPaste any email, proposal, or note someone wrote, and get back a plain-language read on how they think, what drives their decisions, and how they communicate.●····●32/40