Execute track plan via TDD workflow
Conductor Implementcommandsetup L2★0
tdmtrader/jetbridge ↗What it does
Execute TDD task workflow from active track plan with MCP-driven state management
Best for
Driving large multi-phase development projects where atomic task state, phase gating, and learning capture are critical
Inputs
- · conductor/ context files (product.md, tech-stack.md, workflow.md, tracks.md)
- · active track plan
- · task description
Outputs
- · test files
- · implementation
- · git commits
- · updated plan.md with task status
- · cgx.md learning entries
Requires
- · conductor MCP (transition_status, complete_task, checkpoint_phase, add_learning)
- · Bash (git, test runner)
- · Read/Write
Preconditions
- · conductor/ directory structure exists
- · conductor MCP available (preferred)
- · track plan written with Task sections
Failure modes
- · conductor MCP not connected (falls back to manual file edit)
- · test fails
- · phase checkpoint blocked by user
Trust signals
- · MCP-first architecture (read conductor/ context FIRST, before any edits)
- · Red→Green→Refactor TDD flow enforced
- · explicit user approval at phase checkpoints