Plan Marshall

<img align="right" width="300" src="doc/resources/planmarshall.png" alt="Plan Marshall">

[!CAUTION] Under Development. Not released yet. Alpha-Version

What is it?

Plan Marshall is an orchestration layer for AI coding assistants (currently Claude Code) that enforces consistency, reliability, and more predictable outputs. It packages a phase-driven planning workflow, a library of domain skills, and a marketplace of ten production bundles covering Java, JavaScript, Python, OCI containers, requirements, and plugin development.

Prerequisites

[!IMPORTANT] Python 3 is required and must be available as python3 in your PATH.

Verify with:

python3 --version

Installation (Claude Code)

Plan Marshall is distributed via a dist-claude orphan branch that tracks main. For the pinned-release flow and full distribution contract see Developer Documentation › Distribution.

Snapshot (tracks main)

/plugin marketplace add cuioss/plan-marshall@dist-claude
/plugin install plan-marshall@plan-marshall
/reload-plugins

Refresh later with /plugin marketplace update plan-marshall followed by /reload-plugins.

Getting Started

1. Configure the project

After installing the marketplace, run the setup wizard once per project:

/marshall-steward

The wizard configures .gitignore, generates the script executor, discovers project modules, initializes marshal.json, configures skill domains, and detects CI tools.

2. Create your first plan

The simplest way is to invoke /plan-marshall with no arguments and pick "Create new plan" from the interactive menu:

/plan-marshall

If you prefer a one-liner, pass a task= description directly — the init action is inferred:

/plan-marshall task="Add user authentication"

Or seed the plan from a GitHub issue:

/plan-marshall issue="https://github.com/cuioss/plan-marshall/issues/42"

/plan-marshall drives the six-phase lifecycle (init → refine → outline → plan → execute → finalize). Resume an existing plan with /plan-marshall plan="<plan-id>" — it auto-detects the current phase.

See User Guide › Getting Started for the full first-run walkthrough and User Guide › Commands for the complete /plan-marshall parameter reference.

Documentation

Section	Purpose
Concepts	How Plan Marshall is built and why — architecture, planning workflow, the execution-context dispatcher, the per-role model system.
User Guide	Operating Plan Marshall in a target project — installation, configuration, commands, terminal-title integration.
Developer Guide	Working on Plan Marshall itself — build system, marketplace generation pipeline, distribution, testing, workflow verification.

The canonical source of truth for every skill, standard, and extension point is co-located with the code under marketplace/bundles/. The doc/ tree is a thin navigational surface over it.

Available Bundles

Bundle	Purpose
plan-marshall	Core infrastructure, permissions, script execution, and the 6-phase planning workflow with task execution
pm-dev-java	Java development standards and agents
pm-dev-java-cui	CUI-specific Java development standards covering CuiLogger, test generators, value object contracts, and HTTP client patterns
pm-dev-frontend	JavaScript/CSS standards and tooling
pm-dev-frontend-cui	CUI-specific JavaScript project standards covering Maven integration, Quarkus DevUI, NiFi, and SonarQube
pm-dev-oci	OCI container standards and security best practices
pm-dev-python	Python domain extension with pyprojectx build operations
pm-documents	AsciiDoc documentation standards
pm-plugin-development	Marketplace component development
pm-requirements	Requirements engineering standards

License

This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0-only).

For organizations that cannot comply with the AGPL's copyleft requirements (e.g., proprietary or closed-source deployments), commercial licenses are available. Request a commercial license.

Support

• Report issues: https://github.com/cuioss/plan-marshall/issues
• Bundle documentation: marketplace/bundles/*/README.md