Browse / Professional & finance / Productivity & assistant / revaya-aios-workspace-template
revaya-aios-workspace-template
revaya-ai
A structured AI Operating System workspace template for Claude Code.
Open revaya-ai/revaya-aios-workspace-template → Manually confirmed as a workspace.
agentic-aiai-osbusiness-aiclaudeclaude-codeproductivityworkspace-template
Built for Claude Code
ships .claude CLAUDE.md and nothing for other agents.
In its own words
9-component AIOS architecture with slash commands, strategic layer, team agents, GTD system, and content engine. Use this template to build your own Business AI OS.
This is the actual system I use to run my consultancy. Every session, every command, every agent — live and in production. Fork it and build yours.
The Problem
Most founders are trapped doing work their business should be doing for them. Not because they lack discipline. Because AI tools don't connect to how their business actually operates.
You can use ChatGPT for emails and Claude for summaries, but those are one-off interactions. There's no memory. No persistent context. No team. Every session starts from zero. The AI doesn't know your business, your strategy, your pipeline, or your priorities.
A Business AI OS fixes that. It's a structured workspace that gives AI everything it needs to function as a genuine operational partner — not just a smart search box.
What Is a Business AI OS?
A Business AI OS is a Claude Code workspace configured specifically for your business. It contains:
- Persistent context — your business, role, strategy, and current data, always loaded
- A decision filter — One Objective, One Bottleneck, One Goal (OOBG) that scores every task
- A team of specialized agents — 14 agents organized across 6 departments (Attract, Convert, Retain & Deliver, Ascend, Finance, AI HR)
- A command system — 31 slash commands for every recurring workflow (planning, content, GTD, metrics, knowledge capture)
- A learning system — knowledge management and learning loops that make the OS smarter over time
The repository's own description, then 43% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.