piyaz
Using PiyazWeb app

Tasks

View, edit, and track tasks through their lifecycle in the UI.

Tasks

The workspace has three surfaces: the Navigator on the left (task list and graph), the Detail panel in the middle (the selected task), and a Property rail on the right for the task's fields. The property rail is a third column on wide screens and a drawer on narrower ones. When no task is selected, the detail area shows an empty state.

Screenshot coming soon.

The left panel shows tasks in two modes.

Structure mode

A task list grouped by status by default. You can switch the grouping to category or turn grouping off. Each row is a single line showing a status glyph, the task id, dependency hints, a category dot, the title, the last-active time, the priority, and assignee avatars.

Graph mode

An interactive force-directed graph. See Graph view for details.

Detail panel

Selecting a task opens the detail panel in the middle. It shows, top to bottom:

  • Description, editable inline.
  • Acceptance criteria, checkable items that define done.
  • Context bundle preview: a preview of the context an agent receives for this task, with a badge for the current stage.
  • Decisions: choices recorded with their rationale.
  • Relationships: connected tasks with their edge types and notes.
  • Links: attached links, such as the pull request.
  • Execution record: the summary of what was built.
  • Activity: the task's history.

The implementation plan is not a standalone section; it appears inside the context bundle preview.

Property rail

The right rail holds the task's structured fields: status, priority, estimate, assignees, category, tags, dependencies, and files. Some fields are read-only. Edits save automatically.

Task states

Beyond the lifecycle status (see Task lifecycle), Piyaz derives an actionable state that accounts for dependencies:

StateMeaning
draftMissing description or acceptance criteria.
plannableDraft with enough spec to write a plan. Dependencies do not block it.
blockedHas unfinished dependencies. Cannot proceed.
readyPlanned and all dependencies done. Can be implemented now.
in_progressClaimed and being worked on.
doneComplete.

The navigator shows these derived states so you can see what is actionable at a glance.

On this page