Skip to main content

Overview

The settings command provides interactive configuration of GSD workflow agents and model profile through a guided multi-question prompt. Configure which optional agents run and which Claude models are used.

Syntax

How It Works

  1. Ensures config exists - Creates ~/.claude/get-shit-done/config.json with defaults if missing
  2. Reads current settings - Loads and parses existing configuration
  3. Interactive 5-question prompt - Presents choices with current values pre-selected
  4. Merges config - Updates only changed settings
  5. Writes config file - Saves merged configuration
  6. Displays confirmation - Shows updated settings with quick command references

Configuration Options

1. Model Profile

Controls which Claude model each agent uses. Options:
  • quality - Claude Opus for all agents (highest quality, highest cost)
  • balanced - Sonnet for most, Opus for critical agents (recommended)
  • budget - Sonnet for all agents (lower cost, good quality)

2. Research Agent

Runs codebase research before planning phases. Options:
  • enabled - Research runs by default (recommended)
  • disabled - Skip research, faster planning
Affects: /gsd:plan-phase

3. Plan Checker

Validates plans before execution, suggests improvements. Options:
  • enabled - Plans reviewed before execution (recommended)
  • disabled - Execute plans without review
Affects: /gsd:execute, /gsd:quick --full

4. Verifier Agent

Validates implementation after execution. Options:
  • enabled - Implementation verified against plan (recommended)
  • disabled - Skip verification, faster execution
Affects: /gsd:execute, /gsd:quick --full

5. Git Branching

Controls branch creation during phase execution. Options:
  • enabled - Create feature branch per phase
  • disabled - Work directly on current branch (default)
Affects: /gsd:execute

Usage Examples

Initial configuration

Interactive prompt:

Change to budget mode

You select:
Confirmation:

Quality mode for critical project

You select:
Confirmation:

Model Profiles

Quality Profile

Cost: ~3-5x vs balanced Quality: Highest reasoning, best for complex work
Cost: ~1.5-2x vs budget Quality: High quality where it matters, efficient elsewhere

Budget Profile

Cost: Baseline Quality: Good for most tasks, excellent value

Config File Location

Format:

Default Settings

If no config exists, GSD uses:
Balanced quality and cost, all quality gates enabled.

Per-Command Overrides

Settings can be overridden per command:

When to Change Settings

Use Quality Profile

  • Production systems
  • Complex business logic
  • Security-critical code
  • Regulatory compliance
  • High-stakes projects

Use Balanced Profile

  • Most projects (recommended default)
  • Balances cost and quality
  • Full-stack applications
  • Team development

Use Budget Profile

  • Learning projects
  • Prototyping
  • Simple CRUD apps
  • Personal projects
  • Token budget constraints

Quick Commands

Faster ways to change specific settings:
  • set-profile - Quick model profile switching
  • plan-phase - Uses research setting
  • execute - Uses verifier and branching settings
  • quick - Always skips optional agents (—full overrides)