workflow

Multi-service feature workflows are tracked using a unified state machine that manages phases, branches, and PRs across services. This reduces state drift and ensures team alignment through deterministic context-switching and gate-checked transitions.

A state-machine driven lifecycle enforces deterministic transitions between feature phases like brainstorming, PRD creation, and implementation. It applies gate rules and session checks to validate state changes before allowing work to proceed.

Context switching across active features and workspaces is managed by the unified state machine. It tracks current statuses and phases, allowing product development teams to deterministically switch contexts without losing track file alignment.

Gate-checked transitions support team collaboration by enforcing session checks and onboarding integration before allowing state changes. This ensures multi-service feature work meets defined criteria before progressing through the lifecycle.

A unified state machine is needed when coordinating multi-service feature work requires consistent state management across phases, branches, and track files. It prevents state drift and ensures alignment during complex product development.