Where are the profile mappings stored?

All classifications and skip-lists are stored in your project's marshal.json file under the extension_defaults section.

What are canonical classifications?

Canonical classifications are standardized command categories used by Plan Marshall, such as integration-tests, coverage, benchmark, and quality-gate.

Can I map multiple profiles to the same canonical command?

Yes, you can map multiple profiles to one canonical command; however, only one primary command will be generated for that category.

What is an unmatched Maven profile?

An unmatched profile is a build profile in your pom.xml that the Plan Marshall discovery system doesn't automatically recognize as a standard command like 'coverage' or 'integration-tests'.

Does this skill run automatically?

Yes, it is typically invoked by the analyze-project-architecture workflow when it detects profiles that require manual classification.

Maven Profile Manager

Name: Maven Profile Manager
Author: cuioss

bycuioss

Deployment & DevOps

Classifies and maps unmatched Maven build profiles to canonical commands for consistent build orchestration.

About

The manage-maven-profiles skill is an essential component of the Plan Marshall orchestration layer, designed to resolve ambiguities in Java build systems. When automated discovery identifies Maven profiles that cannot be auto-matched to standard actions, this skill provides a structured workflow to classify them. Users can map custom profiles to canonical categories like integration-tests, coverage, or quality-gates, or choose to skip them entirely. By standardizing how Claude interacts with complex Maven configurations, it ensures more predictable build outputs and reliable CI/CD command generation across multi-module projects.

Key Features

Detection of unmatched (NO-MATCH-FOUND) Maven profiles
Interactive user-guided profile classification workflow
Mapping of custom profiles to canonical command standards
Support for deduplicated profile management across multiple modules
0 GitHub stars
Persistent configuration storage in marshal.json

Use Cases

Resolving unclassified profiles during project architecture discovery
Excluding internal or environment-specific profiles from build command generation
Mapping non-standard test profiles (e.g., 'it-local') to integration-test commands

About

Key Features

Detection of unmatched (NO-MATCH-FOUND) Maven profiles
Interactive user-guided profile classification workflow
Mapping of custom profiles to canonical command standards
Support for deduplicated profile management across multiple modules
0 GitHub stars
Persistent configuration storage in marshal.json

Use Cases

Resolving unclassified profiles during project architecture discovery
Excluding internal or environment-specific profiles from build command generation
Mapping non-standard test profiles (e.g., 'it-local') to integration-test commands