context-driven-development

Run the Conductor setup flow to create a conductor directory containing product.md, tech-stack.md, workflow.md, and tracks.md. For new projects you answer questions interactively; for existing codebases the artifacts are pre-populated from detected patterns.

The conductor directory contains index.md, product.md, product-guidelines.md, tech-stack.md, workflow.md, tracks.md, setup_state.json, a code_styleguides folder, and a tracks folder with per-track spec.md, plan.md, and metadata.json files.

Yes, brownfield projects are supported. The setup analyzes existing code, configs, and documentation to pre-populate artifacts, then you review and refine the generated context to reconcile existing patterns with desired standards.

Update tech-stack.md whenever you add dependencies, upgrade major versions, or change infrastructure. Update product.md when features complete, the product vision shifts, or target users change, keeping artifacts synchronized with each other.

Common anti-patterns include stale context that is never updated, context sprawl across scattered locations, implicit knowledge never written down, and over-specification that makes documents impossible to maintain. Update artifacts incrementally with each track.