Draft Tomorrow's Sprint Planning Brief

For a squad that shows up to planning with a full backlog and no consensus on priorities. One prompt pulls the backlog, reads last week's funnel, and drops a one-page brief in Notion with recommendations and the data behind each call.

Linear logoLinear
PostHog logoPostHog
Notion logoNotion
THE GRIND

Planning debates priorities, not trade-offs

The backlog is full of P1s. The funnel has a hole. Nobody walks in with the connection between the two, so planning spends 45 minutes re-litigating what should've been prep.

Planning starts cold — nobody pre-read the backlog

Funnel data lives in PostHog, priorities live in Linear, never meet

The same 'should we do ONB-133 or BILL-221' debate, every other week

Composio collapses all of this into one prompt — here's what that looks like.

THE FLOW
5 steps · 3 toolkits

Your agent runs it end-to-end.

  1. 01
    Pull issues sized for the next sprint — triaged, scoped, not started
    linear logo
  2. 02
    Query last week's funnel and week-over-week deltas
    posthog logo
  3. 03
    Map each issue to the funnel step it most directly affects
  4. 04
    Recommend P0 / P1 / slip based on funnel impact, with the delta as justification
  5. 05
    Write the brief to Notion — recommendations, data, and open questions
    notion logo
THE PAYOFF

Planning meets to decide, not discover

Tomorrow's planning opens with the brief already on screen. The team argues trade-offs instead of priorities — and the meeting ends in 30 minutes, not 90.

Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.