doc-driven-dev

Documentation-driven development aligns design docs, ROADMAP.md, and story files with code changes by enforcing validation steps and synchronization rules during feature iteration. This ensures code changes remain traceable to living documentation, reducing drift and miscommunication.

Document-first development orchestrates feature workflows by updating the ROADMAP, creating a Story file, drafting design docs, implementing code, and syncing all documentation to reflect the final state. It ensures story files and changelogs accurately reflect implemented features through compliance checks.

Structure documentation by organizing files under stories/, docs/design/, and ROADMAP.md with proper frontmatter metadata. This layout maintains templates and references for design decisions and changelogs to guide development and ensure validation steps are enforced.

Yes, the workflow applies to feature development across existing projects by validating that Story files reflect implemented features and updating ROADMAP.md accordingly. It enforces synchronization rules to ensure code changes align with your established design references and changelogs.

Enforce traceability by applying documentation-driven workflow orchestration that validates Story files against implemented features and updates ROADMAPs during code iteration. This ensures design docs, changelogs, and stories stay synchronized with development work through compliance checks.

Code drifts from design docs when development workflows lack enforced synchronization rules between code changes and documentation. Prevent drift by maintaining a document-first workflow that validates story files and updates ROADMAP.md and design references during every code iteration.