chieflab_prepare_next_move
ActiveTool of ChiefLab
[chieflab_* alias of chiefmo_prepare_next_move] USE WHEN the user has just published a launch (or ≥24h post-launch) and asks 'what's next?', 'follow-up post?', 'iterate on this', 'plan day 2'. P13 — turns one launch into a 7-day launch mode: drafts a queue of follow-up actions (day 2 reply post, day 3 case study, day 5 metrics share, day 7 retrospective) grounded in the prior launch's runId, the per-tenant brand voice + repo facts + channel performance from the P9 company brain, and the prior recommendation (so the next move doesn't repeat the last one). Returns a draft queue + signed reviewUrl + the standard agentGuide block. Each next-move action lands in awaiting_approval; nothing fires without explicit human approval.
Parameters schema
{
"type": "object",
"required": [
"runId"
],
"properties": {
"runId": {
"type": "string",
"description": "The prior launchId returned by chiefmo_launch_product. The prepared queue grounds in this run's measurement + memory."
},
"horizon": {
"type": "string",
"description": "\"day_2\" | \"day_3\" | \"week\" — how far to plan. Default: \"week\" (7-day mode)."
},
"channels": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional. Restrict next-moves to these channels. Defaults to the channels of the prior launch."
},
"workspaceId": {
"type": "string",
"description": "Optional workspace id."
}
}
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
ChiefLab
https://github.com/bdentech/chiefmo-agent
1/7 registries