Recipe: marshal.json Configuration Audit

Generic, domain-invariant recipe skill that drives a plan to audit and improve .plan/marshal.json — the project configuration file setup / marshall-steward seed and every phase consumes. Where recipe-refactor-to-profile-standards brings code into compliance with profile standards and recipe-simplify-codebase sweeps surplus structure, this recipe inspects the live configuration along nine aspects and collects one deliverable per aspect.

The first five aspects are the structural-hygiene audit (default-surfacing, dead-config, docs, naming, units). Aspects 6–9 enforce the config-design governance principles — the ownership, house-rules, placement, and anti-speculation rules defined once in config-design-principles.md. The governance aspects xref that standard for every rule body and never inline it.

Like recipe-simplify-codebase it is an LLM-driven, SKILL.md-only deliverable-collection workflow (no scripts): the phase-3-outline recipe path loads it to produce a config-audit solution_outline.md.

Unlike the interactive recipes, this recipe hard-codes its (thoroughness, scope) cell instead of gathering it from the user. It implements the coverage-gathering contract — expand and consume — but skips the gather step, supplying a fixed identifier + expanded instruction per the contract's gather → expand → consume model.

Input Parameters

The recipe's discovery metadata (recipe_domain, recipe_profile) is declared in this skill's YAML frontmatter — manage-config list-recipes reads it from frontmatter, the sole source of truth; the markdown body is never scanned for these keys.

There is no recipe_scope / recipe_thoroughness input — the cell is fixed (see Step 1). The package-source parameter is omitted because the recipe audits a single config file and does not iterate packages. The recipe is plan-bound; it persists the resolved cell to status.json metadata.