Identity (WHO)
Defined by role.json + ROLE.md. Sets personality, constraints, and communication style. An architect thinks differently than an engineer.
OSTwin turns a markdown plan into a fully-orchestrated multi-agent execution. No custom agent code required.
PLAN.md ──► Engine ──► DAG ──► War-Rooms ──► Agents │ │ │ │ │ "Build a game" │ Waves │ Channels │ Skills │ │ of │ Memory │ MCP Tools ▼ ▼ epics ▼ Lifecycle ▼ Goal + Epics Dependency Isolated Role-based + Constraints resolution execution specialistsEvery agent in OSTwin is defined by three orthogonal axes. This is what makes agents composable rather than monolithic.
Identity (WHO)
Defined by role.json + ROLE.md. Sets personality, constraints, and communication style. An architect thinks differently than an engineer.
Expertise (WHAT)
Loaded from SKILL.md files on demand. Domain knowledge injected into context only when needed. Skills are portable across roles.
Execution (HOW)
MCP servers provide isolated tool access. Each war-room gets its own tool boundary. No agent can reach outside its sandbox.
Write a plan, run it, watch agents collaborate:
# 1. Install OSTwingit clone https://github.com/igot-ai/os-twin.gitcd os-twin && pwsh Install.ps1
# 2. Set your API keyexport ANTHROPIC_API_KEY="sk-ant-..."
# 3. Write a plancat > my-plan/PLAN.md << 'EOF'# My First Plan## Configprovider: anthropicmodel: claude-sonnet-4-20250514## GoalBuild a REST API with authentication and tests.## Epic 1: Auth System### DoD- JWT auth working with login/register endpoints### Tasks- TASK-001: Implement user model and auth routesEOF
# 4. Run itpwsh Engine.ps1 -PlanPath ./my-plan/PLAN.md