This document outlines planned development for MIRA. If you're interested in contributing, look for issues tagged with help wanted or good first issue.
Want to Pitch In? Here are tasks that could be done and PR'd:
Import/Export API endpoint that collects messages and memories and puts them in a file that can be imported. Put them on the /actions endpoint.
Identify dead code and include a reference to a grep that it is truly orphaned in the PR
OpenWebUI integration. the hosted version has the bespoke UI but some basic web UI would help lower the barrier to entry for new users
ADVANCED: writing tests. lord, if you can work through the directories writing pytests with strong precise assertations I will be forever grateful.
Q1 2025
January: Codebase Cleanup
Focus on reducing technical debt and improving code quality.
Remove dead code and unused imports
Standardize error handling patterns
Consolidate duplicate logic across modules
Improve type annotations coverage
Update and clean up documentation
Refactor inconsistent naming conventions
Contribution opportunities: Code cleanup tasks are excellent entry points for new contributors.
February: LT_Memory Refinement
Enhance the long-term memory system and self-reflection capabilities.
Refine LT_Memory extraction and linking logic
Adjust end-of-segment self-reflection step
Implement blind scratchpad for MIRA observations
MIRA generates unstructured observations before structured extraction
Captures intuitions that might be lost in direct-to-structure processing
Improve memory refinement pipeline
March: TUI Enhancement
Build out a more complete terminal user interface.
Expand TUI feature set
Improve navigation and usability
Add configuration options accessible via TUI
Enhanced conversation display and controls
How to Contribute
Check the Issues page for tasks tagged help wanted
Read CONTRIBUTING.md for development setup
For larger changes, open an issue first to discuss the approach
Questions? Open a Discussion or reach out in Issues.
1---2name: 317-roadmap-0261eb1e3description: MIRA Roadmap4---5# MIRA Roadmap67This document outlines planned development for MIRA. If you're interested in contributing, look for issues tagged with `help wanted` or `good first issue`.89## Want to Pitch In? Here are tasks that could be done and PR'd:10- Import/Export API endpoint that collects messages and memories and puts them in a file that can be imported. Put them on the /actions endpoint. 11- Identify dead code and include a reference to a grep that it is truly orphaned in the PR12- OpenWebUI integration. the hosted version has the bespoke UI but some basic web UI would help lower the barrier to entry for new users13- ADVANCED: writing tests. lord, if you can work through the directories writing pytests with strong precise assertations I will be forever grateful. 141516## Q1 20251718### January: Codebase Cleanup1920Focus on reducing technical debt and improving code quality.2122- [ ] Remove dead code and unused imports23- [ ] Standardize error handling patterns24- [ ] Consolidate duplicate logic across modules25- [ ] Improve type annotations coverage26- [ ] Update and clean up documentation27- [ ] Refactor inconsistent naming conventions2829**Contribution opportunities**: Code cleanup tasks are excellent entry points for new contributors.3031---3233### February: LT_Memory Refinement3435Enhance the long-term memory system and self-reflection capabilities.3637- [ ] Refine LT_Memory extraction and linking logic38- [ ] Adjust end-of-segment self-reflection step39- [ ] Implement blind scratchpad for MIRA observations40 - MIRA generates unstructured observations before structured extraction41 - Captures intuitions that might be lost in direct-to-structure processing42- [ ] Improve memory refinement pipeline4344---4546### March: TUI Enhancement4748Build out a more complete terminal user interface.4950- [ ] Expand TUI feature set51- [ ] Improve navigation and usability52- [ ] Add configuration options accessible via TUI53- [ ] Enhanced conversation display and controls5455---5657## How to Contribute58591. Check the [Issues](../../issues) page for tasks tagged `help wanted`602. Read [CONTRIBUTING.md](CONTRIBUTING.md) for development setup613. For larger changes, open an issue first to discuss the approach6263Questions? Open a Discussion or reach out in Issues.
Run npx skillmds@latest add tools-only/317-roadmap-0261eb1e in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
MIRA Roadmap It is listed under Product & Planning on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tools-only