chieflab_suggest_next_move
P75 — Next Move Engine. USE WHEN measurement just came in (chiefmo_post_launch_review fired automatically at 24h, OR the user manually called it) and you want to know what the operator should do next. Reads metrics + the original launch's brief and emits a deterministic suggestion: {kind: 'follow_up_email' | 'founder_dm' | 'thread_reframe' | 'landing_iteration' | 'lessons_learned_post' | 'seo_title_test' | 'wait' | 'noop', priority, reasoning, draftBrief: {channel, headline, body, cta?, recipients?}, measurementGroundingFacts}. Pure-function; same input → same output, no LLM. Pair with chieflab_create_next_move_action to turn the suggestion into an approval-gated draft.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"channel": "<channel>",
"metrics": "<metrics>"
},
"name": "chieflab_suggest_next_move"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| runId | No | Optional. Source run whose brief grounds the suggestion (so the draft references the actual product / market / audience instead of templates). | |
| channel | Yes | Channel the measurement is for (linkedin, x, email, landing_hero, product_hunt, hacker_news). | |
| metrics | Yes | Measurement metrics — engagements, clicks, opens, replies, traffic, conversions, upvotes, rank, etc. Synonyms (engagement / openRate / clickRate / visits) are accepted. | |
| workspaceId | No | Optional workspace id. |