agentleFS
Sign inStart free
tmdytmdy/CodeDeck/.agents/skills/source-command-trellis-continue/SKILL.md

source-command-trellis-continue

Skill2 starsChanged 26 days agoMITView on GitHub

Migrated source command `trellis-continue`

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user asks to run the migrated source command trellis-continue.

    line 8
  2. Very specific:

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

    line 49
  3. Very specific:

    Follow the loaded instructions.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

source-command-trellis-continue

Use this skill when the user asks to run the migrated source command trellis-continue.

Command Template

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. 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):

  1. Run steps in order within a phase — [required] steps must not be skipped
  2. [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 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 and detailed phase steps 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