Conductor Workflow Patterns FAQs

Question 1

What is the TDD Task Lifecycle in this skill?

Accepted Answer

It follows a comprehensive 11-step process including task selection, marking progress in plan.md, writing failing tests (RED), implementing minimum code (GREEN), refactoring, and verifying 80% coverage before final commit.

Question 2

How are project deviations managed?

Accepted Answer

Deviations in scope or implementation are systematically documented in the tech-stack.md or plan.md files, ensuring that the rationale for changes is preserved alongside the code.

Question 3

Does this skill integrate with Git?

Accepted Answer

Yes, it provides standardized commit message formats (feat, fix, refactor, etc.) and uses Git Notes to attach rich summaries and architectural decisions to commits without cluttering the history.

Question 4

What are Phase Completion Protocols?

Accepted Answer

These are verification gates triggered when all tasks in a phase are done. They include running the full test suite, performing manual verifications, and creating a specific checkpoint commit with a recorded SHA.

Question 5

How does the skill handle test coverage?

Accepted Answer

The workflow enforces a minimum 80% test coverage target. It requires identifying uncovered lines, adding missing tests, and passing quality gates before a task can be marked as complete.

Conductor Workflow Patterns

Key Features

Use Cases

Conductor Workflow Patterns

Key Features

Use Cases