agentleFS
Sign inStart free
wuwei-crgwuwei-crg/LXB-Framework/.agents/skills/trellis-continue/SKILL.md

trellis-continue

Skill301 starsChanged 6 months 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, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use trellis-channel, trellis-session-insight and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wayfarer35Skill

    trellis-channel

    Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.

    Also in 14 projects that use this

  • wayfarer35Skill

    trellis-session-insight

    Reach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.

    Also in 14 projects that use this

  • +1 more from wayfarer35

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 16 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
  1. Very specific:

    Run steps in order within a phase — [required] steps must not be skipped

    line 42
  2. Very specific:

    Follow the loaded instructions.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 16 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.py

Confirms: current task, git state, recent commits.

Step 2: Load the Phase Index

python ./.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:

  • status=planning + no prd.md → 1.1 (load trellis-brainstorm)
  • status=planning + prd.md exists + implement.jsonl not curated (only the seed _example row) → 1.3
  • status=planning + prd.md + curated implement.jsonl → 1.4 (run task.py start to enter Phase 2)
  • status=in_progress + implementation not started → 2.1
  • status=in_progress + implementation done, not yet checked → 2.2
  • status=in_progress + check passed → 3.1
  • status=completed (rare; usually archived immediately) → archive flow

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

  1. Run steps in order within a phase — [required] steps must not be skipped
  2. [once] steps are already done if the output exists (e.g., prd.md for 1.1; implement.jsonl with curated entries for 1.3) — skip them
  3. 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 codex

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

Reference

Full workflow, skill routing table, and the DO-NOT-skip table live in .trellis/workflow.md. This command is only an entry point — the canonical guidance is there.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free