trellis-continue

Resume in-progress Trellis tasks by loading workflow phase and context.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/imbingox/acex --skill trellis-continue-imbingox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-continue
Source: https://github.com/imbingox/acex/tree/main/.agents/skills/trellis-continue
Command: npx skills add https://github.com/imbingox/acex --skill trellis-continue-imbingox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resume work on in-progress Trellis tasks by loading the correct workflow phase and context.

Core Features & Use Cases

  • Phase detection and phase-specific context loading to re-enter the correct point in a Trellis workflow.
  • Status-aware routing that directs you to the next required step based on current task status.
  • Context restoration and guidance for multi-phase tasks to minimize downtime between sessions.

Quick Start

Run the resume context command to load the current phase and continue the Trellis workflow.

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 multi-phase task and load its correct workflow context?

To resume an in-progress multi-phase task, the skill identifies the current status and leverages phase routing in .trellis/workflow.md to load the correct workflow phase and its associated context for continuation.

How does phase routing determine the next actionable step in a Trellis workflow?

Phase routing uses status indicators and the get_context.py utility to evaluate the current task status, directing you to the specific next required step within the multi-phase Trellis workflow.

Can I restore task context for a Trellis workflow if I do not have a .trellis/workflow.md file?

No, you cannot restore task context without the .trellis/workflow.md file because the skill relies on this file for phase routing to detect the current phase and recover the associated status.

What is the best way to minimize downtime between sessions for complex task management?

The best way to minimize downtime between sessions is to use status-aware context restoration, which detects the exact workflow phase and provides guidance for the next actionable step to continue work immediately.

Do I need the get_context.py utility to recover the current status of a multi-phase task?

Yes, you need the get_context.py utility because it applies to multi-phase Trellis tasks to recover the current status, phase, and step, ensuring accurate phase-specific context loading.

Why does my Trellis workflow fail to re-enter the correct phase when resuming a task?

Re-entering the correct phase fails when status indicators are missing or the .trellis/workflow.md phase routing is misconfigured, preventing the skill from determining the next actionable step.