marketplace/bundles/pm-dev-java-cui/skills/plan-marshall-plugin/SKILL.md
CUI Java domain manifest for plan-marshall workflow integration
npx skillsauth add cuioss/plan-marshall plan-marshall-pluginInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Domain manifest skill providing CUI-specific Java patterns.
Execution mode: Extension manifest; modify only via Extension API contract.
Prohibited actions:
Constraints:
get_skill_domains() from ExtensionBaseDeclares the CUI Java domain including:
All configuration is in extension.py which implements the Extension API. Every
hook this bundle overrides:
| Hook | Purpose |
|------|---------|
| get_skill_domains() | Domain metadata with profiles |
| applies_to_module() | Applicability check — additive to the java domain, keyed on Maven/Gradle build systems plus de.cuioss:* dependency signals |
| provides_recipes() | Contributes the cui-logging-enforce recipe |
| provides_domain_verb() | Declares the marker-detect verb, resolving to pm-dev-java-cui:search-markers — the domain-owned OpenRewrite marker detector. Core resolves it null-on-absent, so a project without java-cui active runs no marker gate. See plan-marshall:extension-api/standards/ext-point-domain-verb.md. |
| config_defaults() | Seeds CUI-standard Maven profile mappings and the internal-profile skip list (write-once) |
This extension is discovered by:
skill-domains get-available - Lists available domainsskill-domains configure --domains java-cui - Configures the domainmarshall-steward wizard - Domain selectiondevelopment
Domain-owned OpenRewrite log-line finding parser for the java-cui domain — parses the
development
Domain-owned OpenRewrite marker detection for the java-cui domain — scans Java/Kotlin sources for cui-rewrite TODO markers, categorizes them by recipe, and fails the gate on any detected marker
development
Operator control surface for the marshalld build server — enrol/drop a project in the machine-global registry (the opt-in enable signal and anti-laundering wall), manage the daemon lifecycle (start, stop, drain, status, install, upgrade) version-pinned to the verified bundle copy, and inspect the daemon's per-project interaction-audit log (read-only)
tools
The tiny build-consumption client for the marshalld build server — submit a build job, bounded long-poll for its result, ping the daemon identity, and preflight registry-plus-liveness in one call; consumption only, never provisioning or enrolment