What file format does this skill use for storage?

It uses the TOON format (config.toon) for storage, which provides a structured and human-readable way to define plan metadata and validation rules.

What is the primary purpose of the Manage Config skill?

It manages plan-specific settings in config.toon files, ensuring that AI coding tasks follow consistent rules for commits, branches, and domains.

Is schema validation included for configuration fields?

Yes, the skill validates fields like commit_strategy and branch_strategy against predefined allowed values to prevent workflow errors.

Can I manage multiple domains with this skill?

Yes, it supports managing arrays of domains (e.g., java, javascript) to ensure the AI uses the correct context for multi-domain plans.

Does this skill handle project-level settings?

No, it focuses on individual plan configurations. Project-wide settings are managed via the marshal.json file using the manage-plan-marshall-config skill.

Plan Configuration Manager

Name: Plan Configuration Manager
Author: cuioss

bycuioss

Productivity & Workflow

Manages plan-specific settings and domain configurations with schema validation for the Plan Marshall orchestration layer.

About

The Plan Configuration Manager skill provides a robust interface for handling per-plan settings within the Plan Marshall framework for Claude Code. It enables the creation, retrieval, and updating of 'config.toon' files, ensuring that AI-driven coding tasks adhere to specific commit strategies, branch protocols, and domain requirements. By providing nested field access and strict schema validation, this skill maintains consistency and reliability across complex development plans, allowing agents to operate within predictable boundaries and project-specific standards.

Key Features

Multi-domain array management for complex project orchestration
Automated initialization of plan-specific metadata
Validation of commit, PR, and branch strategies
Nested field access for granular get/set operations
Schema-validated management of per-plan configuration files
0 GitHub stars

Use Cases

Updating a plan's commit strategy dynamically to 'per_task' or 'per_plan'
Initializing a new development plan with specific language domains and verification rules
Retrieving domain assignments to route tasks to specialized AI workflow agents

About

Key Features

Multi-domain array management for complex project orchestration
Automated initialization of plan-specific metadata
Validation of commit, PR, and branch strategies
Nested field access for granular get/set operations
Schema-validated management of per-plan configuration files
0 GitHub stars

Use Cases

Updating a plan's commit strategy dynamically to 'per_task' or 'per_plan'
Initializing a new development plan with specific language domains and verification rules
Retrieving domain assignments to route tasks to specialized AI workflow agents