distribution-plan

Preamble (run first)

Before any other tool, run the preflight MCP tool (or metalworks preflight on the CLI). If it reports setup issues or that an update is available, surface that to the user in one line and help them resolve it (install the missing extra/key, or pip install -U metalworks) before continuing. Skip only if the user has already passed preflight this session.

Read the reference; never reverse-engineer the source. The moment you need to know how metalworks behaves — provider/model resolution, which source/reader runs, config precedence, an error you hit, or the async run loop — STOP and read docs/operating-metalworks.md (bundled with this plugin) before opening any file under src/. It is the source of truth; do not derive behavior from source. (Full docs: https://metalworks.lab2a.ai/docs.) For a long-running run, poll status with the Monitor tool or a bounded loop — never a blind sleep.

You are sequencing one demand report's distribution channels into a CAMPAIGN. Distribution is not a flat list of channels with arbitrary T+2h spacing — it is pushes (concentrated spike moments) and streams (compounding channels run continuously), and the timing of every push comes from a deterministic playbook table sourced from the research, never from an invented hour. You are NOT making up a schedule.

Steps

1. Get the report_id. If the user hasn't run a report yet, point them at /demand-report first — the plan sequences the report's channel strategy (D2), which needs a finished report to ground on.

2. Call the distribution_plan MCP tool with the report_id (or, on the CLI, run metalworks distribution plan <report_id>). It routes the report into its channel strategy, then returns a DistributionPlan with two lists: pushes (the spike channels sequenced into moments) and streams (the compounding channels run continuously).

3. Read the plan honestly, in two parts:

   • Pushes — for each Push: the timing (READ from the playbook table — e.g. "Day 1, 12:01am PT (Tue/Wed)" for Product Hunt), the channel_name, the action (the concrete human step), the spark_channel it ignites (if any), and the rationale. The campaign opens with a pre-launch warming push and closes with a 30-day post step — present them as the frame around the launch week, not as channels.
   • Streams — for each Stream: the channel_name, the cadence_note (how it runs continuously), and the rationale. Streams have no timing — they run all the time, not as a moment.