trellis-continue

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

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/gyc-12/Archipelago --skill trellis-continue-gyc-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-continue
Source: https://github.com/gyc-12/Archipelago/tree/main/docs/trellis/skills/trellis-continue
Command: npx skills add https://github.com/gyc-12/Archipelago --skill trellis-continue-gyc-12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to an in-progress Trellis task, it is easy to lose track of which workflow phase and step you left off at. This Skill inspects the current task state and routes you to the exact step to resume, so no required step is skipped or repeated. ## Core Features & Use Cases - Context Loading: Runs get_context.py to confirm the current task, git state, and recent commits. - Phase Routing: Reads the task status field and artifact presence (prd.md, implement.jsonl) to determine whether to resume at Plan, Execute, or Finish phase steps. - Step-Level Detail: Loads instructions for a specific step via get_context.py --mode phase --step, following the canonical rules in .trellis/workflow.md. - Use Case: You return to a coding task after a day away and cannot remember whether the PRD was finished or implementation had started. Run this Skill to identify the exact step to pick up at and load its instructions. ## Quick Start Ask the assistant to resume the current Trellis task and determine 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 presence of artifacts like prd.md or implement.jsonl 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 combined with artifact presence. For example, status=planning with an existing prd.md and curated implement.jsonl routes to step 1.4, while status=in_progress with implementation done routes to step 2.2.

Can I skip workflow steps that were already completed?

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

What happens if the task status is completed?

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

Where is the full workflow documentation for Trellis phases?

The canonical guidance lives in .trellis/workflow.md, which contains the full workflow, skill routing table, and the DO-NOT-skip table. This skill is only an entry point to that documentation.