HOW MENGBOT TEAMS WORK

One file. One team. Three minutes to work.

Written for people and for AI: the Markdown file is the team manual, and MengBot runs it immediately.

01

One Markdown file

The YAML frontmatter is the exact blueprint. The Markdown body explains the mission and process to any person or agent product.

02

Review before install

MengBot previews the bots, Chief of Staff, channels, playbooks, apps, and routines before creating anything.

03

No hidden access

Connections stay off, routines arrive paused, and a package cannot contain credentials, conversations, memory, or computer permissions.

04

Forkable forever

Every team lives in a public GitHub repository, so anyone can inspect it, improve it, or adapt it for a new industry.

MENGBOT IMPORT

Preview. Approve. Activate.

The app turns package-local keys into fresh bots and channels. Existing records cannot be targeted by a shared file.

Add to MengBot
├── fetch public .md
├── validate structure
├── show complete preview
├── create fresh bots
├── build new channels
├── mark Chief of Staff
└── keep apps + routines off
UNIVERSAL FALLBACK

Give the same file to any Chief of Staff.

If a product does not understand the structured metadata, the readable playbook still tells its Chief of Staff how to recreate and coordinate the team.