workflow-patterns
Enforces a structured test-driven development workflow with quality checkpoints and verification.
Install
mkdir -p .claude/skills/workflow-patterns && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3715" && unzip -o skill.zip -d .claude/skills/workflow-patterns && rm skill.zipInstalls to .claude/skills/workflow-patterns
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Execute TDD red-green-refactor cycles
- →Manage task phase checkpoints
- →Record git commit notes with context
- →Enforce quality assurance gates
- →Update progress in plan.md files
- →Follow verification protocols
How it works
The skill guides task implementation by enforcing sequential phases, requiring failing tests before code changes, and mandating checkpoint verification. It tracks progress through updates to plan.md and maintains code quality via defined gates.
Inputs & outputs
When to use workflow-patterns
- →Following TDD red-green cycle
- →Managing phase checkpoints
- →Recording git commit notes
- →Enforcing quality gates
About this skill
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
When not to use it
- →Skipping the initial failing test phase
- →Bypassing checkpoint verification
- →Working around blockers instead of addressing them
Prerequisites
Limitations
- →Requires adherence to sequential phase order
- →Mandates specific coverage targets
- →Depends on the availability of plan.md for task tracking
How it compares
Unlike manual development, this skill enforces a strict verification protocol and sequential phase management to ensure quality gates are met before task completion.
Compared to similar skills
workflow-patterns side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| workflow-patterns (this skill) | 1 | 2mo | No flags | Intermediate |
| spec-driven-workflow | 0 | 1mo | No flags | Advanced |
| proof-of-work | 1 | 6mo | No flags | Intermediate |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by wshobson
View all by wshobson →You might also like
spec-driven-workflow
CafeSemCafeina
The build workflow for avaliador-tech-recruiter — risk-ordered tiers with a protected mock-mode floor, a Ready spec required before any unit is implemented, eval gates (L0 contract / L1 policy / L2 fixtures) as the merge filter, package partitioning for parallel agents, atomic Conventional Commits,
proof-of-work
MadAppGang
Proof artifact generation patterns for task validation. Covers screenshots, test results, deployments, and confidence scoring.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
verification-before-completion
obra
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always