skills.rest
42team-ru
42team-ruOFFICIAL
Explore all skills by this author →
GitHub

trellis-continue

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

2|Updated Jun 2, 2026
Search Tags:#workflow#context loading#project automation#phase routing#trellis#task resumption
One-click install
npx skills add https://github.com/42team-ru/teampilot --skill trellis-continue-42team-ru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-continue
Source: https://github.com/42team-ru/teampilot/tree/main/.agents/skills/trellis-continue
Command: npx skills add https://github.com/42team-ru/teampilot --skill trellis-continue-42team-ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to an in-progress task after a break, it is easy to lose track of which phase and step you were on. This Skill reloads the current task context, inspects the workflow Phase Index, and routes you to the exact step to resume. ## Core Features & Use Cases - Context Reloading: Runs get_context.py to confirm the current task, git state, and recent commits. - Status-Based Routing: Reads the task's status field (planning, in_progress, completed) plus artifact presence (prd.md, implement.jsonl) to determine the exact phase/step to resume. - Step-Level Detail Loading: Fetches instructions for a specific step via get_context.py --mode phase --step <X.X>. - Use Case: You return to a half-finished feature after the weekend. Run this Skill to discover the task is in status=in_progress with implementation done but not checked, so it routes you to step 2.2 with the relevant instructions loaded. ## Quick Start Ask the assistant to resume the current task and it will load the workflow context, determine the correct phase and step, and continue from there.

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 the trellis-continue flow, which calls get_context.py to load the current task, git state, and Phase Index. It then routes you to the correct step based on the task's status field and which artifacts already exist.

How does the skill decide which workflow step to resume at?▼

It reads the task's status field and checks 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.

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 go back to an earlier phase in the workflow?▼

Yes, the phase rules allow returning to an earlier phase if discoveries require it. Steps marked [once] are skipped if their output already exists, while [required] steps must run in order.

What happens if the task status is already completed?▼

A completed status is rare because tasks are usually archived immediately. If encountered, the skill routes to the archive flow rather than resuming implementation steps.

Related Skills

Explore More Software Engineering Skills→
dev2019zhengdev2019zheng

trellis-continue

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

Community
Intermediate
SilentFlowerSilentFlower

re-implement

Re-runs Implement and Check agents after PRD requirement changes in Trellis tasks.

Community
Intermediate
inayayousfiinayayousfi
1

commit

Drafts and confirms Git commit messages before committing staged changes.

Community
Intermediate
elebirdselebirds

trellis-continue

Resumes in-progress tasks by loading the Trellis workflow phase index and step context.

Community
Intermediate