manage-config

Name: manage-config
Availability: InStock
Author: cuioss

Centralize project infrastructure configuration in marshal.json with domain defaults and CI settings.

4|Updated Jan 11, 2026

Search Tags:#automation #workflow #config #infrastructure #manage #marshal.json

Ready to run

npx skills add https://github.com/cuioss/plan-marshall --skill manage-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: manage-config
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/manage-config
Command: npx skills add https://github.com/cuioss/plan-marshall --skill manage-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires toon_parser, extension_discovery, and includes scripts (resource) components.

What problem does it solve?

This Skill centralizes the project-level infrastructure configuration stored in .plan/marshal.json, enabling consistent domain defaults, system retention, plan phase defaults, and CI settings across a repository.

Core Features & Use Cases

Centralized management of marshal.json, including skill_domains, system retention, plan defaults, and CI configuration
Per-domain defaults and optionals wiring with runtime profile resolution from bundles
Wizard-driven initialization and configuration, with domain discovery and extension data integration

Quick Start

Run the init command to create marshal.json with defaults, then tailor domains with skill-domains configure.

Frequently Asked Questions about manage-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I centralize project infrastructure configuration in marshal.json?▼

To centralize project infrastructure configuration, run the init command to generate marshal.json with default settings, then use the domain configuration command to tailor skill domains, plan defaults, and CI settings.

What is the best way to manage domain defaults and system retention settings across a repository?▼

Managing domain defaults and system retention settings is handled by centralizing these values in the marshal.json file, ensuring consistent infrastructure configuration applied uniformly across the entire repository.

How does wizard-driven initialization work for project CI configuration?▼

Wizard-driven initialization for CI configuration works by discovering available domains and integrating extension data from bundles, guiding you step-by-step to populate marshal.json with the required settings.

Do I need Python stdlib to manage plan phase defaults in marshal.json?▼

Yes, managing plan phase defaults requires Python stdlib for operations, as the process reads extension data from bundles and project files to properly apply configurations into marshal.json.

Can I configure per-domain defaults and optionals using this infrastructure management approach?▼

Yes, you can configure per-domain defaults and optionals, applying runtime profile resolution by reading extension data directly from bundles to wire the specific settings required by each domain.

Why does marshal.json configuration require YAML frontmatter in SKILL.md?▼

Marshal.json configuration requires YAML frontmatter in SKILL.md to properly expose the skill name and description, enabling the wizard-driven initialization to accurately discover domains and integrate extension data.