Skip to content

CLI Commands

Assemble provides commands that you type directly in your AI coding tool’s chat interface. These are not terminal commands — they’re prompts that Jarvis intercepts and routes.

The universal entry point. Describe what you need, and Jarvis routes it to the right agents.

/go fix the authentication bug in the login flow
/go add dark mode support to the dashboard
/go review the payment module for security issues

How it works:

  1. Jarvis classifies the domain (dev, marketing, security, etc.)
  2. Assesses complexity (TRIVIAL, MODERATE, COMPLEX)
  3. Matches a workflow or composes an ad-hoc one
  4. Executes with the appropriate agents

These trigger predefined workflows:

Trigger: feature-development workflow

/feature add user profile avatars
/feature implement real-time notifications

Steps: spec (professor-x) → plan (tony-stark) → tasks (captain-america) → implement (dev agents) → test (hawkeye)

Trigger: bug-fix workflow

/bugfix the search endpoint returns 500 on empty query
/bugfix login fails silently on expired tokens

Steps: diagnose (dev agent) → fix (dev agent) → regression test (hawkeye)

Trigger: code-review-pipeline workflow

/review
/review the payment processing module

Steps: code review (dev agents) → security review (punisher) → test coverage check (hawkeye)

Trigger: sprint-cycle workflow

/sprint plan the next 2-week iteration
/sprint retrospective for sprint 14

Steps: backlog review (captain-america) → priority (professor-x) → planning (captain-america)

Trigger: release-cycle workflow

/release prepare v2.1.0
/release candidate for production

Steps: changelog (captain-america) → final tests (hawkeye) → deploy prep (thor)

Trigger: mvp-launch workflow

/mvp launch the beta version of the booking system

Steps: spec (professor-x) → architecture (tony-stark) → implement (dev agents) → GTM (star-lord)

Trigger: security-audit workflow

/security audit the API endpoints
/security penetration test the auth system

Steps: vulnerability scan (punisher) → red team (microchip) → remediation (dev agents)

Trigger: tech-debt-reduction workflow

/refactor migrate from REST to GraphQL
/refactor extract the auth module into a service

Steps: analysis (tony-stark) → plan (tony-stark) → implement (dev agents) → test (hawkeye)

Trigger: seo-content-pipeline workflow

/seo create a content strategy for the blog
/seo optimize the landing page for "AI coding tools"

Steps: technical audit (black-widow) → content plan (storm) → GEO optimization (jean-grey)

Trigger: marketing-campaign workflow

/campaign launch for Product Hunt
/campaign Black Friday promotion

Steps: strategy (star-lord) → copy (loki) → ads (gamora) → social (ms-marvel)

Start a multi-agent brainstorming session.

/party should we use microservices or monolith?
/party marketing how do we position against Cursor?
/party all what's our biggest technical risk?

Rules:

  • Deadpool is always summoned (contrarian role)
  • 3-8 agents per session
  • Agents speak in character
  • Session persists until /dismiss

End a party session or dismiss a directly invoked agent.

/dismiss # End the party session
/dismiss @loki # Remove Loki from the session

Inspect and operate the Kanban board used by complex Spec-Driven workflows.

/board
/board status
/board resume
/board reprioritize T-004 before T-003

Use it to:

  • inspect current board status and ticket progression
  • resume execution after an interruption
  • re-prioritize tickets in _board.yaml when plans change

Show the command catalog and available agents.

/help

Invoke any agent directly with @agent-name:

@spider-man optimize the dashboard for Core Web Vitals
@bruce-banner add rate limiting to the /api/users endpoint
@loki write 3 tagline options for the pricing page
@beast create a dashboard for user engagement metrics

The agent stays in character until /dismiss.

Check the current workflow status during execution.

Transfer the current context to a different agent mid-workflow.

Strategic stress-test for critical decisions (only invoked explicitly):

@doctor-doom should we migrate to Kubernetes?