thecomputer07/qsd-settings

<objective> Interactive configuration of qsd workflow agents and model profile via multi-question prompt.

Routes to the settings workflow which handles:

• Config existence ensuring
• Current settings reading and parsing
• Interactive 5-question prompt (model, research, plan_check, verifier, branching)
• Config merging and writing
• Confirmation display with quick command references </objective>

<execution_context> @$HOME/.claude/qsd/workflows/settings.md </execution_context>

<process> **Follow the settings workflow** from `@$HOME/.claude/qsd/workflows/settings.md`.

The workflow handles all logic including:

1. Config file creation with defaults if missing
2. Current config reading
3. Interactive settings presentation with pre-selection
4. Answer parsing and config merging
5. File writing
6. Confirmation display </process>

<preflight_research_toggle> Field: workflow.preflight_research Valid values (exactly four): off | prompt | on | per-phase Default: off (absence of the field is treated identically to off — conservative, zero token spend)

Modes:

• off — never runs pre-flight research. Default. Zero new files, zero tokens.
• on — runs automatically before plan/execute phases.
• prompt — asks user (Y/N) before each run; default N on empty input (never auto-yes).
• per-phase — only runs for phases whose ROADMAP block contains preflight: true (sibling depth of Depends on: / Plans:).

CLI:

qsd-tools settings get workflow.preflight_research     # → 'off' on fresh project
qsd-tools settings set workflow.preflight_research on  # → persists 'on'
qsd-tools settings set workflow.preflight_research bogus
  # → non-zero exit, message: "Valid values: off|prompt|on|per-phase"

Output (when active) lands in .planning/research/preflight-<phaseId>-<YYYY-MM-DD>.md with YAML frontmatter and per-theme ## sections carrying cited bullets. The planner/executor skills Read this file at start when present. </preflight_research_toggle>