Dvp Composer

1. Create dvp_workspace/ when the workflow starts 2. At each phase's [Done] step, write all deliverable files to dvp_workspace/ 3. At the start of each phase (except Phase 1), read the previous phase's deliverable files first 4. File names are hard-coded in each phase instruction — do not rename them 5. Overwrite existing files without asking for confirmation 6. All files use Markdown format. The only exceptions are: dvp_content.json (JSON), DVP__v1.0.xlsx (Excel), and any user-provided template files.

Cross-Phase File: assumptions-and-gaps.md

Phase 1 creates this file with the initial table structure: | # | Category | Description | Status | Phase |. Phases 2 and 3 MUST append new rows (with Status = Open) when they encounter information gaps or make assumptions not confirmed by the user. Phase 4 MUST update the Status column from Open to Resolved for each item it resolves. Before appending, MUST read the existing file to avoid duplicate entries.