CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/trellis-continue/SKILL.md
SKILL.md
Quality
Evals
Security

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

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.

Repository
mindfold-ai/Trellis
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.