How do I install the Trellis Continue skill?

Run npx skillmds@latest add livelybug/trellis-continue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Trellis Continue safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Trellis Continue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Trellis Continue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Trellis Continue?

livelybug (@livelybug) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Trellis Continue by livelybug — Agent Skill

Name: Trellis Continue
Rating: 4.2 (5 reviews)
Author: livelybug

Trellis Continue

Resume work on the current task. Loads the workflow Phase Index, figures out which phase/step to pick up at, then pulls the step-level detail via get_context.py --mode phase. Use when coming back to an in-progress task and you need to know what to do next.

livelybug Updated Sep 8, 2026 0 repo stars

File contents

Continue Current Task

Resume work on the current task — pick up at the right phase/step in .trellis/workflow.md.

Step 1: Load Current Context

python3 ./.trellis/scripts/get_context.py

Confirms: current task, git state, recent commits.

Step 2: Load the Phase Index

python3 ./.trellis/scripts/get_context.py --mode phase

Shows the Phase Index (Plan / Execute / Finish) with routing + skill mapping.

Step 3: Decide Where You Are

get_context.py shows the active task's status field. Route by status + artifact presence. This command replaces the user needing to remember the Trellis flow; it does not itself approve implementation.

status=planning + no prd.md → 1.1 (load trellis-brainstorm)
status=planning + prd.md only → decide whether the task is lightweight or complex. Lightweight can move to 1.4 review; complex returns to 1.1 to add design.md + implement.md.
status=planning + complex artifacts complete + sub-agent jsonl not curated (only the seed _example row) → 1.3
status=planning + required artifacts complete + required jsonl curated or inline mode → 1.4 (ask for start review; only run task.py start after user confirms)
status=in_progress + implementation not started → 2.1
status=in_progress + implementation done, not yet checked → 2.2
status=in_progress + check passed → 3.3 (spec update) → 3.4 (commit)
status=completed (rare; usually archived immediately) → archive flow

Phase rules (full detail in .trellis/workflow.md):

Run steps in order within a phase — [required] steps must not be skipped
[once] steps are already done if the required output exists. prd.md alone can be enough only for lightweight tasks; complex tasks also need design.md and implement.md.
You may go back to an earlier phase if discoveries require it

Step 4: Load the Specific Step

Once you know which step to resume at:

python3 ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform codex

Follow the loaded instructions. After each [required] step completes, move to the next.

Reference

Full workflow and detailed phase steps live in .trellis/workflow.md. This command is only an entry point — the canonical guidance is there.

---name: trellis-continuedescription: Resume work on the current task. Loads the workflow Phase Index, figures out which phase/step to pick up at, then pulls the step-level detail via get_context.py --mode phase. Use when coming back to an in-progress task and you need to know what to do next.---# Continue Current TaskResume work on the current task — pick up at the right phase/step in `.trellis/workflow.md`.---## Step 1: Load Current Context```bashpython3 ./.trellis/scripts/get_context.py```Confirms: current task, git state, recent commits.## Step 2: Load the Phase Index```bashpython3 ./.trellis/scripts/get_context.py --mode phase```Shows the Phase Index (Plan / Execute / Finish) with routing + skill mapping.## Step 3: Decide Where You Are`get_context.py` shows the active task's `status` field. Route by `status` + artifact presence. This command replaces the user needing to remember the Trellis flow; it does not itself approve implementation.- `status=planning` + no `prd.md` → **1.1** (load `trellis-brainstorm`)- `status=planning` + `prd.md` only → decide whether the task is lightweight or complex. Lightweight can move to **1.4** review; complex returns to **1.1** to add `design.md` + `implement.md`.- `status=planning` + complex artifacts complete + sub-agent jsonl not curated (only the seed `_example` row) → **1.3**- `status=planning` + required artifacts complete + required jsonl curated or inline mode → **1.4** (ask for start review; only run `task.py start` after user confirms)- `status=in_progress` + implementation not started → **2.1**- `status=in_progress` + implementation done, not yet checked → **2.2**- `status=in_progress` + check passed → **3.3** (spec update) → **3.4** (commit)- `status=completed` (rare; usually archived immediately) → archive flowPhase rules (full detail in `.trellis/workflow.md`):1. Run steps **in order** within a phase — `[required]` steps must not be skipped2. `[once]` steps are already done if the required output exists. `prd.md` alone can be enough only for lightweight tasks; complex tasks also need `design.md` and `implement.md`.3. You may go back to an earlier phase if discoveries require it## Step 4: Load the Specific StepOnce you know which step to resume at:```bashpython3 ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform codex```Follow the loaded instructions. After each `[required]` step completes, move to the next.---## ReferenceFull workflow and detailed phase steps live in `.trellis/workflow.md`. This command is only an entry point — the canonical guidance is there.

Frequently asked questions