Start every new feature with the right context already loaded
Pull strategy docs, ICP profiles, planning docs, and related research into your AI conversation before you start designing
Overview
Every new feature starts the same way: you open your AI assistant, then spend 20 minutes hunting for context. Where is the strategy doc? What did the ICP research say? Are there related Jira tickets? You copy-paste it all in just to have a useful conversation. By the time you are ready to brainstorm, you have already lost momentum.
How it works
MCP gathers everything you need to start a feature design: the company strategy doc, ICP profiles, relevant Slack threads about team initiatives. Then it asks what feature you are working on. Based on your answer, it pulls related Coda planning docs, Jira tickets, and user research from Dovetail. Once everything is loaded, you are ready to brainstorm user journeys, explore the problem space, and collaborate with your AI using full context.
Who this is for
Product managers, designers, and strategists who start new features by pulling context from multiple tools. Anyone who is tired of re-explaining their project to AI every time they start a new conversation.
Suggested prompt
Help me start a new feature problem space. Begin by pulling: (1) our 2026 company strategy doc from Google Docs, (2) the ICP profiles, and (3) any Slack threads about current team initiatives. Then ask me what feature I am working on. Based on my answer, find related Coda planning docs, Jira tickets, and user research studies. Once you have gathered everything, summarize what you found and let me know we are ready to start brainstorming. As we work, if I create PRDs or feature specs, be ready to help me turn them into Jira tickets at the end. Show me each ticket before creating it.
Frequently asked questions
What kind of context does it load before I start?
It pulls your company strategy doc, ICP profiles, and relevant Slack threads about team initiatives. Then based on what feature you are working on, it finds related Coda planning docs, Jira tickets, and user research from Dovetail.
Can it turn my PRDs into Jira tickets?
Yes. Once you have finished brainstorming and created a feature spec, the AI can help you break it into Jira tickets. It shows you each ticket before creating it so you can review the scope and acceptance criteria.
How many tools does this connect to?
This template connects to five tools: Google Docs for strategy docs, Coda for planning docs, Jira for tickets, Slack for team discussions, and Dovetail for user research. All the context flows into one AI conversation.
Do I need all five integrations to use this?
You can start with whichever tools you use most. The template works best with all five, but even connecting two or three gives you significantly more context than starting from scratch each time.