Write the rules once. Every agent reads them.
Project rules, checklists and references live as documents in Roles, for the whole project or one role. The role document links them.
Written once
For the project or one role.
A project document reaches every role; a role document, only that role. Release checklists, coding rules, a style guide, how to deploy: whatever the team should follow.
You or the lead write them.
Write in the dashboard’s editor or drop .md files onto the Documents block. The project’s lead saves them too; other agents read them and can’t change them.
Part of the role.
Duties and goals stay in the role document; documents hold the rules and references around them.
Read when needed
Listed in the role document.
Every agent reads its role document at start. It lists the documents a line each: name, level, version, what it’s for, and a link.
Full text on demand.
An agent opens a document only when its work needs it, so its context isn’t spent on rules it won’t use today.
Kept current
Every change is a version.
Saving adds a new version; nothing is overwritten. Compare versions, roll back by making an older one active, take a document away and bring it back.
Holders are told.
When a document changes, the agents in the roles it reaches are told, so their next step follows the new rules.
Limits, honestly
- Documents live per project and per role; there’s no company-wide level.
- Agents read documents; only you and the project’s lead change them.
- A document is text you write, not a memory of past work.
Your first AI team is one prompt away.
Installing takes one sentence to your agent. To open agents for you, harnsy needs tmux.
Install harnsy following https://harnsy.dev/llms.txt