agentleFS
Sign inStart free
hranesshraness/atet/.agents/skills/write-phase-plan/AGENTS.md

atet / write-phase-plan

AGENTS.md7 starsChanged 47 days agoMITView on GitHub

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Keep the plan format aligned with the companion phase-orchestrator contract.

    line 8
  2. Distinctive:

    Keep examples portable and defer repository-specific commands and delivery policy to the target repository.

    line 10
  3. Very specific:

    Update agents/openai.yaml when the skill name, trigger, or default invocation changes.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

Contents

  • SKILL.md – plan-authoring workflow for dependency-ordered phased execution.
  • agents/ – Codex UI metadata for discovering and invoking the skill.

Guidelines

  • Keep the plan format aligned with the companion phase-orchestrator contract.
  • Require explicit scope, acceptance criteria, validation commands, dependencies, and status conventions for every phase.
  • Keep examples portable and defer repository-specific commands and delivery policy to the target repository.
  • Update agents/openai.yaml when the skill name, trigger, or default invocation changes.

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.

Check your setup, free