trellis-continue

To resume an interrupted software development task, retrieve the workflow context and route the task to the correct phase. This identifies the current project state and determines whether planning, implementation, validation, or completion work should happen next.

Workflow context recovery restores task status, git state, and phase information for interrupted development work. You need it when returning to an unfinished implementation task to avoid manually reconstructing project progress.

To determine the correct workflow phase, map existing task artifacts and status to phase routing instructions. This step routing guidance directs the development task to the appropriate planning, execution, or validation stage.

Yes, phase routing continues software development tasks consistently by loading existing project context. It requires workflow context retrieval to map the current state to the correct next action without losing progress.

The best way to recover project context is using task continuation instructions that load task status and git state. This restores development context and routes the work to the appropriate workflow phase.

Manually reconstructing task progress fails because it misses critical workflow context and phase routing dependencies. Retrieving the existing project state ensures the interrupted task resumes at the correct validation or implementation step.