Claude-skill-registry-data manage-plan-marshall-config
Project-level infrastructure configuration for marshal.json
git clone https://github.com/majiayu000/claude-skill-registry-data
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/manage-plan-marshall-config" ~/.claude/skills/majiayu000-claude-skill-registry-data-manage-plan-marshall-config && rm -rf "$T"
data/manage-plan-marshall-config/SKILL.mdPlan-Marshall Config Skill
Manages project-level infrastructure configuration in
.plan/marshal.json.
What This Skill Provides
- Skill Domains: Implementation skill defaults and optionals per domain
- System Settings: Retention and cleanup configuration
- Plan Phase Configuration: Phase-specific settings (branching, compatibility, commit strategy, pipelines)
When to Activate This Skill
Activate this skill when:
- Initializing project configuration (
wizard)/marshall-steward - Querying implementation skills for a domain
- Managing retention settings
- Configuring plan phase settings
Workflow: Initialize Configuration
Pattern: Script Automation
Initialize marshal.json with defaults.
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config init
Workflow: Query Skill Domains
Pattern: Read-Process-Write
Get implementation skills for a specific domain.
Get Domain Defaults
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ skill-domains get-defaults --domain java-core
Output:
status: success domain: java-core defaults[1]: - pm-dev-java:java-core
Get Domain Optionals
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ skill-domains get-optionals --domain java-implementation
Validate Skill in Domain
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ skill-domains validate --domain java-core --skill pm-dev-java:java-lombok
Workflow: System Settings
Pattern: Read-Process-Write
Manage system-level infrastructure settings.
Get Retention Settings
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ system retention get
Set Retention Field
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ system retention set --field logs_days --value 7
Workflow: Plan Phase Configuration
Pattern: Read-Process-Write
Manage phase-specific plan configuration. Each phase has its own sub-noun.
Get Phase Configuration
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ plan phase-2-refine get
Get Specific Phase Field
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ plan phase-2-refine get --field compatibility
Set Phase Field
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ plan phase-5-execute set --field commit_strategy --value per_plan
Workflow: CI Command Lookup
Pattern: Lookup and Execute
Get a CI command by name, then execute with arguments.
Get CI Command
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ ci get-command --name issue-view
Output:
status: success name: issue-view command: python3 .plan/execute-script.py plan-marshall:tools-integration-ci:github issue view
Execute the Command
Parse the
command field from output, then execute with arguments:
python3 .plan/execute-script.py plan-marshall:tools-integration-ci:github issue view --issue 123
Available CI commands (registered via
ci_health persist):
- Create pull requestpr-create
- Get PR reviewspr-reviews
- Get PR commentspr-comments
- Check CI statusci-status
- Wait for CI completionci-wait
- Create issueissue-create
- View issue detailsissue-view
API Reference
Noun: skill-domains
| Verb | Parameters | Purpose |
|---|---|---|
| (none) | List all domains |
| | Get full domain config (returns nested structure for technical domains) |
| | Get default skills (returns for nested domains) |
| | Get optional skills (returns for nested domains) |
| | Set domain config (profiles read from extension.py, system domain only) |
| | Add new domain |
| | Check if skill valid (searches all profiles for nested domains) |
| (none) | Auto-detect domains from project files |
| | Get workflow skill extensions for domain |
| | Set workflow skill extension (types: outline, triage) |
| (none) | Get available domains based on detected build systems |
| | Configure selected domains with templates |
resolve-domain-skills
| Parameters | Purpose |
|---|---|
| Resolve skills for domain and profile (aggregates + ) |
Standard profiles:
implementation, module_testing, integration_testing, quality.
resolve-workflow-skill
| Parameters | Purpose |
|---|---|
| Resolve system workflow skill for phase (init, refine, outline, plan, execute, verify, finalize) |
Always returns from the
system domain's workflow_skills.
resolve-workflow-skill-extension
| Parameters | Purpose |
|---|---|
| Resolve domain-specific workflow extension (types: outline, triage) |
Returns null (not error) if extension doesn't exist for the domain.
get-workflow-skills
| Parameters | Purpose |
|---|---|
| (none) | Get all workflow skills from system domain (7-phase model) |
get-skills-by-profile
| Parameters | Purpose |
|---|---|
| Get skills organized by profile for architecture enrichment |
configure-task-executors
| Parameters | Purpose |
|---|---|
| (none) | Auto-discover profiles and register task executors (convention: profile X -> ) |
resolve-task-executor
| Parameters | Purpose |
|---|---|
| Resolve task executor skill for a profile (e.g., implementation, module_testing) |
Noun: ext-defaults
| Verb | Parameters | Purpose |
|---|---|---|
| | Get extension default value |
| | Set extension default value (always overwrites) |
| | Set value only if key does not exist (write-once) |
| (none) | List all extension defaults |
| | Remove extension default |
Noun: system
| Verb | Parameters | Purpose |
|---|---|---|
| (none) | Get all retention settings |
| | Set retention field |
Noun: plan
Phase-specific configuration using
plan {phase} {verb} pattern.
| Verb | Parameters | Purpose |
|---|---|---|
| | Get init phase configuration |
| | Set init phase field (branch_strategy) |
| | Get refine phase configuration |
| | Set refine phase field (confidence_threshold, compatibility) |
| | Get execute phase configuration |
| | Set execute phase field (commit_strategy) |
| | Get verify phase configuration |
| | Toggle generic verify step |
| | Toggle domain verify step |
| | Set verify max iterations |
| (none) | Get finalize phase configuration |
| | Toggle finalize step |
| | Set finalize max iterations |
Noun: ci
| Verb | Parameters | Purpose |
|---|---|---|
| (none) | Get full CI config |
| (none) | Get CI provider and repo URL |
| (none) | Get authenticated tools list |
| | Get single CI command by name (ready to execute) |
| | Set CI provider |
| | Set authenticated tools (comma-separated) |
| | Persist full CI config (provider, commands, tools) |
init
python3 .plan/execute-script.py plan-marshall:manage-plan-marshall-config:plan-marshall-config \ init [--force]
Data Model
marshal.json Location
.plan/marshal.json
Structure
The defaults template contains only
system domain. Technical domains (java, javascript, etc.) are added during project initialization based on detection or manual configuration. Technical domains store only bundle reference and workflow_skill_extensions -- profiles are loaded at runtime from extension.py.
Example (Java project after init):
{ "skill_domains": { "system": { "defaults": ["plan-marshall:ref-development-standards"], "optionals": ["plan-marshall:ref-development-standards"], "task_executors": { "implementation": "pm-workflow:task-implementation", "module_testing": "pm-workflow:task-module_testing", "integration_testing": "pm-workflow:task-integration_testing" } }, "java": { "bundle": "pm-dev-java", "workflow_skill_extensions": { "triage": "pm-dev-java:ext-triage-java" } } }, "system": { "retention": { "logs_days": 1, "archived_plans_days": 5, "memory_days": 5, "temp_on_maintenance": true } }, "plan": { "phase-1-init": { "branch_strategy": "direct" }, "phase-2-refine": { "confidence_threshold": 95, "compatibility": "breaking" }, "phase-5-execute": { "commit_strategy": "per_deliverable" }, "phase-6-verify": { "max_iterations": 5, "1_quality_check": true, "2_build_verify": true, "domain_steps": {} }, "phase-7-finalize": { "max_iterations": 3, "1_commit_push": true, "2_create_pr": true, "3_automated_review": true, "4_sonar_roundtrip": true, "5_knowledge_capture": true, "6_lessons_capture": true } } }
Standard Domains
System Domain
The
system domain contains task executors and base skills applied to all tasks.
| Field | Purpose |
|---|---|
| Base skills loaded for all tasks () |
| Optional base skills available for selection |
| Maps profiles to task executor skills (convention: profile X -> ) |
Technical Domains (Profile Structure)
Technical domains store
bundle reference and workflow_skill_extensions in marshal.json. Profiles are loaded at runtime from extension.py.
| Profile | Phase | Purpose |
|---|---|---|
| all | Skills loaded for all profiles |
| execute | Production code tasks |
| execute | Unit/module test tasks |
| execute | Integration test tasks |
| verify | Documentation, verification |
Available Domains:
| Domain | Bundle | Extensions |
|---|---|---|
| | triage |
| | triage |
| | outline, triage |
| | outline, triage |
Use
resolve-domain-skills --domain {domain} --profile {profile} to get aggregated skills.
Scripts
| Script | Notation |
|---|---|
| plan-marshall-config | |
Script characteristics:
- Uses Python stdlib only (json, argparse, pathlib, xml.etree)
- Outputs TOON to stdout
- Exit code 0 for success, 1 for errors
- Supports
flag--help
Integration Points
With plan-marshall Skill
- Called during wizard initialization
- Called from configuration menus
With Implementation Agents
provides skills to loadskill-domains get-defaults
provides available optionalsskill-domains get-optionals
With Cleanup
provides retention settingssystem retention get
Error Handling
All operations validate prerequisites before proceeding:
status: error error: marshal.json not found. Run command /marshall-steward first
Standard error conditions:
- Runmarshal.json not found
first/marshall-steward
- Runskill_domains not configured
first/marshall-steward
- Domain doesn't existUnknown domain: {name}