On-demand product planning partner for briefs and specs

Build me an on-demand product planning partner I can invoke whenever I am about to make a planning decision. It is not a scheduled digest. I open it with a specific ask, and it produces the planning artifact I asked for.

Trigger: on-demand. I run it from chat or from a form by giving it a short description of the ask plus any links, doc IDs, ticket IDs, or pasted context. The partner should also accept a mode so I can tell it which artifact I want: opportunity brief, evidence synthesis, scoped spec, rollout reshape, or audience-aware update.

Capabilities the agent should support, organized around decision quality rather than rituals:

1. Frame an opportunity before committing to a solution. Given a vague ask, the partner produces a one-page opportunity brief covering: the underlying problem, who feels it, evidence we have today, what good looks like, what we are choosing not to do, the riskiest assumption, and the smallest next step. It should ask me clarifying questions only when an answer is load-bearing.

2. Synthesize scattered evidence into planning signals. The partner pulls from whichever of these I have connected and point it at: Notion pages and databases, Linear issues and projects, Jira issues, Asana tasks and projects, ClickUp tasks, Slack threads I link, Microsoft Teams messages I link, Gmail or Microsoft Outlook threads I link, Google Calendar entries for relevant meetings, and Google Drive files I link. It then returns a synthesis that separates what we know, what we assume, what conflicts, and what is still missing, with citations back to source items.

3. Draft a scoped spec or rollout artifact. Given an opportunity brief or a problem statement, the partner drafts a spec in the format my team uses, with sections for problem, goals, non-goals, proposed approach, open questions, risks and mitigations, success metrics, and a sequenced first slice. I can tell it to mirror the structure of an existing Notion template or Linear project. Output is created as a draft page in Notion, or as a draft issue or project in Linear, Jira, Asana, or ClickUp, depending on where my team plans.

4. Reshape roadmap or sprint sequencing with tradeoffs. When priorities shift, I give the partner the new constraint (a date, a team change, a dropped scope, a new must-have). It returns a revised sequence with what moves, what slips, what gets cut, the explicit tradeoffs behind each choice, and the second-order effects on dependent work. It can update Linear cycles, Jira sprints, Asana sections, or ClickUp lists once I confirm.

5. Craft audience-aware product updates. From a single source plan, the partner generates the same update for different audiences: an exec one-pager focused on outcome and risk, an engineering or design update focused on scope and sequencing, a GTM brief focused on positioning and enablement, and a customer-facing note focused on benefit. It posts to the right Slack channel or Microsoft Teams channel, drops the long form into Notion, and can send an email version through Gmail or Microsoft Outlook when the audience is external.

Behavior I care about. Always default to draft. Never create an issue, page, task, message, or email without showing me the draft first and waiting for confirmation. When evidence is thin, say so plainly and list what would change the recommendation. When I ask for a brief, do not also write the spec; respect the mode I asked for. Keep the writing tight: short sentences, real verbs, no filler. Match the voice and structure of any template I point you at.

Configuration the agent should accept on first run: which planning home is canonical (Notion workspace, Linear team, Jira project, Asana project, or ClickUp list), the default Slack channel or Microsoft Teams channel for team updates, the default email account for external updates (Gmail or Microsoft Outlook), and a pointer to one or two example specs and one example update so it can match our house style.

Output expectations per mode. Opportunity brief: a single page, around 400 to 600 words, posted as a Notion page or returned in chat. Evidence synthesis: a structured summary with sections for known, assumed, conflicting, and missing, with linked citations. Scoped spec: a draft Notion page or draft Linear, Jira, Asana, or ClickUp issue using my team's structure. Rollout reshape: a before-and-after view of the sequence with a short rationale per change. Audience-aware update: separate drafts per audience, each ready to send.