context-driven-development

You can keep product documentation and code context synchronized by organizing context artifacts alongside code to ensure consistent AI behavior and team alignment. This approach defines relationships between product.md, tech-stack.md, and workflow.md to provide a single source of truth.

Context-driven development is an artifact-driven approach that organizes project context artifacts alongside code to ensure AI alignment and team clarity. You need it when scaling projects requires keeping product, tech-stack, and workflow documentation in sync for reliable AI interactions.

To set up context artifacts for a new Conductor-driven project, run the /conductor:setup command to initialize the required documentation structure. This establishes the relationships between product.md, tech-stack.md, and workflow.md to provide a single source of truth.

Context-driven development works for both greenfield and brownfield projects. It supports onboarding, governance, and lifecycle management for context artifacts across existing and new projects by enforcing a structured lifecycle with artifacts, relationships, and update rules.

Your AI workflow loses alignment when documentation changes because context-driven development is hard to scale without a consistent artifact-driven approach. Enforcing structured update rules between product.md, tech-stack.md, and workflow.md keeps context current and actionable.