context-driven-development

Keeping project documentation in sync with code is achieved by treating context artifacts like product.md and tech-stack.md as living documents that evolve directly alongside your codebase. This reduces context drift across repositories.

Context-driven development is a technique that manages project context as a living artifact to guide AI interactions and ensure team alignment. You need it when context drift occurs across AI sessions or in multi-team environments.

To establish core context artifacts, frame the project by creating and maintaining product.md, tech-stack.md, and workflow.md files alongside your code. This ensures living documentation supports cross-team collaboration from the start.

Yes, this context-driven approach works specifically with Conductor-managed initiatives that require living context across product, tech-stack, and workflow artifacts. It documents relationships to these artifacts to support multi-team environments.

AI consistency degrades across coding sessions due to context drift. Enforcing a frontmatter with name and description and maintaining living context artifacts improves AI decision traceability and consistency over time.

You can use this for both greenfield and brownfield projects. It improves AI consistency and decision traceability by ensuring living documentation evolves with project needs regardless of the project's current lifecycle stage.