文件

T

wangsli和Claude Sonnet 5 c4025083af 落地任务复用治理规则与 worktree 对齐检查 [09-09-trellis-workflow-alignment]

2026-09-09 本地已验证完成、待交审的治理修复，一直未提交：

- 6 个 skill（trellis-before-dev/brainstorm/check/continue/finish-work/start）
  统一改为"先检查当前和直接相关既有任务，复用优先于新建"，取代原来"复杂任务
  先请求新建 task"的默认动作；新增 worktree/active-task 一致性校验步骤。
- project-governance.md 新增两节：Task Reuse（任务复用判据）、Active Task And
  Worktree Alignment（激活任务与实际执行 worktree 一致性检查，防止跨 worktree
  会话把上一个任务的 workflow-state 当成当前任务）。
- workflow.md 的 Request Triage / Parent-Child 章节、no_task 面包屑同步改写。

本地已过 task validate、check-trellis-governance.mjs、check-process-contract.mjs、
audit-docs.mjs、git diff --check；无业务代码改动。

Co-Authored-By: Claude Sonnet 5 <[email protected]>

2026-09-25 20:40:28 +08:00

3.0 KiB

原始文件 永久链接 Blame 文件历史

name, description

name	description
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.

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

Run python3 .trellis/scripts/task.py current --source from the worktree that will actually be edited. Compare with the intended approved task. If mismatched, use official task.py start <task> and read back current before resuming. A previous turn's workflow-state may refer to the old task. Follow project-governance.md → Active Task And Worktree Alignment; do not create a legacy global pointer.

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

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

3.0 KiB 原始文件 永久链接 Blame 文件历史