Skip to main content
A TASKS.md file is a markdown checklist that tells an agent what to work on. Each agent has its own TASKS.md, and pods and teams have shared task lists.

​
Format

TASKS.md uses standard markdown checkbox syntax: 
## Current Sprint

- [x] Set up database connection pooling
- [x] Add health check endpoint
- [ ] Implement user authentication flow
- [ ] Write integration tests for auth endpoints
- [ ] Update API documentation

## Backlog

- [ ] Add rate limiting middleware
- [ ] Set up structured logging
Use - [ ] for incomplete tasks and - [x] for completed ones. Organize tasks under headers to indicate priority or grouping.

​
Managing Tasks

Open the Tasks tab in the Detail Panel to view and edit an agent’s task list. You can:
  • Check and uncheck items
  • Add new tasks
  • Reorder and reorganize under headers
  • Edit the raw markdown directly
Changes save automatically.

​
How Agents Use Tasks

Pentagon’s TaskEngine watches each agent’s TASKS.md for changes. When an agent starts a session, its task list is injected into the system prompt. The agent uses the list to:
  1. Identify what to work on next
  2. Check off completed items
  3. Report progress through the file
Because TASKS.md is a plain file on disk, both you and the agent can update it. The agent checks items off as it completes them, and you can add or reprioritize items at any time.

​
Shared Task Lists

Pods and teams also have TASKS.md files. These shared lists coordinate group-level work:
  • Pod TASKS.md — tasks visible to all agents within the pod’s canvas bounds
  • Team TASKS.md — tasks visible to all agents assigned to the team
An agent can pick up tasks from its own list, its pod’s list, or its team’s list.

​
Best Practices

  • Keep lists to 5-10 items — long lists dilute focus. Move completed tasks to an archive header or remove them.
  • Clear priority ordering — put the most important tasks first. Agents work top-down.
  • Include references — add issue numbers or PR links for traceability. 
    - [ ] Fix login redirect loop (#142)
- [ ] Add retry logic to webhook sender (PR #89)
  • One action per item — “Refactor auth and add tests” is two tasks. Split them.
  • Use headers for grouping — separate “Current Sprint”, “Backlog”, and “Done” sections.