Manage Config Skill

Manages project-level infrastructure configuration in .plan/marshal.json.

Scope: hybrid means this skill manages project-level settings (marshal.json persists across plans) while also providing plan-phase-specific configuration (branching, commit strategy, verification steps).

Enforcement

Base contract: See manage-contract.md for shared enforcement rules, TOON output format, and error response patterns.

Skill-specific constraints:

• Do not bypass initialization (marshal.json must exist before queries)
• Domain configuration follows the noun-verb pattern documented in the API Reference
• Phase configuration uses the plan {phase} {verb} pattern
• Every addition, removal, relocation, or rename of a config field MUST satisfy the governance rules in standards/config-design-principles.md — ownership boundaries (Rule 1 foreign-system, Rule 2 meta-project convention), placement (Rule 5), anti-speculation (Rule 6), and the lossless field-migration mechanics (Rule 3).

Workflow: Initialize Configuration

Pattern: Script Automation