A small, portable set of role definitions for a founder-led company using persistent AI agents. It is for solo founders and very lean teams that want agents to execute useful work without inventing an organizational chart.
A bot file defines the durable job: what the bot owns, how it works, where its authority ends, and what done means. A task instruction defines one desired result, its current context, constraints, and deadline. Put stable guidance in the bot file; keep temporary details in the task.
- The human founder remains CEO, product owner, and final decision-maker; chooses priorities; and approves consequential decisions.
- Bots execute within the authority documented in their files.
- Git stores durable responsibilities, boundaries, and working principles.
- The agent platform may retain task history and learned context.
- Work should usually be assigned directly to the bot that owns the outcome.
- Choose the bot that owns the desired outcome.
- Give its Markdown file to the agent platform as persistent or project-level instructions.
- Provide a separate task with the desired result, relevant context, constraints, and available sources.
- Review approval requests and the bot's final evidence against its definition of done.
Example:
Follow
bots/engineer.md. Fix the incorrect total shown after an item is removed. Reproduce the issue, make the smallest correct change, add a regression test, and summarize validation and remaining risks. Ask before taking any action outside the authority in the bot file.
Update a definition from observed behavior, not speculation. When a bot repeatedly makes the same avoidable mistake or needs the same clarification, add the smallest rule or boundary that would prevent it. When guidance is unused, redundant, or creates overhead, simplify or remove it. Commit the reason for material changes so the operating model remains understandable.
Create a bot only when a distinct outcome recurs, has clear success measures, and cannot be owned cleanly by an existing bot. Use templates/bot-template.md to define its authority and completion criteria.
Do not create a bot for a one-time project, a narrow skill, extra status reporting, or coordination between other bots. Extend an existing bot first. Merge, pause, or delete a bot when its work is no longer recurring or it does not produce distinct value. Keep the smallest useful roster.
- No speculative employees.
- No bot whose primary purpose is managing another bot.
- No recurring process without a demonstrated need.
- No automation before the underlying workflow is reliable.
- No new role until repeated work clearly requires one.
- Delete or merge bots that are not producing distinct value.
- Prefer execution over meetings, reports, and process.
Licensed under the ISC License.