trellis-continue

Resume an in-progress Trellis task by identifying the current workflow phase and next action.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you resume an interrupted Trellis task without guessing what to do next, so you can pick up the correct phase and avoid repeating work.

Core Features & Use Cases

  • Loads the current task context and Git state to establish where the work left off.
  • Reads the phase index, checks task status and artifact presence, and routes you to the correct next step.
  • Use it when returning to planning, implementation, review, or completion on a Trellis-managed coding task.

Quick Start

Ask the assistant to resume the current Trellis task and determine the next phase using the workflow context.

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 interrupted coding task without losing my place in the workflow?

To resume an interrupted coding task, load the current task context and Git state to identify the workflow phase and route to the correct next step. This prevents guessing and avoids repeating completed work.

What is phase routing and how does it help continue a paused implementation session?

Phase routing identifies the current workflow stage—planning, implementation, review, or completion—and directs you to the appropriate next action. It uses the phase index and artifact presence to safely continue a paused session.

How do I check task status and artifacts before continuing a Trellis workflow?

Checking task status and artifacts involves reading the phase index and verifying artifact presence to determine the exact workflow state. This status check ensures you resume from the correct phase without overwriting work.

Can I use context loading to pick up a paused code review or planning phase?

Yes, context loading retrieves the current task state and Git history to resume paused planning, implementation, review, or completion phases. The phase-specific context loader routes you to the correct step safely.

Why does my resumed task start from the wrong workflow step after a Git pause?

Resuming from the wrong step happens when context loading fails to read the phase index or check artifact presence. Proper phase routing identifies the exact paused state—planning, review, or completion—to continue correctly.