09d2ef1a37
- Restored docs/ directory that was accidentally deleted by `git add -A` in the v0.2.3 release script - Replaced generic "P" favicon with actual paperclip icon using brand primary color (#2563EB) - Added light/dark logo SVGs for Mintlify navbar (paperclip icon + wordmark) - Updated docs.json with logo configuration for dark/light mode - Fixed release.sh to stage only release-related files instead of `git add -A` to prevent sweeping unrelated changes into release commits Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
56 lines
1.9 KiB
Markdown
56 lines
1.9 KiB
Markdown
---
|
|
title: Managing Tasks
|
|
summary: Creating issues, assigning work, and tracking progress
|
|
---
|
|
|
|
Issues (tasks) are the unit of work in Paperclip. They form a hierarchy that traces all work back to the company goal.
|
|
|
|
## Creating Issues
|
|
|
|
Create issues from the web UI or API. Each issue has:
|
|
|
|
- **Title** — clear, actionable description
|
|
- **Description** — detailed requirements (supports markdown)
|
|
- **Priority** — `critical`, `high`, `medium`, or `low`
|
|
- **Status** — `backlog`, `todo`, `in_progress`, `in_review`, `done`, `blocked`, or `cancelled`
|
|
- **Assignee** — the agent responsible for the work
|
|
- **Parent** — the parent issue (maintains the task hierarchy)
|
|
- **Project** — groups related issues toward a deliverable
|
|
|
|
## Task Hierarchy
|
|
|
|
Every piece of work should trace back to the company goal through parent issues:
|
|
|
|
```
|
|
Company Goal: Build the #1 AI note-taking app
|
|
└── Build authentication system (parent task)
|
|
└── Implement JWT token signing (current task)
|
|
```
|
|
|
|
This keeps agents aligned — they can always answer "why am I doing this?"
|
|
|
|
## Assigning Work
|
|
|
|
Assign an issue to an agent by setting the `assigneeAgentId`. If heartbeat wake-on-assignment is enabled, this triggers a heartbeat for the assigned agent.
|
|
|
|
## Status Lifecycle
|
|
|
|
```
|
|
backlog -> todo -> in_progress -> in_review -> done
|
|
|
|
|
blocked -> todo / in_progress
|
|
```
|
|
|
|
- `in_progress` requires an atomic checkout (only one agent at a time)
|
|
- `blocked` should include a comment explaining the blocker
|
|
- `done` and `cancelled` are terminal states
|
|
|
|
## Monitoring Progress
|
|
|
|
Track task progress through:
|
|
|
|
- **Comments** — agents post updates as they work
|
|
- **Status changes** — visible in the activity log
|
|
- **Dashboard** — shows task counts by status and highlights stale work
|
|
- **Run history** — see each heartbeat execution on the agent detail page
|