@ktpartners/dgs-platform 2.6.2

package/deliver-great-systems/workflows/set-profile.md

@@ -0,0 +1,83 @@
+<purpose>
+Switch the model profile used by DGS agents. Controls which Claude model each agent uses, balancing quality vs token spend.
+</purpose>
+
+<context_tier>none</context_tier>
+
+<required_reading>
+Read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
+
+<process>
+
+<step name="validate">
+Validate argument:
+
+```
+if $ARGUMENTS.profile not in ["quality", "balanced", "budget"]:
+  Error: Invalid profile "$ARGUMENTS.profile"
+  Valid profiles: quality, balanced, budget
+  EXIT
+```
+</step>
+
+<step name="ensure_and_load_config">
+Ensure config exists and load current state:
+
+```bash
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-ensure-section
+INIT=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" state load)
+if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
+```
+
+This creates `dgs.config.json` with defaults if missing and loads current config.
+</step>
+
+<step name="update_config">
+Read current config from state load or directly:
+
+Update `model_profile` field:
+```json
+{
+  "model_profile": "$ARGUMENTS.profile"
+}
+```
+
+Write updated config back to `dgs.config.json`.
+</step>
+
+<step name="confirm">
+Display confirmation with model table for selected profile:
+
+```
+✓ Model profile set to: $ARGUMENTS.profile
+
+Agents will now use:
+
+[Show table from MODEL_PROFILES in dgs-tools.cjs for selected profile]
+
+Example:
+| Agent | Model |
+|-------|-------|
+| dgs-planner | opus |
+| dgs-executor | sonnet |
+| dgs-verifier | haiku |
+| ... | ... |
+
+Next spawned agents will use the new profile.
+```
+
+Map profile names:
+- quality: use "quality" column from MODEL_PROFILES
+- balanced: use "balanced" column from MODEL_PROFILES
+- budget: use "budget" column from MODEL_PROFILES
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Argument validated
+- [ ] Config file ensured
+- [ ] Config updated with new model_profile
+- [ ] Confirmation displayed with model table
+</success_criteria>

package/deliver-great-systems/workflows/settings.md

