trellis-continue

Resumes in-progress Trellis tasks by loading workflow phase context and routing to the correct step.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-continue-jiozhaoyue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-continue
Source: https://github.com/jiozhaoyue/ST-BgLoader/tree/main/.reasonix/skills/trellis-continue
Command: npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-continue-jiozhaoyue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to an in-progress task, it is easy to lose track of which phase or step you were on in the Trellis workflow. This Skill removes that guesswork by inspecting the current task state and telling you exactly where to pick up. ## Core Features & Use Cases - Context Loading: Runs get_context.py to confirm the current task, git state, and recent commits before resuming work. - Phase Routing: Reads the task status field and artifact presence (prd.md, design.md, implement.md) to route you to the correct phase step, from planning through implementation to commit. - Step-Level Detail: Loads instructions for a specific step via get_context.py --mode phase --step, so you follow the canonical workflow in .trellis/workflow.md. - Use Case: You return to a feature task after a day away. Run this Skill to discover the task is in_progress with implementation done but not checked, so it routes you to step 2.2 for verification. ## Quick Start Ask the assistant to resume the current Trellis task and tell you which workflow step to continue from.

Frequently Asked Questions about trellis-continue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an in-progress Trellis task?▼

Run get_context.py to confirm the current task and git state, then load the Phase Index with --mode phase. The task status field and existing artifacts like prd.md determine which step to resume at.

How does the skill decide which workflow step to continue from?▼

It routes based on the task status field plus artifact presence. For example, status=planning with only prd.md routes to review or design work, while status=in_progress with implementation done routes to the check step.

What is the difference between lightweight and complex Trellis tasks?▼

Lightweight tasks can move to review with only prd.md complete. Complex tasks additionally require design.md and implement.md before proceeding to the start review step.

Does trellis-continue approve implementation or start tasks automatically?▼

No. It only loads context and routes to the right step. The task.py start command runs only after the user confirms the start review, and the skill itself never approves implementation.

Where is the full Trellis workflow documented?▼

The canonical workflow and detailed phase steps live in .trellis/workflow.md. This skill is only an entry point that loads the relevant portions via get_context.py.