context-driven-development

Maintain project context by creating and updating artifacts like product.md and workflow.md in a conductor directory. This ensures consistent AI behavior and team alignment by keeping living documentation synchronized alongside your codebase as it evolves.

The best way to extract project context from an existing codebase is through brownfield context extraction. This process analyzes your current code to generate documentation artifacts like tech-stack.md and tracks.md, capturing the existing project state for accurate AI alignment.

Prevent documentation drift by validating artifact consistency before implementation and synchronizing documents during code evolution. Regular context validation checks that your conductor artifacts remain aligned with the actual codebase, preventing inconsistencies between documentation and development.

Yes, you can use project documentation artifacts for onboarding new teammates during project migration or setup. Up-to-date contextual documents like product.md and workflow.md provide new team members with the current project state, accelerating their integration and understanding.

No specific framework is required to scaffold context artifacts for a new project. You can set up a new project from scratch by generating the standard conductor artifact suite, which includes product.md, tech-stack.md, workflow.md, and tracks.md, to establish initial project context.