Planning / Mnemosyne
Mnemosyne
Your implementation plans, part of your software's memory.
Keep repository guidance, architecture references and implementation plans in Git. Mnemosyne recognizes the important documents using defined, configurable conventions. Inspect the result in Code Explorer, and adapt those conventions to your repository yourself or with your agent.
01
See how your documents were recognized
Code Explorer makes the recognized repository guidance and planning structure visible. Browse the important documents, inspect their assigned roles and recorded status, and open a document's outline and incoming links alongside the code.
This is the human view of the indexed result: you can check which documents Mnemon found and how it classified them, rather than relying only on an agent's summary. The source remains available when you need to verify the context.
02
Your repository, your document conventions
Start with shared settings for where Mnemon looks for epics, archived work and important guidance documents. Use repository-specific overrides when a project's layout differs, without changing the shared defaults for other repositories.
Set the conventions yourself, or ask your agent to inspect and configure the repository's conventions through MCP. Identify the documents and locations that matter to your project within Mnemon's supported settings; you do not have to reorganize the repository to match a single folder layout.
Configuration defines how documents are discovered and classified; Code Explorer shows the indexed result. Saving settings does not itself refresh that index. Run the required re-index or rebuild before checking the updated classification.
03
Prepare the implementation with your agent
Use the repository's writing conventions and optional recipes to organize a new brief and implementation plan with your agent. You decide the work; the agent helps write the documents; Mnemosyne makes their structure discoverable.
04
Find documents by their role in the work
- Role: roadmap, execution plan, architecture reference or runbook.
- Kind: epic, brief or reference material.
- Lifecycle: recognized Draft, Planned, Active or Done state, with the source status available to inspect.
- Connections: recognized planning links, including missing targets and anchors.
Recognition uses paths, content and configurable conventions, without an LLM. Common layouts need no special front matter, and Mnemon can explain the rules behind a classification.
05
Follow the plan through its changes
Revisit document structure and planning metadata across commits. Find recorded active work and next steps, then inspect the source when you need the detail.
Status reflects your documents and conventions, not automatic delivery verification. Closed or archived work is not necessarily shipped work; you and your team still maintain the plan.
06
Find related context without remembering the title
Enable embeddings to retrieve related indexed documents by meaning. A local ONNX option is available. This optional search layer complements Mnemosyne's document classification; it does not determine planning status.
07
Preview a draft before committing
With Watch Focused enabled, preview the tags, kind and lifecycle of supported uncommitted Markdown. These temporary results are marked as work in progress and remain separate from committed memory.
08
The plan stays in your repository
Write with your existing tools, review in Git and adapt conventions to your layout. Once committed and indexed, the documents are available to both the application and your connected agent.