Molten.bot Public Backlog

🔥 We build in public. This is our live development board for Molten.bot — the execution control plane for autonomous AI agents.

See what we're working on, what's coming next, and how we prioritize. Have a feature request? Open an issue.

---

🎯 What Is This?

This repository is the single source of truth for Molten.bot's product development. Every feature, bug fix, and improvement starts here as a GitHub issue.

You can:

• 👀 See our current priorities (STACK_RANK.md)
• 🐛 Report bugs
• 💡 Request features
• 📊 Track progress on open issues
• 💬 Comment and vote on existing issues

We prioritize by:

1. Revenue Impact — Drives conversions, retention, expansion
2. Strategic Value — Advances our product vision
3. User Impact — How many users this affects
4. Blocking Factor — Unblocks other important work
5. Time Sensitivity — Deadlines or opportunities
6. Effort vs Impact — Quick wins jump the queue

See STACK_RANK.md for detailed prioritization methodology.

---

🚀 Current Priorities

Check STACK_RANK.md to see what we're working on right now.

Issues are ranked by importance:

• 🔴 Critical — Shipping now
• 🟡 High Priority — Next up
• 🟢 Medium Priority — In queue
• ⚪ Low Priority — Future consideration

Transparency: Priorities shift based on user feedback, technical constraints, and business goals. What's #1 today might not be #1 tomorrow.

---

💡 Submit a Feature Request

Have an idea? Open a GitHub issue!

Use the template (auto-populated when you create an issue):

1. Context — What problem does this solve?
2. Acceptance Criteria — What does "done" look like?
3. Resources — Links, examples, references
4. Why This Matters — Impact on your workflow

We'll:

• Review and respond within 48 hours
• Stack rank against existing priorities
• Update you on status changes

No promises — We can't build everything, but we read and consider every request.

---

🐛 Report a Bug

Found something broken? Open an issue with:

• What happened — Observed behavior
• What you expected — Expected behavior
• Steps to reproduce — How to trigger the bug
• Environment — Browser, OS, account tier
• Impact — How urgent is this?

Production bugs get prioritized immediately.

---

📋 Issue Labels

We use labels to organize and prioritize:

Priority:

• priority:high — Critical or high-impact work
• priority:medium — Normal queue
• priority:low — Nice-to-have

Type:

• type:feature — New functionality
• type:bug — Something broken
• type:enhancement — Improvement to existing feature
• type:docs — Documentation update

Status:

• status:blocked — Waiting on external input
• status:in-progress — Actively being worked on
• status:needs-feedback — Need more info from community

Source:

• community-requested — Requested by users
• internal — Molten.bot team-initiated

---

📁 Repository Structure

/Molten-Bot/backlog/
├── drafts/           # Agent-drafted issues awaiting GitHub creation
├── in-progress/      # Active work (development, testing, pre-prod)
├── done/             # Completed and shipped issues
├── STACK_RANK.md     # Live priority ranking (single source of truth)
└── README.md         # This file

Workflow:

1. Draft — Agent creates issue draft in drafts/
2. GitHub — Boss Man reviews and creates GitHub issue
3. In Progress — File moves to in-progress/ when work starts
4. Done — File moves to done/ when complete, removed from STACK_RANK.md
5. Close — GitHub issue closed with commit reference

Transparency: File location shows real status, not aspirational status.

---

✅ How We Work

Our workflow is transparent:

1. Issue Created → Added to backlog
2. Stack Ranked → Prioritized against other work (STACK_RANK.md)
3. In Progress → Agent or team member picks it up
4. Shipped → Commit with Closes #N auto-closes issue
5. Announced → Shared in changelog/updates

Ship velocity: Check closed issues to see how fast we move.

---

🤝 Community Guidelines

Be constructive:

• Clearly explain the problem or opportunity
• Provide examples or use cases
• Respect that we can't build everything

Be patient:

• We're a small team shipping fast
• Priorities shift based on user feedback and data
• We read everything, even if we can't respond immediately

Be specific:

• "Add dark mode" is vague
• "Add dark mode toggle in header, persist preference to localStorage" is actionable

---

🤖 Automation

We use AI agents to work through this backlog. Issues are picked from STACK_RANK.md (top = highest priority), executed, and closed automatically via commit messages.

How it works:

• GitHub Issues → Task tracking
• Stack ranking → Prioritization
• OpenClaw agents → Execution
• Closes #N in commits → Auto-close issues

Why this matters: We're building Molten.bot (AI agents that execute tasks). This backlog is both our development board AND a live example of agents doing real work.

---

📊 Stack Ranking

See STACK_RANK.md for:

• Current priorities (what's #1 right now)
• Ranking criteria (how we decide)
• Decision framework (why things are ranked where they are)
• Workflow (how issues move through the system)

Transparency = Trust. We show our work.

---

🔗 Links

• Website: molten.bot
• Documentation: docs.molten.bot (coming soon)
• Blog: molten.bot/blog
• Skills Repo: Molten-Bot/skills (private)
• Discord: (coming soon)

---

📬 Questions?

• Feature requests: Open an issue
• Bug reports: Open an issue
• General questions: Open a discussion (or issue for now)
• Security issues: Email security@molten.bot

---

Built with 🔥 by the Molten.bot team

We're building the execution control plane for autonomous AI agents. This backlog is part of our commitment to building in public.

Star this repo to follow along.