Plans
Plans let a team run its work in dagsec: goals split into tasks that members and their AI agents take, do and hand in. A task is done when its pull request passes dagsec and is merged, never because an agent says so.
Plans are off until the team's owner turns them on, under Teams → Plans.
Plans and tasks
| Plan | A goal, such as "Release 2.0 by the end of the month", for the whole team or one area |
| Task | Part of a plan: a title, details, acceptance criteria (one per line), priority, area and person |
| Status | To do → Doing → In review → Done, or Cancelled |
| Open task | Anyone in the team, or their AI agent, can take it |
A team can have 20 open plans, each with up to 200 tasks.
Deleting a plan deletes its tasks too and can't be undone; close it instead to keep the history.
Who does what
| Owner, admin | Member | Member's AI agent | |
|---|---|---|---|
| Start, edit, close and delete plans | yes | no | no |
| Add tasks | yes | for themselves | yes, marked "added by AI" |
| Assign tasks | to anyone | take open tasks | take open tasks for its person |
| Change status | any | own tasks, up to In review | own tasks, up to In review |
| Mark done or cancelled | yes | no | no |
The owner can stop agents from adding tasks or taking open tasks.
Done means merged and passed
Name the task in the pull request: write dagsec: #12 in its description, or name the branch task-12-…. With the GitHub App installed on a repository the team added under Repositories:
- When dagsec checks the pull request, it links it to the task and moves the task to In review.
- When the pull request is merged and dagsec's last check on it passed, the task is done, and its person is told.
A merged pull request that failed dagsec's check leaves the task in review. A pull request in another team's repository can't touch the task. The owner or an admin can always mark a task done by hand.
AI agents
dagsec's MCP server gives agents these tools:
| Tool | What it does |
|---|---|
plan_list | The team's open plans and unfinished tasks, the user's own first, with acceptance criteria |
task_take | Takes an open task for the user and starts it |
task_create | Adds a task to a plan, marked "added by AI" |
task_update | Moves the user's task to Doing or In review, or edits it |
task_done_check | What a task still needs: a linked pull request, a passing check, the merge |
When a member starts a Claude Code session in one of the team's repositories, Claude also gets their unfinished tasks with the team's notes and rules (with the desktop app's Claude Code hook).
Plan tools don't count against the monthly agent checks.
Weekly email
Owners and admins get a line per team in their weekly email with the tasks finished that week.