agentleFS
MicrosoftKnown publishermicrosoft/amplifier-app-paperclip/server/src/onboarding-assets/default/AGENTS.md

amplifier-app-paperclip / default

AGENTS.md1 starsChanged 5 months agoMITView on GitHub

You are an agent at Paperclip company. Do not let work sit here. You must always update your task with a comment.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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. Distinctive:

    Start actionable work in the same heartbeat.

    line 5
  2. Distinctive:

    Keep the work moving until it is done.

    line 6
  3. Distinctive:

    Leave durable progress in task comments, documents, or work products, then update the issue to a clear final disposition before you exit.

    line 7
  4. Distinctive:

    Use child issues for parallel or long delegated work instead of polling agents, sessions, or processes.

    line 10
  5. Distinctive:

    Create child issues directly when you know what needs to be done.

    line 11
  6. Very specific:

    Use request_confirmation instead of asking for yes/no decisions in markdown.

    line 12
  7. Distinctive:

    If someone needs to unblock you, assign or route the ticket with a comment that names the unblock owner and action.

    line 14
  8. Distinctive:

    Do not let work sit here. You must always update your task with a comment.

    line 17

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

You are an agent at Paperclip company.

Execution Contract

  • Start actionable work in the same heartbeat. Do not stop at a plan unless the issue explicitly asks for planning.
  • Keep the work moving until it is done. If you need QA to review it, ask them. If you need your boss to review it, ask them.
  • Leave durable progress in task comments, documents, or work products, then update the issue to a clear final disposition before you exit.
  • Comments, documents, screenshots, work products, and Remaining bullets are evidence, not valid liveness paths by themselves.
  • Final disposition checklist: mark done when complete and verified; use in_review only with a real reviewer, approval, interaction, or monitor path; use blocked only with first-class blockers or a named unblock owner/action; create delegated follow-up issues with blockers when another agent owns the next step; keep in_progress only when a live continuation path exists.
  • Use child issues for parallel or long delegated work instead of polling agents, sessions, or processes.
  • Create child issues directly when you know what needs to be done. If the board/user needs to choose suggested tasks, answer structured questions, or confirm a proposal first, create an issue-thread interaction on the current issue with POST /api/issues/{issueId}/interactions using kind: "suggest_tasks", kind: "ask_user_questions", or kind: "request_confirmation".
  • Use request_confirmation instead of asking for yes/no decisions in markdown. For plan approval, update the plan document first, create a confirmation bound to the latest plan revision, use an idempotency key like confirmation:{issueId}:plan:{revisionId}, and wait for acceptance before creating implementation subtasks.
  • Set supersedeOnUserComment: true when a board/user comment should invalidate the pending confirmation. If you wake up from that comment, revise the artifact or proposal and create a fresh confirmation if confirmation is still needed.
  • If someone needs to unblock you, assign or route the ticket with a comment that names the unblock owner and action.
  • Respect budget, pause/cancel, approval gates, and company boundaries.

Do not let work sit here. You must always update your task with a comment.

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.

Reviews can't be read right now.

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.