Skip to content

Getting Started

mx-workflow is a development workflow plugin for Claude Code that covers the full dev lifecycle: planning, implementation, quality checks, conventional commits, E2E testing, and multi-agent team builds.

Before installing mx-workflow, make sure you have:

  • Claude Code CLI installed and working
  • git configured with SSH or HTTPS access to your repositories

There are three ways to install mx-workflow. Choose the one that fits your setup.

Section titled “Option A: Marketplace install (recommended)”

Register the mx-workflow repository as a plugin marketplace, then install:

Terminal window
# 1. Add the marketplace (one-time)
/plugin marketplace add https://github.com/joshtune/mx-workflow.git
# 2. Install the plugin
/plugin install mx@joshtune-mx-workflow

When prompted, choose a scope:

ScopeWhere it’s storedWho has access
user~/.claude/settings.jsonYou, in all projects
project.claude/settings.jsonEveryone on the team
local.claude/settings.local.jsonYou, on this machine only (gitignored)
Terminal window
# Clone the repo
git clone https://github.com/joshtune/mx-workflow.git ~/mx-workflow
# Load for current session
claude --plugin-dir ~/mx-workflow

This is temporary — the plugin is only available for that session.

Terminal window
# Clone the repo
git clone https://github.com/joshtune/mx-workflow.git ~/mx-workflow

Then add the path to your Claude Code settings. Edit ~/.claude/settings.json:

{
"plugins": ["~/mx-workflow"]
}

The plugin will load automatically in every session.

Once installed, type /mx: in Claude Code and you should see all commands in autocomplete.

Test with:

/mx:help

This displays the full command reference card.

Here is a typical walkthrough for your first session with mx-workflow:

/mx:prime

This reads key project files (like CLAUDE.md, package.json, tsconfig.json) and runs initial quality checks so Claude understands your project’s structure, conventions, and current health.

/mx:status

See what tools are available (linter, type checker, test runner) and whether the project is in a clean state. Fix any blockers before writing code.

If you have a ticket, create a branch first:

/mx:branch EIT-42 add-user-auth

Then create an implementation plan:

/mx:plan

The plan analyzes your codebase and produces a step-by-step implementation guide.

/mx:implement

This executes the plan step by step, running validation after each change and invoking specialized agents to review your code.

/mx:validate

Confirm that lint, type-checks, and tests still pass after your changes.

/mx:commit

Creates a conventional commit with auto-inferred scope, type, and ticket reference. No need to write the commit message yourself.

/mx:pr

Creates a pull request with an auto-generated summary. Use /mx:pr --draft if it is not ready for review yet.