report

aweek:report

Send a CEO report on behalf of an agent. Every report:

1. Persists a notification under the sender agent's .aweek/agents/<slug>/notifications.json, which surfaces immediately on the dashboard's inbox.
2. If the project's .aweek/channels/slack/config.json (or env) provides BOTH a botToken AND a ceoChannel, posts a formatted Slack message to that channel/DM via chat.postMessage.

The skill is the canonical surface agents call autonomously during a heartbeat session (aweek exec report send …) AND the user-facing slash command for manually composing or testing a report. Use aweek:notify directly only when you need the generic notification surface without the report/question framing.

When the agent uses this autonomously

During a heartbeat session an agent decides "I should tell the CEO about this" or "I'm blocked and need a decision" — it shells out to:

echo '{
  "senderSlug": "<AGENT_SLUG>",
  "kind": "report",
  "title": "<SHORT_TITLE>",
  "body": "<DETAILED_BODY>",
  "severity": "info"
}' | aweek exec report send --input-json -

Replace kind with "question" when the agent needs a decision (rather than a status update). Replace severity with "warning" (action recommended) or "error" (blocked / urgent).

You do not invoke this on the agent's behalf — agents call it themselves through Bash during their heartbeat tick. The slash command below is for the USER to manually compose a report (testing, manual escalation, or surfacing context the agent can't articulate yet).

Slash-command workflow (user-facing)

You MUST follow this exact workflow when invoked. Use aweek exec report send — never write notification JSON files directly.

Step 1: Pick the sender agent

List available agents so the user can choose which one the report should be attributed to:

echo '{"dataDir":".aweek/agents"}' \
  | aweek exec agent-helpers listAllAgents --input-json -

Project each entry to { id, name, role } for display. Treat zero entries as the "create an agent first" case — direct the user to aweek hire and stop.