Shared execution doctrine for all mx-* skills: model dispatch and escalation, delegation templates, judgment rubrics (when done / when to ask / wrong-direction signals), verification contracts, maintenance protocol. Consult when dispatching sub-agents, when repeatedly failing, or before editing any mx-harness file. Usage: /mx-doctrine [topic]
Full development workflow orchestrator: brainstorm → plan → scope analysis → worktree → convergent TDD/review loop → verify → PR. One human gate (spec approval); all other gates auto-proceed. Use when starting a new feature or significant change from scratch. Usage: /mx-flow <topic>; /mx-flow finish <name> for post-merge cleanup.
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub, GitLab, or Bitbucket — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name]
Multi-perspective code review for git diffs or whole files: three parallel reviewers (Senior Engineer, SRE Guardian, Future Maintainer) synthesized by a Tech Lead, with language-specific standards (Go, C#). Use to review local changes before commit/merge. Usage: /mx-team-review [diff-spec] or /mx-team-review --repo <path>
Turn a rough idea into an approved design spec before any code is written: one question at a time, 2-3 distinct approaches with trade-offs, spec and ADR written to ~/.mx/<project>/<name>/. Hard gate: no implementation until the user approves the spec. Use at the start of any feature or non-trivial fix.
Commit all pending changes following the project's commit message convention. Inspects staged and unstaged changes, groups them by logical concern, stages and commits each group separately. Enforces: one logical change per commit, type prefix, 50-char subject limit, numbered body items in "reason → change" format, English only. Usage: /mx-commit [--auto]
Triage review findings — from local mx-team-review reports or GitHub/GitLab PR comments — into fix / track / skip buckets by validity, severity (P0-P3), and cost, then execute approved decisions. Use after mx-team-review or when handling PR feedback before merge. Usage: /mx-review-triage [--source review | --source pr <id|url>]
Show the current stage, progress, and next action for all features in the current project. Scans ~/.mx/<project>/ for specs/ADRs and .mx/ (project-local) for plans, worktrees, and temp files. Detects broken states and gives concrete recovery instructions. Use whenever you lose track of where you are in the mx-flow workflow.