/config

name: config
description: "Configure settings: depth, model profiles, features, git, and gates."
allowed-tools: Read, Write, Bash, Glob, AskUserQuestion
argument-hint: "set <key> <value> | get <key> | list"

**STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 tokens. Begin executing Step 1 immediately.**

Step 0 — Immediate Output

**Before ANY tool calls**, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► CONFIGURATION                              ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

/pbr:settings — Configure Plan-Build-Run

Overview

Reads and writes `.planning/config.json`. Interactive configuration with AskUserQuestion.

References

• `references/config-reference.md` — Full config.json schema (54 fields, 16 feature toggles, validation rules)
• `references/model-profiles.md` — Model selection guide for agent spawning
• `references/questioning.md` — Questioning philosophy for config decision guidance
• `references/ui-brand.md` — Status symbols, banners, formatting for config display output

Flow

1. Load Current Config

Read `.planning/config.json`. If it doesn't exist, display:

╔══════════════════════════════════════════════════════════════╗
║  ERROR                                                       ║
╚══════════════════════════════════════════════════════════════╝

No Plan-Build-Run project found.

**To fix:** Run `/pbr:new-project` first.

1b. Quick Start Path (no arguments, first-time configuration)

If no `$ARGUMENTS` provided and this is the first time running `/pbr:settings` interactively (no prior config changes detected), present:

Use AskUserQuestion: question: "How would you like to configure?" header: "Setup" options:

• label: "Quick Start (recommended)"

description: "Answer 4 essential questions, sensible defaults for everything else"

• label: "Advanced (all fields)"

description: "Full config with 54 fields for granular customization"

**If user selects "Quick Start":**

First, check for global defaults: `pbr-tools config load-defaults` If defaults exist, use them as pre-populated values. Otherwise, use hardcoded defaults shown below.

Present 4 essential questions sequentially:

**Q1. Mode:** Use AskUserQuestion: question: "How do you want to work?" header: "Mode" options:

• label: "Interactive (default)" description: "Pause at key gates for your approval"
• label: "Autonomous" description: "Auto-proceed, only stop for critical decisions"

**Q2. Depth:** Use AskUserQuestion: question: "How thorough should planning be?" header: "Depth" options:

• label: "Standard (default)" description: "5-8 phases, includes research"
• label: "Quick" description: "3-5 phases, skip research, ~50% cheaper"
• label: "Comprehensive" description: "8-12 phases, full deep research, ~2x cost"

**Q3. Parallel agents:** Use AskUserQuestion: question: "Run agents in parallel when possible?" header: "Parallel" options:

• label: "Yes (default)" description: "Parallel execution of independent plans"
• label: "No" description: "Sequential execution only"

**Q4. Git branching:** Use AskUserQuestion: question: "Git branching strategy?" header: "Branching" options:

• label: "Phase (default, recommended)" description: "Branch per phase for safe undo"
• label: "None" description: "All work on current branch"

After 4 answers, write config.json with all other fields set to sensible defaults.

**Quick Start defaults:** mode=interactive, depth=standard, parallel=true, git.branching=phase

After writing config, offer: "Save these as your global defaults for future projects? (y/n)" If yes, run: `pbr-tools config save-defaults`

Display: "Config written. For full field reference, see `references/config-reference.md`."

Skip to Step 4 (Apply Changes confirmation).

**If user selects "Advanced":** proceed to Step 3 (Interactive Mode) below.

2. Parse Arguments

If `$ARGUMENTS` is provided, handle direct setting:

• `depth quick|standard|comprehensive` — set depth directly
• `model <agent> <model>` — set model for specific agent (e.g., `model executor sonnet`)
• `model-profile quality|balanced|budget|adaptive` — set all models at once using a preset
• `gate <gate-name> on|off` — toggle a gate
• `feature <feature-name> on|off` — toggle a feature (e.g., `feature auto_continue on`). When the user specifies a feature name without the `features.` prefix, automatically prepend `features.` before writing to config.
• `session_phase_limit <N>` — set the session phase limit directly (e.g., `/pbr:settings session_phase_limit 5`). Validate N is an integer between 0 and 20. Write to config.json at top level: `"session_phase_limit": N`. Display: "Session phase limit set to {N}. PBR will suggest pausing after {N} phases per session. (0 = disabled)"
• `git branching none|phase|milestone|disabled` — set branching strategy
• `git mode disabled` — disable git integration entirely
• `show` — display current config (default when no args)

3. Interactive Mode (no arguments or just `show`)

Display current configuration in a readable format:

Plan-Build-Run Configuration
=====================

Workflow:
  Depth: standard (balanced)
    Research: on   Plan-check: on   Verify: on
    Scan mappers: 4   Debug rounds: 5   Inline verify: off
  Mode: interactive
  Context Strategy: aggressive
  Session Phase Limit: 3 (pause after 3 phases)
  # When session_phase_limit is 0, display: "Session Phase Limit: disabled"

Features:
  ✓ Structured planning    ✓ Goal verification
  ✓ Context isolation       ✓ Atomic commits
  ✓ Session persistence     ✓ Research pha