trellis-continue
Skill2 starsChanged 26 days agoMITView on GitHub
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.
16 other projects use a version of this, 15 of them edited.
Adopted by
Most recently taken up by
- phoben/agent-skillsedited, first seen Nov 8, 2026
- vibex-ai/vibexedited, first seen Nov 8, 2026
- mipawn/cc-useedited, first seen Nov 1, 2026
- zhexin233-ui/easytoagentsedited, first seen Oct 11, 2026
- wuwei-crg/LXB-Frameworkedited, first seen Oct 8, 2026
- mumu-0922/GankAIGCedited, first seen Oct 8, 2026
Other versions16 projects use a version of this.
Word for word · 1
- CharTyr/STS2-Agent★ 357100% same
Edited · 15
- mindfold-ai/Trellis★ 15k94% same
- EcoPasteHub/EcoPaste★ 7.5k97% same
- QiaoKes/fntv-electron★ 1.3k97% same
- mumu-0922/GankAIGC★ 39696% same
- wuwei-crg/LXB-Framework★ 30179% same
- fy-agent/fyagent★ 21897% same
- vibex-ai/vibex★ 7097% same
- mipawn/cc-use★ 994% same
- xhl592576605/agent-skills-mesh★ 897% same
- ofoxai/skills★ 274% same
5 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- source-command-trellis-continueSkill
- source-command-trellis-finish-workSkill
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-break-loopSkill
- trellis-channelSkill
- trellis-checkSkill
- trellis-finish-workSkill
- trellis-metaSkill
- trellis-session-insightSkill
- trellis-spec-bootstrapSkill
- trellis-startSkill
- trellis-update-specSkill
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-break-loopSkill
- trellis-channelSkill
- trellis-checkSkill
- trellis-metaSkill
- trellis-session-insightSkill
- trellis-spec-bootstrapSkill
- trellis-update-specSkill
- delegate-with-codedeckSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 43
Run steps in order within a phase — [required] steps must not be skipped
- Very specific: line 55
Follow the loaded instructions.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
python ./.trellis/scripts/get_context.pyConfirms: current task, git state, recent commits.
Step 2: Load the Phase Index
python ./.trellis/scripts/get_context.py --mode phaseShows 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+ noprd.md→ 1.1 (loadtrellis-brainstorm)status=planning+prd.mdonly → decide whether the task is lightweight or complex. Lightweight can move to 1.4 review; complex returns to 1.1 to adddesign.md+implement.md.status=planning+ complex artifacts complete + sub-agent jsonl not curated (only the seed_examplerow) → 1.3status=planning+ required artifacts complete + required jsonl curated or inline mode → 1.4 (ask for start review; only runtask.py startafter user confirms)status=in_progress+ implementation not started → 2.1status=in_progress+ implementation done, not yet checked → 2.2status=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.mdalone can be enough only for lightweight tasks; complex tasks also needdesign.mdandimplement.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:
python ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform codexFollow 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

