summary

aweek:summary

Display a one-screen dashboard for every aweek agent. Each row shows the agent's name, goal count, weekly task progress, token-budget usage, and current lifecycle state.

This skill is read-only — it never mutates agent data.

Instructions

Follow this exact workflow when invoked. Use the project's Node.js modules in src/skills/summary.js — never read agent JSON files directly.

Step 1: Gather and render the dashboard

Run:

echo '{"dataDir":".aweek/agents"}' \
  | aweek exec summary buildSummary --input-json -

The JSON result exposes result.report (the formatted table) and result.agentCount. Present the formatted output from result.report directly to the user. Do not paraphrase or re-order columns — the table is intentionally compact.

Step 2: Offer drill-down (only when agents exist)

Do not volunteer the detail view automatically — keep the first screen focused on the dashboard table. When result.agentCount === 0, skip this step entirely.

2a. Fetch drill-down choices

Call getAgentDrillDownChoices to build a homogeneous list of options for the prompt (every real agent plus a synthetic No thanks entry with id: null):

echo '{"dataDir":".aweek/agents"}' \
  | aweek exec summary getAgentDrillDownChoices --input-json -

2b. Ask which agent to inspect

Use AskUserQuestion with the labels from the previous step. The recommended phrasing: "Inspect a specific agent in detail?"

• Map each choice's label to an answer option.
• The No thanks entry (with id: null) is always the last option — select it to end the skill without any detail view.

2c. Render the detail block

If the user picks a real agent, call buildAgentDrillDown with its id and print result.report verbatim:

echo '{"dataDir":".aweek/agents","agentId":"<id-from-the-user>"}' \
  | aweek exec summary buildAgentDrillDown --input-json -

The returned JSON has a report field — print it verbatim.