mcpField
T
trellis-continue

trellis-continue

github.com/mindfold-aiAgent workflows15.0k144 installsUpdated 4w ago
Repository

About trellis-continue

trellis-continue is a Trellis skill that identifies where to resume the active task in the development workflow. It uses task status and artifact presence to route work to the appropriate phase and step, without approving implementation.

Key features

  1. 01Load task context and Git state
  2. 02Display the workflow phase index
  3. 03Route by status and available artifacts
  4. 04Load instructions for the selected step

Use cases

  1. 01Resume a task in progress
  2. 02Determine the next step after planning
  3. 03Find the appropriate workflow step from task artifacts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mindfold-ai/trellis --skill trellis-continue

After installing, type/trellis-continuein Claude Code to confirm it loaded.

Details

From the project README

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 (empty, or only a legacy _example placeholder 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.

Comments

Markdown supported