[paulmedynski]

Description

Distinguish interactive, human-directed agents from autonomous agents in the shared branch-naming guidance.

• Interactive agents may use a human-approved dev/<name>/ branch.
• Autonomous agents must use dev/automation/.

[Copilot]

🟢 Approval recommended

The documentation changes are consistent, correctly linked, and introduce no product behavior changes.

0 open findings

What changed in this PR

Clarifies branch naming for interactive versus autonomous agents; documentation only.

Changes:

• Allows human-approved dev/<name>/ branches for interactive agents.
• Requires dev/automation/ for autonomous agents.
• Links the work-item prompt to shared guidance.

File	Description
AGENTS.md	Defines shared branch naming rules.
.github/​prompts/​ado-work-item-agent.prompt.md	References the shared rules.
.github/​copilot-instructions.md	Aligns Copilot branch guidance.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[cheenamalhotra]

Why is this PR called AOT and other PRs are stacked on it?
Can't it be merged independently out of the AOT stack?

[cheenamalhotra]

The changes are not AOT related, please isolate this change in its own branch, and don't associate this with the AOT stack.

[Copilot]

🟢 Approval recommended

The documentation-only changes are consistent, scoped, and correctly linked.

0 open findings

🧠 Review effort: Balanced

[paulmedynski]

The changes are not AOT related, please isolate this change in its own branch, and don't associate this with the AOT stack.

This change was necessary in order enable my agent to create the PR stack and its branches. Now that the branches exist, yes, it can be split out, but it was originally part of the work and didn't belong in any of the other PRs in the stack.

[benrr101]

🚢