Implement TDD Workflow Patterns
Conductor's TDD workflow - phase checkpoints, git commit management, and verification protocol for implementation.
Why it matters
Streamline task implementation using Conductor's TDD workflow, ensuring quality through phase checkpoints, Git management, and verification protocols.
Outcomes
What it gets done
Implement tasks following TDD red-green-refactor.
Manage Git commits and progress tracking.
Execute verification protocols for quality assurance.
Complete phase checkpoints during implementation.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-workflow-patterns | bash Overview
Workflow Patterns
Guides task implementation using Conductor's TDD workflow: phase checkpoints, git commit management, and a verification protocol. Use when implementing tasks from a track's plan.md, following TDD, or handling phase checkpoints and verification.
What it does
Workflow Patterns is a 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 - and when NOT to
Use this skill when implementing tasks from a track's plan.md, following the TDD red-green-refactor cycle, completing phase checkpoints, managing git commits and notes, understanding quality assurance gates, handling verification protocols, or recording progress in plan files. It is not for tasks unrelated to workflow patterns or for work in a different domain or tool outside this scope.
Inputs and outputs
Given a task from a track's plan.md, the skill applies the TDD red-green-refactor cycle through defined phase checkpoints, producing verified progress recorded back into the plan file along with the associated git commits and notes. Detailed patterns and examples are available in resources/implementation-playbook.md.
Who it's for
Engineers implementing tasks from a Conductor track's plan who want a consistent TDD workflow with phase checkpoints, git commit discipline, and a verification protocol - rather than ad-hoc implementation without quality gates.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.