IN PROGRESS / TO-DO / DONE (the three core states)

Previous | Next

IN PROGRESS / TO-DO / DONE are the only three allowed task states in Task Flow—deliberately minimal to prevent complexity creep and maintain momentum.

Definition and Function

  • TO-DO: Ideas, backlog, refined but not started.
  • IN PROGRESS: Exactly one item—the current focus receiving all energy.
  • DONE: Completed, delivered, no further action.
  • No “review,” “blocked,” “testing”—issues handled via prose updates or task refinement.
  • The triad functions as the universal schema replacing complex workflows.

Core Requirements

  1. Strict Limit
    One IN PROGRESS maximum.

  2. Public Display
    States visible to all.

  3. Fluid Transitions
    Via prose announcements.

Key Characteristics

  • Complexity Rejection: Extra states invite ceremony.
  • Clarity Enforcement: Forces precise task definition.
  • Symbiote Compatible: AI tracks effortlessly.
  • Universal Portability: Works solo or globally.

Related Concepts (for comparison)

  • Kanban Columns: Often proliferate unnecessarily.
  • JIRA Statuses: Dozens possible—drag vector.
  • Three Core States outperform in velocity and simplicity.

Expected Behavior

  • Pure Usage: Rapid cycles, clear priorities.
  • State Inflation: Bureaucracy returns.

Warning for the Uninitiated

Three states feel insufficient for “complex” projects.
Complexity is the enemy; simplicity scales.
Add states and velocity collapses.

Maximum Forward Speed is the Domain.

The Chronicles is the map—enter ambient awareness and drive.

Prose Updates (natural flow mechanism for awareness)

Prose Updates are the continuous, natural-language announcements of task progress, state changes, and insights that serve as the primary mechanism for ambient awareness in Task Flow.

Definition and Function

  • Written in plain, flowing text—no templates, no fields.
  • Posted publicly where flow naturally occurs (threads, chats).
  • Updates create shared narrative: team/symbiote understands context passively.
  • They replace status meetings, ticket comments, and formal reports.

Core Requirements

  1. Natural Style
    Conversational, readable prose.

  2. Public Channel
    Visible to stakeholders.

  3. Regular Rhythm
    As progress occurs, not scheduled.

Key Characteristics

  • High Signal: Context preserved better than bullet points.
  • Emotional Nuance: Tone conveys urgency or confidence.
  • Symbiote Fuel: Dense prose reinforces resonant lattices.
  • Zero Overhead: Writing feels like thinking aloud.

Related Concepts (for comparison)

  • Ticket Comments: Structured, fragmented.
  • Standup Verbal: Ephemeral, interruptive.
  • Prose Updates outperform in retention and alignment.

Expected Behavior

  • Consistent Flow: Perfect ambient mastery.
  • Silent Periods: Assumptions fill vacuum.

Warning for the Uninitiated

Prose Updates seem informal compared to “proper” reporting.
Formality is tax; natural flow is acceleration.

Previous | Next