trellis-continue

To resume an in-progress development workflow, you can run the trellis-continue skill to load phase routing and step mapping from stored workflow context. It determines the exact point to restart by reading task status and existing artifacts like prd.md and design.md.

Workflow context loading determines the next task action by using get_context.py to read the Phase Index and check for artifacts like implement.md and step-level jsonl curation. It routes you deterministically to the correct planning, execution, or review-gate stage based on these signals.

Yes, you can continue a partially complete task even if some step outputs are missing. The routing mechanism chooses the next action based on the presence or absence of files like prd.md, design.md, and implement.md, guiding you to complete the required outputs in order.

The best way to pick up a paused task moving from planning into review gates is to resume the workflow using stored context. The system identifies the transition point by evaluating task status and artifacts, then loads step-level instructions to proceed through the review gate.

You do not necessarily need completed artifacts like prd.md to use phase routing for workflow resume. The routing mechanism evaluates existing workflow signals and adapts to scenarios where artifacts are partially complete or still being generated during the planning stage.

Workflow resume may fail to load the correct step instructions in phase mode if the stored workflow context in .trellis/workflow.md is misconfigured or missing. Proper phase routing requires get_context.py to successfully index the phase and read task status to load deterministic next actions.