mission-control-task-ops

Automating Mission Control task lifecycle management in Supabase involves centralizing creation, setting dependencies, enforcing statuses, and applying safe metadata updates. It requires explicit created_by_agent metadata on creation and prohibits cancellation of active tasks.

A cold-start brief for task-management workflows defines what to do, where to do it, acceptance criteria, context or why, and blockers for a new task. It provides foundational structure before execution begins in the pipeline.

To set dependencies and priorities across Supabase backlog tasks, you apply metadata.blocked_by and status fields. This coordinates upstream and downstream work to escalate when critical-path tasks stall.

The Safe Metadata Update Pattern merges changes safely without overwriting important fields in task-management pipelines. It patches metadata updates across the Mission Control task pipeline to prevent data loss during concurrent modifications.

No, you cannot cancel active Mission Control tasks in Supabase using this approach. The system enforces standardized statuses like todo, in_progress, in_review, and done, and explicitly prohibits cancellation of active tasks.

Yes, you need created_by_agent metadata to create tasks in Supabase workflows. Explicit created_by_agent metadata is required on creation to properly track task origin and automate lifecycle management within the pipeline.