driven▌

Structured project context management through persistent, synchronized documentation artifacts. \n \n Creates and maintains five core artifacts in a conductor/ directory: product.md (vision/goals), tech-stack.md (dependencies/architecture), workflow.md (development practices), tracks.md (work unit registry), and product-guidelines.md (communication standards) \n Scaffolds new projects interactively or extracts context from existing codebases, pre-populating artifacts based on discovered patterns

Write tests first, watch them fail, then implement minimal code to pass. \n \n Follows the red-green-refactor cycle: write a failing test, verify it fails correctly, implement minimal code to pass, then refactor while keeping tests green \n Requires deleting any production code written before tests exist; no exceptions for \"reference\" or \"adaptation\" \n Emphasizes watching tests fail as proof they actually test the right thing; tests that pass immediately prove nothing \n Covers common ratio