Plan Definition

Wiggum plans are defined in TOML files. A plan describes your project metadata, phases, tasks, preflight commands, and orchestrator configuration.

Minimal example

[project]
name = "my-app"
description = "A web API for widget management"
language = "rust"
path = "/path/to/project"

[[phases]]
name = "Foundation"
order = 1

[[phases.tasks]]
slug = "project-setup"
title = "Initialize project structure"
goal = "Set up the repo with build tooling and CI"
depends_on = []

[[phases.tasks]]
slug = "domain-model"
title = "Define domain entities"
goal = "Create the core domain types and traits"
depends_on = ["project-setup"]

Per-task evaluation criteria

You can attach verifiable exit criteria to any task. These are embedded in the generated task file and registered in features.json for the evaluator agent to score:

[[phases.tasks]]
slug = "domain-model"
title = "Define domain entities"
goal = "Create the core domain types and traits"
depends_on = ["project-setup"]
evaluation_criteria = [
    "All domain types implement Serialize/Deserialize",
    "No business logic leaks into the infrastructure layer",
]

Four default criteria are added to every task automatically: build succeeds, all tests pass, linter clean, and implementation matches goal.

Target selection

Wiggum can emit artifacts for one or more AI coding tools at once. Add a [targets] section to your plan to control which tools’ agent files are generated. See Targets for the full reference.

[targets]
vscode      = true   # default when [targets] is absent — GitHub Copilot prompt files
opencode    = false  # .opencode/agents/wiggum-*.md
claude      = false  # CLAUDE.md + .claude/settings.json (full Claude Code support)
agent-rules = false  # .cursorrules + .windsurfrules + .github/copilot-instructions.md

When the [targets] section is absent, Wiggum defaults to vscode = true and the other targets false — this matches the pre-[targets] behavior exactly. The CLI flag --target <vscode|opencode|claude|agent-rules|all> overrides the plan.

Sections

• Project Configuration — Project metadata and language settings
• Phases and Tasks — Organizing work into phases with dependency-ordered tasks and task kinds
• Preflight and Orchestrator — Build/test/lint commands, failure policy, orchestrator persona, and evaluator configuration
• Workspaces — Orchestrate multiple plans as a unit with workspace.toml

Checking plan quality

Before generating, score your plan with wiggum check:

wiggum check plan.toml

This evaluates the plan on five dimensions (granularity, dependency health, coverage, richness, and token budget) and prints actionable suggestions. Plans scoring below 7/10 exit with a non-zero status so they can be caught in CI.