Skip to main content
A task should represent one outcome that can be reviewed in a single scope.

​
Writing strong tasks

Good task titles are specific and reviewable:
  • Fix OAuth callback redirect loop
  • Add empty-state for archived projects
  • Refactor provider selector rendering

​
Add acceptance criteria in the first prompt

Include:
  • expected behavior
  • constraints
  • validation requirements
This keeps sessions aligned and reduces scope drift.

​
Archive policy

Archive tasks when complete to keep active lists focused.