43 lines
1.5 KiB
Markdown
43 lines
1.5 KiB
Markdown
---
|
|
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.
|
|
risk: safe
|
|
source: community
|
|
date_added: '2026-02-27'
|
|
---
|
|
|
|
# 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.
|
|
|
|
## Use this skill when
|
|
|
|
- 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
|
|
|
|
## Do not use this skill when
|
|
|
|
- The task is unrelated to workflow patterns
|
|
- You need a different domain or tool outside this scope
|
|
|
|
## Instructions
|
|
|
|
- Clarify goals, constraints, and required inputs.
|
|
- Apply relevant best practices and validate outcomes.
|
|
- Provide actionable steps and verification.
|
|
- If detailed examples are required, open `resources/implementation-playbook.md`.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed patterns and examples.
|
|
|
|
## Limitations
|
|
- Use this skill only when the task clearly matches the scope described above.
|
|
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
|
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|