πΊοΈ Transparency, Ownership, Results-Driven
Strategic initiatives across Omni, Hive, Spark, Forge, Genie, and Tools
Track what we're building, why we're building it, and who's building it
Projects β’ How to Propose β’ Labels & Stages β’ Contributing β’ Documentation
This repository is the single source of truth for strategic initiatives across the entire Automagik ecosystem. Think of it as:
- π The Command Center: Where all projects align on priorities and timelines
- π― The Context Repository: Strategic analysis (5w2h) and detailed wishes for each project
- π€ The Community Hub: Where stakeholders provide feedback and track progress
- π The Progress Tracker: From Wishlist β Exploring β RFC (Proposal) β Prioritization β Executing β Preview β Shipped
Transparency builds trust. Ownership drives results. Structure enables scale.
Before:
- β Roadmap scattered across Slack, Notion, and individual heads
- β Community asks "when will X be ready?" without visibility
- β Cross-project dependencies create surprise blockers
- β No clear ownership = things fall through the cracks
After (with this repo):
- β Single place to see what's being built across all projects
- β Clear RASCI ownership (Responsible, Accountable, Support, Consulted, Informed)
- β Expected results tracked for every initiative
- β Community can comment, vote, and contribute ideas
- β Quarterly planning and review cadence
| Project | Description | Repository | Context |
|---|---|---|---|
| Omni | Omnichannel messaging with MCP | automagik-omni | 5w2h |
| Hive | Multi-agent orchestration | automagik-hive | 5w2h |
| Spark | Cron system that sparks repos | automagik-spark | 5w2h |
| Forge | AI-powered development orchestrator | automagik-forge | 5w2h |
| Genie | Autonomous agent framework | automagik-genie | 5w2h |
| Tools | MCP tools builder & marketplace | automagik-tools | 5w2h |
Each project folder contains:
- 5w2h.md - Strategic analysis (What, Why, Who, When, Where, How, How Much)
- wishes/ - Detailed initiative plans following the automagik-genie pattern
- README.md - Project overview with repository links
π View Project Board - Live project board with all initiatives
Quick Filters:
- π All Initiatives
- π§ Executing
- π Prioritization
- β Shipped
- β‘ This Quarter (Q4 2025)
- π₯ High Priority
Want to suggest something? We have different paths based on what you need:
Got an idea but not sure how to structure it? Use our simple wish form:
- Make a Wish using the π§ Make a Wish template
- Tell us:
- What's your wish?
- Why would it be useful? (optional)
- Any additional context? (optional)
- Submit β Gets
wish:triagelabel, team will review and guide it forward β¨
Perfect for:
- π‘ Feature ideas
- π― Improvement suggestions
- π€ "Wouldn't it be cool if..." thoughts
- π Quick submissions without formal structure
Have a well-defined initiative ready? Use the formal template:
- Create a new issue using the Initiative template
- Fill in the form fields (project, description, RASCI, expected results)
- Submit β Automatically added to project board β¨
Use our JSON script for fast, automated creation:
# Quick creation with JSON
cat << EOF | ./scripts/create-initiative-from-json.sh
{
"title": "Your Initiative Title",
"project": "omni",
"stage": "Exploring",
"priority": "high",
"quarter": "2026-q1",
"start_date": "2026-01-01",
"target_date": "2026-03-31",
"type": "feature",
"areas": ["api", "performance"],
"description": "One-line summary",
"goals": ["Goal 1", "Goal 2", "Goal 3"]
}
EOF
# Auto-selects owner (genie/forge β namastex888, others β vasconceloscezar)
# All fields set automatically (~40s creation time)
# See: ./scripts/create-initiative-from-json.sh --helpTemplates for detailed specs (optional):
- π LEAN - Streamlined format (recommended)
- π Template Guide - Decision tree, comparison, tips
Features:
- β PRD-style structure (5W2H, BDD stories, personas)
- β Automatic label application
- β Direct project board field setting
- β Retry logic for reliability
π¬ Community feedback is welcome! Share your thoughts on any initiative.
Our initiatives follow a structured lifecycle inspired by GitHub's public roadmap:
- π‘ Wishlist - Initial ideation and brainstorming
- π Exploring - Early investigation, validating the idea
- π¬ RFC - Request for Change, formal proposal and Go/No-Go decision
- π Prioritization - Prioritization and planning phase
- π¨ Executing - Active execution and implementation
- π§ͺ Preview - Beta/preview release for testing
- β Shipped - Generally available, live in production
- π¦ Archived - No longer active or deprioritized
We use a 6-dimensional label system to organize initiatives:
| Dimension | Examples | Purpose |
|---|---|---|
| Project | project:omni, project:hive |
Which project(s) are involved |
| Stage | Exploring, Executing |
Current development phase |
| Type | type:feature, type:research |
Kind of initiative |
| Priority | priority:critical, priority:high |
Urgency level |
| Quarter | quarter:2025-q4, quarter:2026-q1 |
Target timeframe |
| Area | area:api, area:mcp, area:agents |
Technical domain |
Total: ~40 labels across 6 dimensions for precise organization.
For community-submitted feature ideas:
| Label | Meaning | Usage |
|---|---|---|
wish:triage |
User wish pending team review | Auto-applied by Make a Wish template |
wish:active |
Wish approved and being worked on | Set by team during triage |
wish:archived |
Wish completed and archived | Auto-applied when PR merges |
- Stage Definitions - Detailed criteria for each stage
- Label Guide - Complete label taxonomy and usage
- RASCI Guide - Ownership model for open source projects
- Wish Template - How to structure detailed initiatives
- Cross-Repo References - Linking initiatives across repos
Weekly CSV exports are available in exports/ for stakeholder reporting and analysis.
Export format includes:
- Project, Initiative, Description
- Stage, Quarter, Priority
- Expected Results
- Owner, Created/Updated dates
- Links to issues and wish folders
Exports run automatically every Monday via GitHub Actions.
We welcome community input on our roadmap!
How to contribute:
- π§ Make a wish for feature ideas (no technical knowledge needed!)
- π¬ Comment on issues to share feedback and ideas
- π― Propose initiatives via structured templates
- π§ Submit PRs to project repos (link to issues for auto-labeling)
- π‘ Join discussions on our Discord
For Developers:
- All project repos have PR templates with issue linking
- Link PRs to issues using
- Closes #Xfor automatic metadata inheritance - Wish documents in
.genie/wishes/are auto-archived when PRs merge
See CONTRIBUTING.md for detailed guidelines.
This roadmap represents our current plans and priorities. Items may change based on:
- Community feedback and feature requests
- Technical constraints and dependencies
- Strategic shifts and market changes
- Resource availability and capacity
No dates or commitments are guaranteed. This is a living document that evolves with the ecosystem.
- Discord: Join the community
- GitHub Org: @namastexlabs
- Documentation: docs.automagik.ai
MIT License - See LICENSE
Built with transparency by Namastex Labs
Questions? Check our FAQ or reach out on Discord
