For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create and Assign Tasks

Turn requirements and action items into owned, trackable work.

Overview

Tasks turn approved scope into owned execution work.

They create accountability and progress tracking at the work-item level.

Key Concepts

  • Task: unit of delivery work with an owner and status

  • Assignee: single Teammate accountable for completion

  • Linked requirement: scope traceability from task to requirement

  • Due date: scheduling signal for planning and escalation

  • Dependency: sequencing constraint across tasks

How It’s Used

Create tasks during planning.

Update tasks during daily execution and weekly reviews.

Benefits

  • Clear ownership for execution work

  • Cleaner progress reporting

  • Better traceability from requirements to delivery evidence

Setup Steps

1

Create a task from the Tasks area

  1. Open the Project.

  2. Navigate to Tasks.

  3. Select Create task (or New task).

  4. Enter a short, verb-based task name.

  5. Select Create (or Save).

2
  1. Navigate to Requirements.

  2. Open a requirement.

  3. Select Create task (or equivalent action).

  4. Confirm the requirement link is created.

3

Assign an owner and set intent

  1. Set Assignee to one Teammate.

  2. Set Status to the correct starting state.

  3. Set a Due date when sequencing requires it.

  4. Add acceptance criteria in the description when needed.

4

Organize execution (optional)

  1. Add subtasks for multi-step work.

  2. Add dependencies for true sequencing constraints.

Related: Task Dependencies

Best Practices

  • Keep one assignee per task.

  • Keep tasks small enough for weekly reporting.

  • Link tasks to requirements for traceability.

  • Use Blocked only with an unblock condition.

  • Record decisions and changes in comments for auditability.

Summary

Tasks provide the execution backbone for delivery work.

Next actions:

Last updated