> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bossmode.ing/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Your First Directive

> Issue a directive end-to-end and watch the consigliere execute. This is the BossMode hello world.

## What is a directive?

A directive is a bounded work instruction issued to the consigliere. It has a scope, an owner (a capo role), and optionally a `requiresApproval` flag. The consigliere reads your standing orders, picks the right capo, and executes within the rules you've set.

## Step 1 — Get your context

Before issuing directives, pull the full operational context. This is the single call that returns everything:

```bash theme={null}
curl -sH "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  https://bossmode.ing/api/pro/context | jq
```

Response shape:

```json theme={null}
{
  "generatedAt": "2026-04-13T09:00:00Z",
  "sessionId": "ses_••••••",
  "operator": { "handle": "you", "tier": "pro" },
  "signals": [],
  "workPackets": [],
  "standingOrders": [],
  "metrics": { "revenue24h": 0, "signalsScored": 0 },
  "auditFeed": [],
  "guardian": { "mode": "guardrailed", "pending": 0 },
  "buyerContext": {}
}
```

## Step 2 — Issue your first directive

```bash theme={null}
curl -sX POST https://bossmode.ing/api/pro/directives \
  -H "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "directive": "Draft a follow-up email sequence for leads who downloaded the free training but did not book a call.",
    "capo": "capo_marketing",
    "priority": "high",
    "requiresApproval": true
  }'
```

The `requiresApproval: true` flag means the consigliere will queue the output for your review before sending anything. Start with approval on everything — remove it later for work you trust.

## Step 3 — Check the approval queue

```bash theme={null}
curl -sH "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  https://bossmode.ing/api/pro/approvals | jq
```

You'll see the drafted email sequence ready for review. Approve it:

```bash theme={null}
curl -sX POST https://bossmode.ing/api/pro/approvals/{approval_id}/approve \
  -H "x-bossmode-token: $BOSSMODE_API_TOKEN"
```

Or reject with feedback:

```bash theme={null}
curl -sX POST https://bossmode.ing/api/pro/approvals/{approval_id}/reject \
  -H "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "feedback": "Too formal. Match the voice in buyer profile 1." }'
```

## Step 4 — Read the Daily Report

After the consigliere executes, every move is logged. Your Daily Report surfaces the receipts:

```bash theme={null}
curl -sH "x-bossmode-token: $BOSSMODE_API_TOKEN" \
  https://bossmode.ing/api/pro/reports/daily | jq
```

## Using BossMode in Claude Code

If you have the BossMode Claude Code skill installed:

```
bossmode:get-context
```

This returns the same full context blob, formatted for Claude to consume directly.

Issue a directive via Claude Code:

```
bossmode:directive "Draft a follow-up sequence for cold leads" --capo capo_marketing --requiresApproval
```

## Using the MCP server

In any MCP-compatible runtime:

```
bossmode/get-context
bossmode/directive
bossmode/approvals/list
bossmode/approvals/approve
```

## What happens under the hood

1. The consigliere reads your standing orders to understand the rules
2. The directive is routed to the appropriate capo role
3. The capo executes within the engine scope (marketing, revenue, ops, etc.)
4. If `requiresApproval: true`, output is queued for your review
5. Every move is logged to the audit feed with a receipt
6. The Daily Report surfaces outcomes the next morning

## Next

<Card title="Write standing orders" icon="list-check" href="/standing-orders">
  Standing orders are the rules the consigliere follows when the boss is away. Without them, autonomous moves stop at review. With them, delegated work stays bounded by policy.
</Card>