.planning/config.json. The file is created automatically when you run /gsd-new-project and updated whenever you use the configuration commands. You can edit it directly or use the interactive configuration tools — both approaches produce the same result, and unrelated keys are always preserved on write.
Interactive configuration with /gsd-settings
Run/gsd-settings to open a six-section interactive wizard that walks you through every configurable workflow toggle and model profile setting. Answers are merged into your project’s config.json without overwriting keys you do not touch.
Section breakdown
Section breakdown
~/.gsd/defaults.json so future projects start from the same baseline configuration.
Targeted configuration with /gsd-config
Run/gsd-config for a more focused configuration experience. Without flags it covers the most common toggles. Use flags to access power-user settings, integrations, or to switch model profiles with a single command.
adaptive profile, run /gsd-config without flags and select it from the interactive wizard’s Model & Pipeline section.
Core settings
Workflow toggles
All workflow toggles follow the absent = enabled pattern. If a key is missing fromconfig.json, the feature defaults to true.
workflow.auto_advance: false is the safe default. Set it to true only when your requirements are stable and you are comfortable with phases advancing without manual confirmation.Common configuration combinations
The following combinations of settings are commonly used together:Global defaults
Save settings as global defaults so every new project starts from the same baseline. GSD reads~/.gsd/defaults.json when creating a new config.json and merges global defaults as the starting configuration. Per-project settings always override globals.
