Skip to main content

From Request to Deliverable: The Marg Manual

Command reference

Every command on one page. Each row links back to the chapter that teaches it in full.

Daily operation

These are the commands you touch most, the ones that run a normal week.

Command

What it does

When (chapter)

/marg:route <request>

Routes the request to the right team.

Your default verb. (4)

/marg:onboard

Builds or rebuilds your profile.

First session, after pivots. (5)

/marg:btw <note>

Logs an update without routing.

Numbers changed mid-week. (5)

/marg:status

Reports work across teams.

Start of day. (6)

/marg:resume

Recovers interrupted work.

After a cut-off session. (7)

/marg:compact

Flushes session state to memory.

Before long runs. (8)

/marg:heartbeat

Promotes learnings, audits memory.

Roughly weekly. (8)

Flagship workflows

Each of these runs a full piece of work end to end rather than a single step.

Command

What it does

When (chapter)

/marg:blueprint

Generates the 90-Day Growth Blueprint.

A researched quarter plan. (19)

/marg:copywrite <brief>

Research-first copywriting.

Anything that must convert. (20)

/marg:research-log

Hypothesis ledger.

Accountable conclusions. (21)

/marg:research-watch

Standing watchlist.

Topics worth scanning. (21)

/marg:outcomes

Outcome ledger.

Did the advice work? (22)

/marg:compound

Captures solved problems.

Right after a solve. (23)

Documents in Drive

Drive work runs on plain language, not commands. Say "create a doc in Drive called X", "append this to the X doc", or "move the old draft to trash". Chapter 25 covers the patterns, and board-grade rendering routes through the document generator (chapter 16).

Developer-leaning extras

Two commands serve teams that run code reviews through Marg. /marg:review spawns parallel specialist reviewers over a codebase. /marg:triage walks the findings one by one for approve or skip. Both sit outside this manual's operator scope, and engineers find them self-explanatory in use.

The one habit that replaces most commands

When in doubt, describe what you need in plain language. Routing is the product, so the commands above are shortcuts into it, not a vocabulary you have to memorize. A request like "what should worry me this week?" needs no command at all.