quant-designlisted

# quant-design ## 1. Objective Create (or update) the `analysis_journal.md` file that acts as persistent memory across all analysis sessions. This journal records: - Project metadata and data paths - Research questions and hypotheses - Survey/dataset structure - An ordered analysis plan The journal is read by `quant-orchestrator` at the start of every subsequent session to understand context, track progress, and make intelligent routing decisions. **When to invoke:** - Starting a new analysis project (journal does not yet exist) - Adding new research questions or hypotheses mid-project - Reviewing or updating the study design **When NOT to invoke:** - When you want to run a specific analysis — use `quant-orchestrator` or invoke the analysis skill directly - When you just want to see project status — use `quant-orchestrator` --- ## 2. Pre-flight **Step 1 — Check for existing journal:** ``` Read("analysis_journal.md") ``` - If file **exists**: show project summary (§3A — returning user flow) - If file **does not exist**: begin new project setup (§3B — new project flow) **Step 2 — Check for column_metadata.json (if data-prep already ran):** ``` Read("output/data/column_metadata.json") ``` - If file **exists**: extract column names and detected types → use to pre-populate Q5 (survey structure) - If file **does not exist**: skip pre-population; ask user manually in Q5 --- ## 3. AskUserQuestion protocol ### 3A — Returning user (journal exists) Show the current journal