workflow-patterns
wshobson/agents
Implement tasks using Conductor's TDD workflow with phase checkpoints, git management, and verification protocols.
What is workflow-patterns?
Guide for implementing tasks according to Conductor's test-driven development workflow. Use this skill when following the red-green-refactor cycle, managing phase checkpoints, handling git commits with context, and executing quality assurance gates throughout implementation.
- Follow TDD red-green-refactor cycle for task implementation
- Manage phase checkpoints and verification gates
- Handle git commits with rich context notes
- Track progress in plan.md files
- Execute quality assurance verification protocols
- Ensure code coverage meets targets
How to install workflow-patterns
npx skills add https://github.com/wshobson/agents --skill workflow-patternsHow to use workflow-patterns
- 1.Write failing tests first (RED phase) before implementation
- 2.Implement code to pass tests (GREEN phase)
- 3.Refactor code while maintaining test pass (REFACTOR phase)
- 4.Make small, logical commits with rich git notes
- 5.Update plan.md immediately after task completion
- 6.Wait for checkpoint verification before proceeding to next phase
- 7.Verify all quality gates pass before marking task complete
- 8.Address blockers directly rather than working around them
Use cases
- Implementing tasks from a track's plan.md following TDD discipline
- Completing phase checkpoints with proper verification before moving forward
- Managing git commits with contextual notes for future understanding
- Recording task progress and deviations in plan files
- Ensuring quality gates are checked before marking tasks complete
- Developers implementing tasks in Conductor-managed projects
- Teams following test-driven development practices
- Agents managing task workflows with quality checkpoints
- Contributors tracking progress across multiple implementation phases
workflow-patterns FAQ
The RED phase is writing failing tests first, before any implementation. This ensures you understand the requirements and have a clear target for development.
Update plan.md immediately after task completion, not later. This keeps progress tracking current and helps coordinate with other team members.
No. Best practice rule 4 states: never skip checkpoint verification. Wait for approval before proceeding to the next phase.
Include rich context that helps future understanding. Git notes should explain the why and what of changes, not just the code diff.
Don't accept coverage below the target. Coverage discipline is a quality gate that must be met before marking work complete.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
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
- 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
Related skills
More from wshobson/agents and the wider catalog.
accessibility-compliance
Build WCAG 2.2 compliant interfaces with keyboard navigation, screen reader support, and inclusive design patterns.
ai-debt-detector
Audit AI-generated code for hidden debt: missing error handling, orphaned resources, and hallucinated dependencies.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment.
angular-migration
Migrate AngularJS apps to Angular using hybrid mode, incremental rewriting, and dependency injection updates.
remotion-video
|
translate-pdf
|