conductor-implement

Automating a TDD workflow for track implementation involves executing end-to-end task phases with strict process rules, pre-flight checks, and context loading. This skill orchestrates that loop, applying test-driven development phases and commit strategies defined in your workflow configuration.

A conductor track is a structured implementation pathway requiring pre-flight checks, context provisioning, and phase-by-phase task execution. Structured execution works by loading workflow rules, running a task loop with TDD phases, and verifying each checkpoint before committing.

Yes, you can pause and resume test-driven development task execution loops. The skill tracks progress by updating plan.md and metadata.json at each phase checkpoint, allowing you to halt the workflow and continue the implementation from the last verified state.

To track implementation progress and verify phase completion in a TDD workflow, this skill updates metadata.json and plan.md with traceable status updates. It enforces verification rules at each checkpoint to ensure consistent quality before moving to the next task phase.

Yes, conductor-implement works without external dependencies. It operates independently to execute the TDD-driven workflow, relying solely on the process rules, commit strategies, and verification checks defined within your conductor/workflow.md file.

The best way to ensure traceable progress during software development automation is using a structured TDD approach that updates metadata files at each phase. This skill enforces strict commit strategies and verification rules, providing consistent quality and traceable task completion.