文件

T

更新Trellis适配、任务归属与归档失败恢复，精简技能入口和知识读取规则。
保留权限、证据、事务及独立复核合同；纳入对应任务及已完成复核记录。
仅本地提交，不启用新平台适配，不推送或部署。

2026-09-19 13:10:06 +08:00

name, description

name	description
trellis-continue	Resume an existing Trellis task after a pause or handoff; locate its current phase and next unfinished step.

Continue Current Task

Reuse fresh task context; otherwise run python3 .trellis/scripts/task.py current --source and read that task's task.json. If the pointer is missing, inspect directly related tasks before creating anything. Never infer another session's ownership. Use full get_context.py only for a broader session-state question.
Read the current PRD and the latest status/unfinished steps in implement.md; read the applicable design decisions when needed. Preserve constraints and approvals from the handoff. Do not reload unchanged history, unrelated journals or every spec.
Load the Phase Index only when routing is unclear: python3 .trellis/scripts/get_context.py --mode phase. Load the next step with --mode phase --step <X.X> --platform codex; the workflow owns phase rules, so do not maintain a duplicate routing table here.
Complete missing planning decisions before implementation. An existing PRD is not approval; recorded approval for unchanged scope permits task.py start and continued execution without another confirmation. Complex tasks need PRD, design and implementation notes; inline mode permits empty context manifests.
Use trellis-before-dev for implementation and trellis-check for verification. Continue through the approved scope and relevant checks; leave independent review explicitly pending if unavailable. Commit, push, archive, deployment and real-data operations retain their separate authorization boundaries.