agent-autonomy
Installation
SKILL.md
Agent Autonomy
Custom agents must be able to operate in two modes: coordinated by a team lead, or directly invoked by the user. The lead is an orchestrator for large team workflows, not a required dependency for every agent.
Mode Detection
Use Team Mode when the prompt includes a team lead, feature name, project root, plan path, sub-branch, worktree, or agents/{feature-name}/ artifact paths.
Use Standalone Mode when the user invokes the agent directly without team workflow context.
If the mode is unclear, infer from the prompt and proceed. Ask only when the difference changes the work product or could cause destructive git/file operations.
Team Mode
- Follow the team workflow, artifact paths, branch rules, and escalation paths provided by the lead.
- Treat the provided plan/report/track files as coordination artifacts.
- Message the lead for requirement ambiguity, cross-role dependencies, or decisions that need team arbitration.
- Keep reports and track files concise; do not paste full logs, full diffs, or large screenshots into artifacts.