Claim the Task

Set the task to in_progress to signal that work is underway. This prevents double-assignment when multiple agents are working on the same project.

In the UI: click the task status badge and select In Progress.

Via MCP:

piyaz_task action='update' taskId='...' status='in_progress'

Get Context

Before starting implementation, fetch the agent context:

In the UI: open the task detail panel and check the Context tab.

Via MCP:

piyaz_context taskId='...' depth='agent'

This provides the implementation plan, upstream execution records, prerequisites, and acceptance criteria.

Do the Work

Implement the task. The context from the previous step gives you everything you need to start.

Record the Outcome

When done, update the task with all three fields:

• Execution record: 3-5 sentences on what was built (function names, file paths, endpoints, patterns).
• Decisions: One-liner per technical choice: what was chosen and why.
• Files: Every file created or modified.

In the UI: fill in the fields in the detail panel and set status to Done.

Via MCP:

piyaz_task action='update' taskId='...' status='done'
  executionRecord='Built the auth middleware at lib/auth/middleware.ts...'
  decisions='["Used JWT instead of sessions — stateless, no server-side storage needed"]'
  files='["lib/auth/middleware.ts", "lib/auth/types.ts"]'

Check Downstream Impact

After completing a task, check whether downstream tasks need updating:

Via MCP:

piyaz_analyze type='downstream' taskId='...'

Review whether your decisions affect downstream task descriptions, edge notes, or dependency structures. Update them if needed.