context-driven-development

Maintaining project context as a living artifact involves creating conductor artifacts alongside code, organizing product, tech-stack, workflow, and tracks documents that stay synchronized and validated against code changes.

Extracting context from an existing codebase involves analyzing the current project state to generate product, tech-stack, workflow, and tracks documents, capturing established architecture and processes for effective onboarding.

Scaffolding project documentation for a greenfield setup runs a setup process that generates initial product, tech-stack, workflow, and tracks documents in a conductor directory, establishing a managed context artifact baseline.

You can validate artifact consistency before implementation by checking that product, tech-stack, workflow, and tracks documents accurately reflect intended code changes, ensuring alignment across all managed context artifacts.

Keeping tech-stack and tracks documents synchronized requires applying versioned updates and clear governance rules to context artifacts, ensuring documents are refreshed and aligned whenever underlying code changes.

Avoid a managed context artifact approach for highly transient, undocumented workflows where establishing versioned governance and continuous synchronization for product and tracks documents adds unnecessary overhead.