Add a maintainers script to safely promote high-confidence legacy risk labels from unknown to concrete values, cover it with tests, and regenerate the canonical skill artifacts and plugin copies. This reduces the legacy unknown backlog without forcing noisy classifications that still need manual review.
38 lines
1.2 KiB
Markdown
38 lines
1.2 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.
|