Prompt Guidance
How to Manage Project Context with Ottermind: Organize and Reuse Background
A project may begin with a proposal, continue into slides, and later require updates. Keeping goals, audiences, sources, and preferences together in Ottermind gives follow-up tasks a clearer starting point. This tutorial explains how to prepare a project brief, maintain versions, and check that outputs follow the latest requirements.
Record stable context and changing data
Start with goals, audience, sources, output preferences, and update rules. Keep stable background separate from frequently changing data so both are easier to maintain.
1. Create a short project brief
Record information that changes the output, rather than collecting every historical message:
Goal: help new users understand the product's core purpose. Audience: independent creators and small teams. Style: concrete and readable, without unsupported promises. Sources: use the approved product material in this project. Updates: identify conflicts between new and old material and ask which version to use.Save this through the available project or file entry point. Explicitly refer to it in later tasks so you can check the selected context.
2. Organize files and versions
Group product descriptions, meeting notes, references, and approved outputs by purpose. Name files with topics and versions, and identify which are current. Saved files do not guarantee that every later task will use them; specify important inputs directly.
3. Continue from existing context
Using the latest product description and approved plan in this project, prepare a presentation outline for prospective customers. Follow the project style and exclude outdated positioning. First list the sources you will use and any information still needed.This connects the new task to earlier work while exposing gaps.
4. State changes explicitly
When audience, positioning, or dates change, identify the update and whether older instructions are obsolete. For example: the audience is now small design teams; the previous student positioning no longer applies.
Ask for an updated project summary covering the goal, decisions, open questions, and next tasks, then review it yourself.
5. Check the output's context
Verify audience, facts, and style in the actual result. If old information reappears, point to its source and correct it. A confirmation in chat alone does not prove every later output is updated. Retention and memory behavior depend on the current product settings; clear sources and inspectable results remain essential.
Product reference: Organize your project context
