Workflow Commands

Massu AI provides 31 workflow commands organized into categories that enforce a structured, verification-first approach to AI-assisted development. These are not suggestions -- they are mandatory execution protocols that ensure every plan is thorough, every implementation is verified, and every commit meets quality standards.

Installation

All 31 commands are automatically installed when you run npx massu init. The command files are deployed into .claude/commands/ in your project directory and are available immediately in Claude Code.

The command definitions ship inside the @massu/core npm package. When you update @massu/core to a new version, run npx massu install-commands to get the latest command definitions without re-running full init.

# Re-install or update commands only
npx massu install-commands

Implementation Workflow

The core pipeline for structured development:

/massu-create-plan  -->  /massu-plan  -->  /massu-loop  -->  /massu-commit  -->  /massu-push
   (create)          (audit)      (implement)     (pre-commit)     (pre-push)

Development Tools

4 commands for day-to-day development tasks:

Quality & Verification

4 analysis commands for code quality:

Release & Ops

3 commands for release and operational tasks:

Productivity

6 commands for codebase hygiene, documentation, and guided workflows:

Extended Verification

4 commands for browser-level, dependency, documentation, and parity verification:

Internal Commands

The following commands are available only in the private repository. They provide deep audits, infrastructure checks, and specialized tooling that is not part of the public release.

Decision Tree

Not sure which command to use?

• Starting new work -- /massu-create-plan then /massu-plan then /massu-loop
• Scaffolding a feature -- /massu-new-feature
• Ready to commit -- /massu-commit
• Ready to push -- /massu-push (full) or /massu-push-light (fast ~90s)
• Tests are failing -- /massu-test
• Bug to diagnose -- /massu-debug
• Urgent production fix -- /massu-hotfix
• Restructuring code -- /massu-refactor
• Before a code review -- /massu-review
• Cutting a release -- /massu-release
• Project health check -- /massu-status
• Dependency concerns -- /massu-audit-deps
• Dead code / cleanup -- /massu-cleanup or /massu-dead-code (audit only)
• Generate documentation -- /massu-doc-gen or /massu-docs (audit only)
• Effort estimation -- /massu-estimate
• Run all VR checks -- /massu-verify
• UI end-to-end verification -- /massu-verify-playwright
• Feature parity check -- /massu-parity
• Dependency analysis -- /massu-deps
• TDD workflow -- /massu-tdd
• Golden-path guidance -- /massu-golden-path
• Step-by-step guide -- /massu-guide

Why This Workflow?

AI assistants are powerful but they can also be careless. Without a structured workflow:

• Plans have gaps that only surface during implementation
• Implementations claim completion without verification
• Commits include untested or type-unsafe code
• Removals leave behind orphaned references
• "100% complete" turns out to be 80% complete

The Massu AI workflow prevents all of these problems by requiring proof at every stage.

Core Principles

1. Plans Before Code

Every non-trivial change starts with a plan document. Plans live in docs/plans/ and include specific deliverables, file paths, and verification requirements.

2. Verification Before Claims

Every claim of completion requires a verification command and its output as proof. "I verified it" without showing the command output is treated as unverified.

3. Negative Verification for Removals

When a plan says "remove X", verification requires grep -rn "X" src/ returning 0 results. Partial removal is not removal.

4. All Items, Not Most Items

If a plan has 10 items, all 10 must be implemented and verified. Stopping at 8 and claiming complete is a protocol violation.

5. Protocols Are Mandatory

Slash commands are execution instructions, not suggestions. When a protocol says "loop until complete," it means loop until complete.