chieflab_suggest_next_move

Active

declared in 0.3.0

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.

Parameters schema

{
  "type": "object",
  "required": [
    "channel",
    "metrics"
  ],
  "properties": {
    "runId": {
      "type": "string",
      "description": "Optional. Source run whose brief grounds the suggestion (so the draft references the actual product / market / audience instead of templates)."
    },
    "channel": {
      "type": "string",
      "description": "Channel the measurement is for (linkedin, x, email, landing_hero, product_hunt, hacker_news)."
    },
    "metrics": {
      "type": "object",
      "description": "Measurement metrics — engagements, clicks, opens, replies, traffic, conversions, upvotes, rank, etc. Synonyms (engagement / openRate / clickRate / visits) are accepted."
    },
    "workspaceId": {
      "type": "string",
      "description": "Optional workspace id."
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.70.

Parent server

ChiefLab

https://github.com/bdentech/chiefmo-agent

1/7 registries

View full server →