he-workflow

Multi-phase workflow state transitions are tracked by orchestrating sessions and updating a WORKFLOW_STATE.md file, allowing you to monitor progression through phases like init, spec, dev, test, review, and finalize with persistent state logs.

Automating phase progression and finalization tasks is handled by coordinating workflow transitions with guardrails for prerequisites, ensuring that each phase like dev or test meets specific criteria before advancing to finalize.

Yes, you can use templates to initialize workflow state, generating a consistent WORKFLOW_STATE.md file across multiple projects to ensure uniform session tracking and standardized phase progression right from setup.

Session state management works by storing ongoing work data under dedicated session directories, reading and writing updates to the workflow state file as actions progress, and logging changes to maintain an auditable history.

Yes, workflow state and phase transitions require a specific project context managed within a dedicated directory structure, ensuring that session data, state persistence, and finalization actions are properly scoped and tracked.

Workflow state transitions fail when prerequisite guardrails are not fully satisfied, preventing the progression from phases like dev or test to finalize until all required state persistence and change logging actions are completed.