kwila/shelley-extras
1
0
Fork 1
Code Pull requests Releases Activity Actions

docs: restructure AGENTS.md with manager role first #11

Merged
addison merged 4 commits from exe-dev-bot/shelley-extras:docs/plan-before-implementing into main 2026-01-30 22:06:14 -05:00
Conversation 0 Commits 4 Files changed 1 +94 -132
exe-dev-bot commented 2026-01-30 21:50:23 -05:00
Contributor
Copy link

Summary

Complete restructure of AGENTS.md to put the most critical guidance first and make it actionable.

Key Changes

1. "You Are a Manager, Not an Implementer" - Now First Section

This is the most important behavioral guidance. It was previously buried in the middle as "Subagents as Expert Consultants". Now it is:

  • The first thing agents read after the header
  • Explicit about the manager role
  • Clear about what to delegate vs what to do yourself

2. First Tool Call Rule

New forcing function: For any non-trivial task, the FIRST action must be a think call that plans the work and delegation strategy. This prevents agents from getting sucked into implementation before planning.

3. Streamlined Structure

Before: Guidelines, subagents, git, spec writing, conversation workflow, exe.dev, forgejo (all roughly equal weight)

After:

  1. Manager role + planning (critical)
  2. Git workflow (important)
  3. General guidelines (reference)
  4. Conversation workflow (process)
  5. exe.dev + Forgejo API (reference material at end)

4. Other Additions

  • Singular table names convention
  • Consolidated subagent patterns

Context

This came from a task where I read all the subagent guidance and still did implementation work myself. The previous structure didn't emphasize the manager role strongly enough.

## Summary Complete restructure of AGENTS.md to put the most critical guidance first and make it actionable. ## Key Changes ### 1. "You Are a Manager, Not an Implementer" - Now First Section This is the most important behavioral guidance. It was previously buried in the middle as "Subagents as Expert Consultants". Now it is: - The first thing agents read after the header - Explicit about the manager role - Clear about what to delegate vs what to do yourself ### 2. First Tool Call Rule New forcing function: For any non-trivial task, the FIRST action must be a `think` call that plans the work and delegation strategy. This prevents agents from getting sucked into implementation before planning. ### 3. Streamlined Structure **Before:** Guidelines, subagents, git, spec writing, conversation workflow, exe.dev, forgejo (all roughly equal weight) **After:** 1. Manager role + planning (critical) 2. Git workflow (important) 3. General guidelines (reference) 4. Conversation workflow (process) 5. exe.dev + Forgejo API (reference material at end) ### 4. Other Additions - Singular table names convention - Consolidated subagent patterns ## Context This came from a task where I read all the subagent guidance and still did implementation work myself. The previous structure didn't emphasize the manager role strongly enough.
- When tackling multi-component tasks, agents should plan first and
  delegate to subagents rather than implementing everything themselves.

- Database tables should use singular names (user, record, customer).

Co-authored-by: Shelley <shelley@exe.dev>
- Move 'You Are a Manager, Not an Implementer' to the top as the
  most important section
- Add 'First Tool Call Rule' - must use think tool to plan before
  any implementation
- Consolidate subagent guidance into clear patterns
- Move reference material (Forgejo API) to the end
- Streamline general guidelines
- Add singular table names convention

Co-authored-by: Shelley <shelley@exe.dev>
exe-dev-bot changed title from docs: add planning guidance and singular table names convention to docs: restructure AGENTS.md with manager role first 2026-01-30 21:56:16 -05:00 
Can't plan delegation before understanding the codebase.
Planning happens after exploration, not before.

Co-authored-by: Shelley <shelley@exe.dev>
Co-authored-by: Shelley <shelley@exe.dev>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kwila/shelley-extras!11
No description provided.