task

To track project task progress, activate a task by slug to load its context, enforce goals via QG-0, log progress after each plan step, and update the state until completion. This ensures full traceability against acceptance criteria.

End-to-end task execution across MCP-based tooling is coordinated by loading role and stack context, enforcing governance checks, and logging structured feedback through task log and task step commands until the task is done.

Enforcing QG-0 ensures required goals and acceptance criteria exist before starting work on a task loaded from the project database. This governance check prevents unstructured execution and guarantees traceability.

You can integrate role and stack context into task lifecycle tracking using MCP-driven memory. This reuses knowledge and decision history to guide plan steps and update task states throughout execution.

A task slug is required to load specific task context, goals, and plan steps from the project database. Without activating the slug, the system cannot enforce governance or record structured progress for the execution.

Predefined acceptance criteria are required to pass the QG-0 check and start task execution. Lifecycle tracking enforces these goals to ensure all logged plan steps and final completion meet the structured feedback loop.