agentleFS
deanmikandeanmikan/ai-native-company-starter/work/AGENTS.md

ai-native-company-starter / work

AGENTS.md0 starsChanged 2 months agoMITView on GitHub

Current focus, active projects, decisions, and playbooks. This is where direction meets execution. - now.md is the single page for current priorities. Read it before any task that involves what to work on. Do not change its substance without the owner. - projects/ holds durable context, not task state. Verify status against the tracker registered in knowledge/sources.md before updating a page; never infer status from the last edit. Do not copy task lists in. - decisions/ are numbered and never…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a project ends, its durable outputs (decisions, playbooks, learnings, area page updates) must exist before the page moves to archive/.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

work/ rules

Current focus, active projects, decisions, and playbooks. This is where direction meets execution.

  • now.md is the single page for current priorities. Read it before any task that involves what to work on. Do not change its substance without the owner.
  • projects/ holds durable context, not task state. Verify status against the tracker registered in knowledge/sources.md before updating a page; never infer status from the last edit. Do not copy task lists in.
  • decisions/ are numbered and never rewritten. Use record-decision. To change a decision, write a new one that supersedes it.
  • playbooks/ must be usable during the work: short, ordered, with stop conditions. Link external runbooks instead of copying restricted detail.
  • When a project ends, its durable outputs (decisions, playbooks, learnings, area page updates) must exist before the page moves to archive/.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.