@@ -0,0 +1,470 @@
+<purpose>
+Interactive configuration of DGS workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates ${config_path} with user preferences. Optionally saves settings as global defaults (~/.dgs/defaults.json) for future projects.
+</purpose>
+
+<context_tier>lite</context_tier>
+
+<required_reading>
+Read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
+
+<process>
+
+<step name="initialize" priority="first">
+Load planning context:
+
+```bash
+INIT=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" init progress)
+TIER_FILES=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" context load-tier lite --raw 2>/dev/null)
+```
+
+Extract: `project_root`, `config_path` as needed by the workflow.
+Use `TIER_FILES` JSON `files` array for project context (PROJECT.md, STATE.md, config.json).
+</step>
+
+<step name="ensure_and_load_config">
+Ensure config exists and load current state:
+
+```bash
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-ensure-section
+INIT=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" state load)
+if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
+```
+
+Creates `${config_path}` with defaults if missing and loads current config values.
+</step>
+
+<step name="read_current">
+```bash
+cat ${config_path}
+```
+
+Parse current values (default to `true` if not present):
+- `workflow.research` — spawn researcher during plan-phase
+- `workflow.plan_check` — spawn plan checker during plan-phase
+- `workflow.verifier` — spawn verifier during execute-phase
+- `workflow.nyquist_validation` — validation architecture research during plan-phase (default: true if absent)
+- `workflow.codereview` — spawn code reviewer after plan execution (default: false if absent)
+- `model_profile` — which model each agent uses (default: `balanced`)
+- `git.branching_strategy` — branching approach (default: `"none"`)
+- `git.base_branch` — integration target branch for code repos (default: `"main"`)
+- `workflow.discipline` — whether CLAUDE.md workflow routing is active (default: true if absent)
+
+Also detect whether `./CLAUDE.md` exists and contains a DGS section:
+```bash
+CLAUDE_MD_EXISTS=$(test -f ./CLAUDE.md && echo "true" || echo "false")
+CLAUDE_MD_HAS_DGS=$(grep -l 'DGS:BEGIN' ./CLAUDE.md 2>/dev/null && echo "true" || echo "false")
+```
+</step>
+
+<step name="detect_old_templates">
+After loading current config, check if the branch templates use old defaults without `{project}`:
+
+```bash
+CURRENT_PHASE_TPL=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-get git.phase_branch_template --raw 2>/dev/null)
+CURRENT_MILESTONE_TPL=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-get git.milestone_branch_template --raw 2>/dev/null)
+```
+
+If either template is set AND does not contain `{project}`, and `branching_strategy` is not `"none"`, show migration hint before the settings questions:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ DGS ► BRANCH TEMPLATE UPDATE AVAILABLE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Your branch templates don't include the project name, which can cause
+collisions in multi-project setups.
+
+Current:  {current_phase_tpl}
+Suggested: dgs/{project}/phase-{phase}-{slug}
+
+Current:  {current_milestone_tpl}
+Suggested: dgs/{project}/{milestone}-{slug}
+```
+
+Use AskUserQuestion:
+```
+AskUserQuestion([{
+  question: "Update branch templates to include project name?",
+  header: "Templates",
+  multiSelect: false,
+  options: [
+    { label: "Yes (Recommended)", description: "Updates templates to include {project} for multi-project safety" },
+    { label: "No", description: "Keep current templates" }
+  ]
+}])
+```
+
+If "Yes": write updated templates to config.json using config-set:
+```bash
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-set git.phase_branch_template "dgs/{project}/phase-{phase}-{slug}"
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-set git.milestone_branch_template "dgs/{project}/{milestone}-{slug}"
+```
+
+Show confirmation:
+```
+Updated branch templates to include {project}.
+Branch names will now look like: dgs/your-project/phase-03-auth
+
+Note: Existing branches using the old format will NOT be renamed.
+Only new branches will use the updated format.
+```
+
+If templates already contain `{project}` or branching_strategy is "none": skip this step silently.
+</step>
+
+<step name="present_settings">
+Use AskUserQuestion with current values pre-selected:
+
+```
+AskUserQuestion([
+  {
+    question: "Which model profile for agents?",
+    header: "Model",
+    multiSelect: false,
+    options: [
+      { label: "Quality", description: "Opus everywhere except verification (highest cost)" },
+      { label: "Balanced (Recommended)", description: "Opus for planning, Sonnet for execution/verification" },
+      { label: "Budget", description: "Sonnet for writing, Haiku for research/verification (lowest cost)" }
+    ]
+  },
+  {
+    question: "Spawn Plan Researcher? (researches domain before planning)",
+    header: "Research",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Research phase goals before planning" },
+      { label: "No", description: "Skip research, plan directly" }
+    ]
+  },
+  {
+    question: "Spawn Plan Checker? (verifies plans before execution)",
+    header: "Plan Check",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Verify plans meet phase goals" },
+      { label: "No", description: "Skip plan verification" }
+    ]
+  },
+  {
+    question: "Spawn Execution Verifier? (verifies phase completion)",
+    header: "Verifier",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Verify must-haves after execution" },
+      { label: "No", description: "Skip post-execution verification" }
+    ]
+  },
+  {
+    question: "Auto-advance pipeline? (discuss → plan → execute automatically)",
+    header: "Auto",
+    multiSelect: false,
+    options: [
+      { label: "No (Recommended)", description: "Manual /clear + paste between stages" },
+      { label: "Yes", description: "Chain stages via Task() subagents (same isolation)" }
+    ]
+  },
+  {
+    question: "Enable Nyquist Validation? (researches test coverage during planning)",
+    header: "Nyquist",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "Research automated test coverage during plan-phase. Adds validation requirements to plans. Blocks approval if tasks lack automated verify." },
+      { label: "No", description: "Skip validation research. Good for rapid prototyping or no-test phases." }
+    ]
+  },
+  {
+    question: "Spawn Code Reviewer? (multi-agent code review after plan execution)",
+    header: "Code Review",
+    multiSelect: false,
+    options: [
+      { label: "No (Default)", description: "Skip code review after plan execution" },
+      { label: "Yes", description: "Run 3-pass, 9-agent code review after each plan commits. Auto-fixes low-risk issues." }
+    ]
+  },
+  {
+    question: "Git branching strategy?",
+    header: "Branching",
+    multiSelect: false,
+    options: [
+      { label: "None (Recommended)", description: "Commit to current branch (fine for single projects)" },
+      { label: "Per Phase", description: "Branch per phase, review before merging" },
+      { label: "Per Milestone", description: "Branch per project, merge all at end (for parallel projects)" }
+    ]
+  },
+  {
+    question: "Base branch for code repos? (integration target for branching operations)",
+    header: "Git",
+    multiSelect: false,
+    freeform: true,
+    placeholder: currentConfig.base_branch || "main"
+  }
+])
+```
+</step>
+
+<step name="present_discipline_settings">
+Read the current discipline state:
+
+```bash
+DISCIPLINE_STATE=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-get workflow.discipline --raw 2>/dev/null || echo "true")
+```
+
+Determine current state display:
+- If `DISCIPLINE_STATE` is `"true"`: current is "On"
+- If `DISCIPLINE_STATE` is `"false"`: current is "Off"
+- Default (key missing): treat as "On" (matches init-product default)
+
+Also check CLAUDE.md file state:
+```bash
+CLAUDE_MD_EXISTS=$(test -f ./CLAUDE.md && echo "true" || echo "false")
+```
+
+Display current state inline before prompting:
+```
+Workflow Discipline: {On/Off} {(CLAUDE.md present) or (CLAUDE.md not found)}
+```
+
+Use AskUserQuestion:
+```
+AskUserQuestion([{
+  question: "Workflow discipline routes code changes through /dgs:* commands via CLAUDE.md. Currently: {On/Off}.",
+  header: "Workflow Discipline",
+  multiSelect: false,
+  options: [
+    { label: "On", description: "CLAUDE.md with DGS command routing rules (creates if missing)" },
+    { label: "Off", description: "Remove DGS routing rules from CLAUDE.md" }
+  ]
+}])
+```
+
+Pre-select the option matching current state.
+
+**If user selects "On" (toggle on or keep on):**
+
+Read the template:
+```bash
+CLAUDE_TEMPLATE=$(cat ~/.claude/deliver-great-systems/templates/claude-md.md)
+```
+
+Check if `./CLAUDE.md` exists:
+
+- **If CLAUDE.md does NOT exist:** Create `./CLAUDE.md` with DGS section delimiters:
+
+```
+<!-- DGS:BEGIN — managed by deliver-great-systems, do not edit this section manually -->
+{CLAUDE_TEMPLATE content}
+<!-- DGS:END -->
+```
+
+- **If CLAUDE.md exists but has NO DGS section** (no `<!-- DGS:BEGIN` found): Append DGS section to end:
+
+```
+{existing content}
+
+<!-- DGS:BEGIN — managed by deliver-great-systems, do not edit this section manually -->
+{CLAUDE_TEMPLATE content}
+<!-- DGS:END -->
+```
+
+- **If CLAUDE.md exists AND has DGS section** (`<!-- DGS:BEGIN` found): Replace everything from `<!-- DGS:BEGIN` line through `<!-- DGS:END -->` line (inclusive) with the latest template version. Preserve all content before and after the DGS section.
+
+Set config:
+```bash
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-set workflow.discipline true
+```
+
+Display: `Workflow discipline: On`
+
+**If user selects "Off" (toggle off):**
+
+Check current state -- if already off, just confirm and skip:
+```
+Workflow discipline is already off.
+```
+
+If currently on, show consequences and confirm:
+
+```
+AskUserQuestion([{
+  question: "Turning off workflow discipline means Claude will no longer be routed through /dgs:* commands for code changes. The DGS section will be removed from CLAUDE.md (any content you wrote outside the DGS section will be preserved). Continue?",
+  header: "Confirm",
+  multiSelect: false,
+  options: [
+    { label: "Yes, turn off", description: "Remove DGS routing rules from CLAUDE.md" },
+    { label: "Cancel", description: "Keep workflow discipline on" }
+  ]
+}])
+```
+
+**If "Yes, turn off":**
+
+Check `./CLAUDE.md`:
+
+- **If CLAUDE.md exists with DGS section:** Read file content. Remove everything from the `<!-- DGS:BEGIN` line through the `<!-- DGS:END -->` line (inclusive). Trim any resulting double-blank-lines down to single blank lines. If the remaining content (after trimming whitespace) is empty, delete the entire CLAUDE.md file. Otherwise write the cleaned content back.
+
+- **If CLAUDE.md exists without DGS section:** Leave it unchanged (nothing to remove).
+
+- **If CLAUDE.md does not exist:** Nothing to do.
+
+Set config:
+```bash
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-set workflow.discipline false
+```
+
+Display: `Workflow discipline: Off`
+
+**If "Cancel":**
+
+Display: `Kept workflow discipline on.`
+Do not change config or CLAUDE.md.
+</step>
+
+<step name="present_review_settings">
+Load current review configuration:
+
+```bash
+REVIEW=$(node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" review-config --raw)
+```
+
+Parse the JSON to get `reviewers.openai.api_key`, `reviewers.openai.model`, `reviewers.gemini.api_key`, `reviewers.gemini.model`, and `max_rounds`.
+
+Display review key status (DO NOT prompt for keys -- users edit review-keys.json directly):
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Review Configuration (read-only)
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| Setting           | Status        |
+|-------------------|---------------|
+| OpenAI API Key    | {set/not set} |
+| OpenAI Model      | {model}       |
+| Gemini API Key    | {set/not set} |
+| Gemini Model      | {model}       |
+| Max Rounds        | {N}           |
+
+To configure review keys, edit: review-keys.json (in your planning root)
+```
+
+Do NOT use AskUserQuestion for any review settings.
+</step>
+
+<step name="update_config">
+Merge new settings into existing config:
+
+```json
+{
+  ...existing_config,
+  "model_profile": "quality" | "balanced" | "budget",
+  "workflow": {
+    "research": true/false,
+    "plan_check": true/false,
+    "verifier": true/false,
+    "auto_advance": true/false,
+    "nyquist_validation": true/false,
+    "codereview": true/false,
+    "discipline": true/false
+  },
+  "git": {
+    "branching_strategy": "none" | "phase" | "milestone",
+    "base_branch": "main" | user_answer
+  }
+}
+```
+
+Write updated config to `${config_path}`. Review keys are NOT stored in config -- they live in review-keys.json (edited directly by the user).
+</step>
+
+<step name="save_as_defaults">
+Ask whether to save these settings as global defaults for future projects:
+
+```
+AskUserQuestion([
+  {
+    question: "Save these as default settings for all new projects?",
+    header: "Defaults",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "New projects start with these settings (saved to ~/.dgs/defaults.json)" },
+      { label: "No", description: "Only apply to this project" }
+    ]
+  }
+])
+```
+
+If "Yes": write the same config object (minus project-specific fields like `brave_search`) to `~/.dgs/defaults.json`:
+
+```bash
+mkdir -p ~/.dgs
+```
+
+Write `~/.dgs/defaults.json` with:
+```json
+{
+  "mode": <current>,
+  "granularity": <current>,
+  "model_profile": <current>,
+  "commit_docs": <current>,
+  "parallelization": <current>,
+  "branching_strategy": <current>,
+  "workflow": {
+    "research": <current>,
+    "plan_check": <current>,
+    "verifier": <current>,
+    "auto_advance": <current>,
+    "nyquist_validation": <current>,
+    "codereview": <current>,
+    "discipline": <current>
+  }
+}
+```
+</step>
+
+<step name="confirm">
+Display:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ DGS ► SETTINGS UPDATED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| Setting              | Value |
+|----------------------|-------|
+| Model Profile        | {quality/balanced/budget} |
+| Plan Researcher      | {On/Off} |
+| Plan Checker         | {On/Off} |
+| Execution Verifier   | {On/Off} |
+| Auto-Advance         | {On/Off} |
+| Nyquist Validation   | {On/Off} |
+| Code Reviewer        | {On/Off} |
+| Git Branching        | {None/Per Phase/Per Milestone} |
+| Base Branch          | {main/develop/etc.} |
+| Workflow Discipline  | {On/Off} |
+| OpenAI Key           | {set/not set} (edit review-keys.json) |
+| Gemini Key           | {set/not set} (edit review-keys.json) |
+| Saved as Defaults    | {Yes/No} |
+
+These settings apply to future /dgs:plan-phase and /dgs:execute-phase runs.
+
+Quick commands:
+- /dgs:set-profile <profile> — switch model profile
+- /dgs:plan-phase --research — force research
+- /dgs:plan-phase --skip-research — skip research
+- /dgs:plan-phase --skip-verify — skip plan check
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Current config read
+- [ ] User presented with 9 workflow settings (profile + 6 workflow toggles + git branching + base branch)
+- [ ] User shown review key status (read-only)
+- [ ] Config updated with model_profile, workflow, and git sections
+- [ ] User offered to save as global defaults (~/.dgs/defaults.json)
+- [ ] Changes confirmed to user
+- [ ] User shown workflow discipline toggle with current state
+- [ ] Toggle on creates/updates CLAUDE.md with DGS section delimiters
+- [ ] Toggle off removes DGS section with confirmation, preserving user content
+</success_criteria>