Skip to content

Tasks

Who can use it: Architects, Developers, QA and Super Admins create and work on tasks. Project Managers read them. Clients don’t see tasks.

Tasks turn an approved spec into work. Each one has a brief (instructions for the developer or their coding assistant) and links to the acceptance criteria it delivers. Tasks are numbered per feature, for example REQ-4/T2.

Arjun splits REQ-4 into two tasks:

  • T1 · Order history endpoint, linked to AC1
  • T2 · Reorder button and stock check, linked to AC2 and AC3

Arjun starts T1, builds it, and submits it with the pull request link. Meera reviews the PR, merges it and approves T1. T2 follows the same path.

flowchart LR
    A1["AC1"] --- T1["T1 · Order history endpoint"]
    A2["AC2"] --- T2["T2 · Reorder button + stock check"]
    A3["AC3"] --- T2

The Tasks tab lists every acceptance criterion and shows ✓ or No task yet, so gaps are obvious.

stateDiagram-v2
    [*] --> ToDo
    ToDo --> InProgress: Start
    InProgress --> InReview: Submit PR
    InReview --> Done: Architect approves
    InReview --> InProgress: Request changes
    Done --> InProgress: Reopen
    ToDo --> Cancelled: Cancel
    InProgress --> Cancelled: Cancel
    state "To do" as ToDo
    state "In progress" as InProgress
    state "In review" as InReview
  1. Open the feature’s Tasks tab. The spec must be approved.
  2. Add a task: write the brief and link one or more acceptance criteria.
  3. Start the task when you pick it up. Whoever starts it becomes its assignee.
  4. Build it, then submit with the pull request link.
  5. An Architect reviews the PR and CI, merges, then approves the task or requests changes.

Export a task as Markdown, with its criteria, the requirement and the approved spec. Or let an AI agent read it directly.

Tasks in the project lists tasks across every feature.