落地任务复用治理规则与 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]>
这个提交包含在:
@@ -5,6 +5,8 @@ description: "Close out an explicitly requested session or completed task with t
|
||||
|
||||
# Finish Work
|
||||
|
||||
Before closeout, match the active task to the actual execution worktree and record phase, verification, remaining acceptance and who/what is pending. Follow project-governance.md → Active Task And Worktree Alignment. Official `task.py finish` only clears the session pointer; it is not task completion or archive. Do not silently switch to another business task or treat isolated-worktree notes as integrated changes.
|
||||
|
||||
1. Compare this task with its acceptance criteria and latest validation evidence. Do not scan unrelated active tasks for cleanup.
|
||||
2. Report implementation, tests, independent review and deployment separately. A completed stage can leave the overall task active; unresolved acceptance must not be checked off.
|
||||
3. Update existing task notes with concise, redacted results and remaining steps. Record a journal only when useful or requested; avoid duplicating stable facts across documents.
|
||||
|
||||
在新工单中引用
屏蔽一个用户