Akira

Akira is a production-ready AI Product Operator persona built for product teams at scaling companies who are drowning in feature requests but starving for clarity on what to build next — the ones with a backlog that grows faster than they ship, user feedback scattered across six tools, and a roadmap that's really just a list of things people asked for. She runs as a full-stack product operator: synthesizing user research, building outcome-driven roadmaps, planning launches, and maintaining a persistent product memory system that connects every decision back to what users actually need and what the business actually requires.

Akira doesn't just manage a backlog. She builds the decision-making system behind it — user signal in, prioritized roadmap out, with every feature traced to an outcome instead of an opinion.

🎯 All Skills Included The Akira persona includes every product operations skill — no separate purchases needed:

Product Strategy Engine — roadmap built from user outcomes and business goals, not feature requests and stakeholder loudness User Research Synthesis — feedback from support tickets, interviews, surveys, and analytics consolidated into actionable themes, not a spreadsheet of quotes Roadmap Management — quarterly roadmap with clear bets, scoped outcomes, and tradeoff rationale for every prioritization call Launch Planning — go-to-market coordination from internal readiness to external rollout with nothing falling through the cracks Product Memory — every product decision, user insight, and competitive signal documented so the team stops relitigating the same debates

Proven patterns:

Weekly user signal digest synthesizing feedback from all channels into prioritized themes Roadmap review every two weeks with progress, blockers, and reprioritization recommendations Launch checklist triggered 3 weeks before every release with cross-functional coordination Quarterly product strategy review connecting roadmap outcomes to business metrics

What makes Akira different from a generic prompt:

Outcome-driven — every feature on the roadmap is tied to a user outcome and a business metric, not "a customer asked for it" Signal over noise — synthesizes hundreds of feedback inputs into the 3-5 themes that actually matter, filtering out edge cases and one-off requests Tradeoff transparency — when something gets prioritized, Akira documents what didn't make the cut and why, so stakeholders understand the reasoning Launch discipline — treats every release as a coordinated event with internal readiness, external messaging, and post-launch measurement built in Product memory — remembers what was tried before, what worked, what didn't, and why decisions were made so the team doesn't repeat old mistakes Anti-feature-factory — actively pushes back when the roadmap is becoming a list of outputs instead of a plan for outcomes

Includes pre-configured cron schedules (weekly user signal digest, bi-weekly roadmap review, launch coordination triggers, quarterly strategy review), specialized skill documents (product strategy, user research synthesis, roadmap management, launch planning), and a complete README with installation guide. Designed for OpenClaw. Runs on Claude Opus, Sonnet, or any supported LLM model. The persona patterns are model-agnostic — the value is in the operational knowledge.