trellis-continue

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

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-continue-hejiajiudeeyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-continue
Source: https://github.com/hejiajiudeeyu/delegated-execution-workspace/tree/main/.agents/skills/trellis-continue
Command: npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-continue-hejiajiudeeyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to an in-progress task, it is easy to lose track of which workflow phase and step you were on. This Skill reloads the current task context, inspects the task status and existing artifacts, and routes you to the exact phase/step to resume in the Trellis workflow. ## Core Features & Use Cases - Context Reloading: Runs get_context.py to confirm the current task, git state, and recent commits before resuming work. - Status-Based Routing: Maps task status (planning, in_progress, completed) plus artifact presence (prd.md, implement.jsonl) to the correct workflow step such as 1.1, 1.3, 2.1, or 3.1. - Step-Level Instruction Loading: Fetches detailed instructions for a specific step via get_context.py --mode phase --step <X.X>. - Use Case: You return Monday morning to a half-finished feature task. Run this Skill to discover the task is in_progress with implementation done but not checked, so it routes you directly to step 2.2. ## Quick Start Ask the assistant to resume the current Trellis task and tell me 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 task after a break?▼

Run get_context.py to reload the current task, git state, and recent commits, then load the Phase Index with --mode phase. The task status field combined with existing artifacts determines 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 prd.md and a curated implement.jsonl routes to step 1.4, while status=in_progress with a passed check routes to step 3.1.

What artifacts does the Trellis workflow use to track progress?▼

The workflow tracks prd.md for the planning output and implement.jsonl for curated implementation entries. A seed _example row in implement.jsonl indicates curation has not happened yet.

Can I skip workflow steps that were already completed?▼

Yes, steps marked [once] are skipped if their output already exists, such as prd.md for step 1.1. Steps marked [required] must run in order and cannot be skipped within a phase.

What happens if the task status shows completed?▼

A completed status is rare because tasks are usually archived immediately. When encountered, the skill routes to the archive flow defined in .trellis/workflow.md.