Context flow is a project-level feature. Tasks in different projects do not share context with each other. If you want two tasks to benefit from shared context, put them in the same project.
How context flows
Within a project, Rocket maintains a shared understanding of all the work that has been done. When you create a new task, Rocket can draw on the findings, decisions, and outputs from earlier tasks in the same project. Context flows in every direction between tasks. There’s no fixed order - a Build task’s output is just as useful for informing a later Solve task as the reverse.| Direction | What happens |
|---|---|
| Solve → Build | Research findings inform what gets built (features, positioning, design) |
| Build → Solve | Development reveals new questions that trigger deeper research |
| Solve → Solve | Later research builds on earlier findings without duplicating work |
| Build → Build | Branding, messaging, and technical decisions carry forward to new tasks |
What counts as context
Rocket draws on several types of context from within the project:| Context type | Example |
|---|---|
| Solve findings | Market size data, competitive insights, pricing benchmarks from completed research |
| Build outputs | App descriptions, feature lists, technical decisions from Build tasks |
| Chat history | Clarifications, follow-up questions, and refinements from any task’s conversation |
| Shared files | Uploaded documents, images, spreadsheets, and data referenced by tasks |
| Connected services | Live data from Notion pages, Google Docs, and Google Sheets linked to the project |
Examples of cross-task context flow
Solve → Build: Research informs development
Solve → Build: Research informs development
You create a Solve task to analyze the competitive landscape for project management tools. The report identifies key features users expect: Kanban boards, time tracking, and team chat.You then create a Build task in the same project for an MVP. Rocket automatically references the competitive findings, prioritizing the features your research identified as essential.
Build → Solve: Development prompts new questions
Build → Solve: Development prompts new questions
You’re building an e-commerce app and realize you need a pricing strategy. You create a Solve task in the same project. Rocket already knows the product category, target audience, and feature set from the Build task, so the pricing analysis is immediately relevant to your specific product - not generic advice.
Solve → Solve: Research builds on research
Solve → Solve: Research builds on research
Your first Solve task explores market sizing for a fintech product. The report identifies three promising segments.You create a second Solve task diving deeper into one segment. Rocket uses the first report as a foundation, avoiding duplicate research and building on the existing analysis.
Build → Build: Iterative development
Build → Build: Iterative development
You build an MVP web app as your first Build task. Later, you create a second Build task for a companion landing page. Rocket carries forward the branding, messaging, and product details from the app - ensuring the landing page is consistent with what you’ve already built.
Standalone tasks vs project tasks
Every task can work independently. You don’t need a project to create a Solve or Build task - standalone tasks are fully functional. The difference is context.| Standalone task | Task in a project | |
|---|---|---|
| Works on its own | Yes | Yes |
| Accesses shared files | No | Yes |
| Benefits from other tasks’ context | No | Yes |
| Uses connected services | No | Yes |
| Can be collaborated on | Via task sharing | Via project membership |
If you start with a standalone task and later realize you want shared context, you can add it to a project at any time without losing any history.
Intelligence and context
Intelligence and the Intelligence dashboard live outside of projects - they’re managed at the platform level. However, insights from Intelligence can still inform your project work. For example, if Intelligence detects that a competitor just launched a new pricing page, you might:- Create a Solve task in your project to analyze the competitor’s new pricing model
- Use those findings in a Build task to update your own pricing page
Think of Intelligence as your external radar and projects as your internal workbench. Intelligence tells you what’s happening out there; projects are where you decide what to do about it.
Tips for effective context flow
Front-load research
Front-load research
Start your project with a Solve task before jumping into Build. The research findings become foundational context that improves every subsequent task.
Be specific in task prompts
Be specific in task prompts
Even though Rocket has project context, specific prompts get better results. Reference earlier work explicitly: “Based on the competitive analysis from earlier, build a landing page that emphasizes our differentiators.”
Upload relevant files early
Upload relevant files early
Shared files are available to all tasks. Upload brand guidelines, product specs, or reference material when you create the project - not when you need them mid-task.
Keep related work in one project
Keep related work in one project
What’s next?
Share files
Upload documents that all tasks in your project can reference.
Connect services
Bring external data from Notion, Google Docs, and more into your project.
Solve overview
Learn how to create research tasks that feed project context.
Build overview
Learn how to create apps and websites that benefit from shared context.