.planning/config.json. This file controls workflow behavior, model selection, git branching, and execution parameters.
Configuration File Location
/gsd:new-project or update later with /gsd:settings.
Full Schema
Core Settings
Execution mode:
interactive— Confirm at each decision pointyolo— Auto-approve all decisions
Phase breakdown granularity:
coarse— 3-5 phases (larger scope per phase)standard— 5-8 phases (balanced)fine— 8-12 phases (smallest atomic units)
Model tier for agents. See Model Profiles for per-agent breakdown:
quality— Opus for planning/execution, Sonnet for verificationbalanced— Opus for planning, Sonnet for execution/verificationbudget— Sonnet for code, Haiku for research/verification
Workflow Settings
Spawn researcher during
plan-phase to investigate domain, stack, and implementation patterns.Disable when: Domain is familiar, or conserving tokens.Spawn plan checker to verify plans achieve phase goals. Loops up to 3 times until plans pass verification.Disable when: Speed is critical, or plans are simple.
Spawn verifier after
execute-phase to confirm must-haves were delivered.Disable when: Manual verification is sufficient.Auto-chain discuss → plan → execute without stopping.Enable when: Running known phases in batch mode.Warning: Less control between stages.
Research automated test coverage during planning. Maps requirements to test commands.Disable when: Rapid prototyping or phases without tests.Outputs
{phase}-VALIDATION.md with feedback contract.Planning Settings
Track
.planning/ files in git.Set to false when:- Working on sensitive/private projects
- Don’t want planning artifacts in version control
false if .planning/ is in .gitignore.Add
--no-ignore to broad searches to include .planning/ directory.Enable when: Need to search planning docs for context.Parallelization Settings
Run independent plans simultaneously during
execute-phase.Parallelize at the plan level (multiple plans in same wave).
Parallelize individual tasks within a plan.Warning: Experimental. May cause race conditions.
Skip intermediate checkpoints during parallel execution.
Maximum number of executor agents running simultaneously.Adjust based on:
- API rate limits
- Cost tolerance
- System resources
Minimum plans required to trigger parallel execution.Single-plan phases always run sequentially.
Git Settings
Branch creation strategy. See Git Settings for details:
none— Commit to current branch (default)phase— Create branch per phasemilestone— Create branch for entire milestone
Template for phase branch names.Variables:
{phase}— Zero-padded phase number (e.g., “03”){slug}— Lowercase hyphenated phase name
gsd/phase-03-user-authenticationTemplate for milestone branch names.Variables:
{milestone}— Version identifier (e.g., “v1.0”){slug}— Lowercase hyphenated milestone name
gsd/v1.0-mvpConfirmation Gates
All gates default totrue in interactive mode.
Confirm project initialization details.
Confirm phase breakdown.
Confirm full roadmap before proceeding.
Confirm task breakdown within plans.
Confirm each plan before execution.
Confirm before executing next plan in sequence.
Review issues found during verification.
Confirm transitions between major stages.
In
yolo mode, all gates are automatically set to false.Safety Settings
Always confirm destructive operations (deletes, force pushes) regardless of mode.
Always confirm operations involving external services (API calls, deployments).
Updating Configuration
Interactive Update
Quick Profile Switch
Manual Edit
Edit.planning/config.json directly:
Global Defaults
Save settings as defaults for all new projects:- Configure current project:
/gsd:settings - When prompted, choose “Save as defaults”
- Settings written to
~/.gsd/defaults.json
/gsd:new-project inherit these defaults.
Command Overrides
Override config per-invocation:Related References
- Model Profiles — Per-agent model breakdown
- Workflow Agents — Research, plan_check, verifier details
- Git Settings — Branching strategies and templates