Skip to main content

GOV 07 TASKS

This page embeds the canonical rule text and adds commentary after each section to explain why the section exists.

Governance: Tasks​

Commentary: Keeps execution state visible and prioritized across ongoing work.

Task Principle​

Tasks should make work reviewable, verifiable, and low-risk.

Commentary: Keeps execution state visible and prioritized across ongoing work.

Good Task Characteristics​

  • single clear outcome
  • explicit boundary/scope
  • testable acceptance check
  • realistic size for one focused execution pass

Commentary: Keeps execution state visible and prioritized across ongoing work.

Decomposition Guidance​

Break large work into tasks by behavior boundaries, not by files.

Prefer:

  • "add contract validation for X" over
  • "edit 5 files"

Commentary: Captures a specific delivery control so contributors and agents apply this rule consistently.

Backlog Hygiene​

  • keep status current (todo, in_progress, blocked, done)
  • prioritize unblocked high-impact work
  • record blockers with required decisions
  • avoid duplicate or stale tasks

Commentary: Captures a specific delivery control so contributors and agents apply this rule consistently.

Execution Discipline​

  • complete one scoped task with evidence
  • update task status immediately
  • move to next highest-priority unblocked item
  • stop only for blockers, empty backlog, or defined limits

Commentary: Captures a specific delivery control so contributors and agents apply this rule consistently.

Task Completion Evidence​

A task marked done should reference:

  • changed artifacts (paths)
  • verification run(s)
  • residual risks or follow-up tasks

Commentary: Keeps execution state visible and prioritized across ongoing work.