context-driven-development

To maintain consistent AI alignment, you formalize project context as a reusable artifact by creating and updating specific context documents like product.md and tech-stack.md. This ensures AI interactions remain synchronized with your team's decisions.

Living documentation for onboarding provides a single source of truth by maintaining synchronized context files such as workflow.md and tracks.md. New team members reference these documents to quickly understand the product, tech stack, and established workflows.

To set up context documents for ongoing development, create a context/ directory and initialize files for product.md, tech-stack.md, workflow.md, and tracks.md. Maintaining these files ensures your documentation updates as the project evolves.

Treating project context as a first-class artifact works effectively for new projects by establishing a single source of truth immediately. Creating the initial set of context documents ensures synchronized, living documentation from the start.

Your AI interaction loses context when project notes are scattered instead of persisted as a reusable artifact. Maintaining a living documentation set with workflow.md and tracks.md ensures the AI remains aligned with evolving team decisions.

You need a single source of truth for product documentation when onboarding new members or guiding AI interactions in ongoing development. Formalizing context into living documents prevents scattered notes and maintains team alignment.