config

name	config
description	This skill should be used when the user asks to configure Smith, set project preferences, customize agent behavior, or when any Smith command or agent needs to read project-local settings. It should also be used when the user asks "how do I configure Smith" or wants to change output paths.

Config

Smith supports per-project configuration via a .smith.local.yaml file in the project root. This file is user-managed, not committed to git, and provides project-specific settings that Smith agents and commands read at runtime.

File Location

project-root/
└── .smith.local.yaml

The file lives in the project root, not inside .claude/ or docs/.

Gitignore

This file should be added to .gitignore:

.smith.local.yaml

Remind the user to add this entry when creating the file for the first time.

Format

YAML

# Smith project configuration

# Directory where Smith writes research, plans, and reports.
# Default: docs/
output_directory: docs/

# Automatically critique and revise plans after initial generation.
# Default: false
plan_auto_critique: false

# Run git history analysis after research.
# Default: true
research_history: true

All fields are optional. An empty file or a file with only some fields is valid.

Schema

Field	Type	Default	Description
output_directory	string	docs/	Base directory where Smith writes documents. Research files go to <output_directory>/research/, plans to <output_directory>/plans/, and reports to <output_directory>/reports/.
plan_auto_critique	boolean	false	When true, the /plan command automatically runs one round of critique (Critic agent) and revision (Planner agent) after producing the initial plan.
research_history	boolean	true	When true, the /research command runs the Historian agent after the Researcher to append git history analysis. Set to false to skip the history phase.

The schema is intentionally open. Users may add additional keys as needed; agents should read what they recognize and ignore the rest.

Fallback Behavior

If .smith.local.yaml does not exist, or a field is absent, use the defaults listed in the schema. Configuration is always optional; its absence must never block execution.

Creating the Configuration File

When a user asks to configure Smith or set up project settings:

1. Ask what settings they want to configure (or suggest defaults based on the project).
2. Write .smith.local.yaml to the project root.
3. Check if .smith.local.yaml is already in .gitignore. If not, remind the user to add it.
4. Confirm the file was created and summarize the settings.

When This Skill Applies

• User asks to configure Smith, set preferences, or customize agent behavior.
• User asks "how do I configure Smith" or similar setup questions.
• A Smith command or agent needs to read project settings before starting work.
• User wants to change the output directory or other settings.