flower-trellis 0.3.1-beta.2 → 0.3.1-beta.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/enhancements/0.6/.agents/skills/trellis-route/SKILL.md +17 -7
- package/enhancements/0.6/.claude/skills/trellis-route/SKILL.md +17 -7
- package/enhancements/0.6/overrides/workflow-states/in_progress-inline.md +5 -3
- package/enhancements/0.6/overrides/workflow-states/in_progress.md +5 -5
- package/enhancements/0.6/overrides/workflow-states/no_task.md +5 -5
- package/enhancements/0.6/overrides/workflow.md +13 -14
- package/enhancements/MANIFEST.json +2 -2
- package/package.json +1 -1
|
@@ -5,14 +5,14 @@ description: |
|
|
|
5
5
|
Implement can route inline or subagent. Check defaults to check-all inline/subagent; lightweight
|
|
6
6
|
trellis-check is hidden and only available when the user explicitly requests "light check" / "轻量检查".
|
|
7
7
|
Invoked from Phase 2.1 target=implement and Phase 2.2 target=check/check-all of the routing-aware workflow.
|
|
8
|
-
|
|
8
|
+
Current-task repair/recheck loops reuse the latest valid route decision instead of prompting again.
|
|
9
9
|
Final re-checks return to Phase 2.2 before commit.
|
|
10
10
|
Skip in non-trellis projects (no .trellis/). Not for other subagents (trellis-research / trellis-debug).
|
|
11
11
|
---
|
|
12
12
|
|
|
13
13
|
# Trellis 路由器：implement / check 执行模式选择
|
|
14
14
|
|
|
15
|
-
主 agent 进入 Phase 2.1 实现路由或 Phase 2.2 检查路由时调用本 skill
|
|
15
|
+
主 agent 进入 Phase 2.1 实现路由或 Phase 2.2 检查路由时调用本 skill。当前任务内已有合法来源的最近 route 决策时，后续实现、修复、重检默认复用该决策；没有合法决策时才进入本 skill 或同编号 fallback。提交前确实需要最终复查时，回到 Phase 2.2 并复用当前任务的合法 check route，除非用户明确要求重选。
|
|
16
16
|
|
|
17
17
|
个人配置只写入 `.trellis/.route-prefs.tmp`。该文件匹配 `.trellis/.gitignore` 的 `*.tmp` 规则，属于开发者本地偏好，不纳入 git，也不影响其他开发者。
|
|
18
18
|
|
|
@@ -20,9 +20,11 @@ description: |
|
|
|
20
20
|
|
|
21
21
|
## Step 0: 识别目标与用户意图
|
|
22
22
|
|
|
23
|
-
个人 route 配置只决定“已获准执行后的模式”，不是开工授权。读取 `.trellis/.route-prefs.tmp` 前，必须确认当前 workflow 已允许进入对应 target：implement 需要任务已完成规划确认并处于 `in_progress`；check 用于 Phase 2.2
|
|
23
|
+
个人 route 配置只决定“已获准执行后的模式”，不是开工授权。读取 `.trellis/.route-prefs.tmp` 前，必须确认当前 workflow 已允许进入对应 target：implement 需要任务已完成规划确认并处于 `in_progress`；check 用于 Phase 2.2 检查执行，或用户明确要求最终复查 / 轻量检查。最终复查只有在 Phase 2.2 结果缺失、风险较高或用户明确要求复查时才回到 Phase 2.2；回到 Phase 2.2 后优先复用当前任务的合法 check route，除非用户明确要求重选/临时改/清除默认。如果仍在 planning、等待用户确认，或用户表达“等一下 / 我再想想”，停止，不读取个人配置。
|
|
24
24
|
|
|
25
|
-
|
|
25
|
+
合法 route 决策必须能追溯到 `trellis-route`、同编号 fallback 选项，或由本 skill 读取到的有效 `.trellis/.route-prefs.tmp` 配置。用户自然语言说过“inline/subagent”、compact summary、SessionStart 摘要、`codex-mode`、空 `.route-prefs.tmp`、旧单值偏好，都不能单独作为有效 route 决策。
|
|
26
|
+
|
|
27
|
+
当前任务内已有 target 匹配且来源合法的 route 决策时，后续实现、check 发现问题、用户指出刚检查过的实现有问题、修复后重检、提交前复查均默认复用最近 implement/check 路由；除非用户明确要求重选/临时改/清除默认，不再调用本 skill。
|
|
26
28
|
|
|
27
29
|
Codex inline mode 只表示主会话默认直接执行，不是 route 选项过滤器。即使当前上下文出现 `<codex-mode>inline...do not dispatch...</codex-mode>` 或 `workflow-state:in_progress-inline`，也不能推断“只能 inline”或跳过 subagent 选项；仍必须读取 `.trellis/.route-prefs.tmp`，或在无有效配置时展示正常 inline/subagent 选项。若本 skill 的紧邻路由决定是 subagent，本步骤允许主 agent dispatch 对应 implement/check sub-agent；禁止的是绕过 `trellis-route` 直接 dispatch。
|
|
28
30
|
|
|
@@ -224,6 +226,13 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
224
226
|
[来自个人 route 配置：`.trellis/.route-prefs.tmp` (<key>=<value>)。]
|
|
225
227
|
[说明：用户明确请求轻量检查，使用隐藏逃生口。]
|
|
226
228
|
|
|
229
|
+
route_decision:
|
|
230
|
+
target: <implement | check>
|
|
231
|
+
mode: <inline | subagent | check-all-inline | check-all-subagent | check-inline | check-subagent>
|
|
232
|
+
source: <trellis-route | route-prefs | numbered-fallback>
|
|
233
|
+
scope: task
|
|
234
|
+
task: <task.py current 的任务路径或 current>
|
|
235
|
+
|
|
227
236
|
接下来主 agent 应当：
|
|
228
237
|
- <路由表里对应的工具调用形式>
|
|
229
238
|
- [若 implement subagent 且 subagent_skip_compile=true：附加“跳过编译”prompt 段]
|
|
@@ -232,7 +241,7 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
232
241
|
- <要避免的工具调用>
|
|
233
242
|
```
|
|
234
243
|
|
|
235
|
-
中括号内行为条件性出现：仅命中个人配置时显示配置行；仅轻量 check 时显示隐藏逃生口说明；仅 implement subagent + skip_compile=true
|
|
244
|
+
中括号内行为条件性出现：仅命中个人配置时显示配置行；仅轻量 check 时显示隐藏逃生口说明；仅 implement subagent + skip_compile=true 时附加“跳过编译”段。`route_decision` 必须保留在回复、交接摘要或 compact summary 中；没有 `source` 的自然语言偏好不能被后续 agent 复用为 route。
|
|
236
245
|
|
|
237
246
|
---
|
|
238
247
|
|
|
@@ -241,7 +250,7 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
241
250
|
1. **个人配置私有**：`.trellis/.route-prefs.tmp` 是本地偏好，gitignored，不能进入提交计划。
|
|
242
251
|
2. **正常路由少打断**：命中个人配置时直接输出路由决定，不再重复询问。
|
|
243
252
|
3. **显式覆盖优先于配置**：用户要求临时改、重新选择或清除默认时，必须重新展示选项，不能让配置优先。
|
|
244
|
-
4.
|
|
253
|
+
4. **当前任务复用路由**：当前任务内已有合法来源的最近 implement/check 路由时，后续实现、修复、重检和复查默认沿用，不再次询问模式。
|
|
245
254
|
5. **check 默认全面检查**：普通 check 路由只展示 `check-all` inline/subagent，不推荐轻量 `trellis-check`。
|
|
246
255
|
6. **轻量 check 是隐藏逃生口**：只有用户明确请求 `light check` / `轻量检查` 时才可走轻量 `trellis-check`。
|
|
247
256
|
7. **决策与执行分离**：本 skill 只输出指令，下一轮由主 agent 调工具。
|
|
@@ -259,7 +268,8 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
259
268
|
- 没有用户明确请求时，把 check 降级到轻量 `trellis-check`。
|
|
260
269
|
- `AskUserQuestion` / `request_user_input` 不可用时，记录为 inline 或 subagent 路径并继续。
|
|
261
270
|
- 没有有效 check 配置、用户选择或最近本轮 check 路由决定时，自动执行 inline check。
|
|
262
|
-
-
|
|
271
|
+
- 没有 `source` 合法的 `route_decision`，就把“用户说过 inline/subagent”或 compact summary 当成已路由。
|
|
272
|
+
- check 发现问题后，把当前任务内已有合法 route 的修复/重检当成新的 route 边界再次询问模式。
|
|
263
273
|
- 给 check 任何模式附加“跳过编译”指令。
|
|
264
274
|
- 询问后忽视用户答案默认 subagent。
|
|
265
275
|
- 因 `<codex-mode>` 或 `in_progress-inline` 提到 inline，就自行把无配置 route 结果改成 inline 或隐藏 subagent 选项。
|
|
@@ -5,14 +5,14 @@ description: |
|
|
|
5
5
|
Implement can route inline or subagent. Check defaults to check-all inline/subagent; lightweight
|
|
6
6
|
trellis-check is hidden and only available when the user explicitly requests "light check" / "轻量检查".
|
|
7
7
|
Invoked from Phase 2.1 target=implement and Phase 2.2 target=check/check-all of the routing-aware workflow.
|
|
8
|
-
|
|
8
|
+
Current-task repair/recheck loops reuse the latest valid route decision instead of prompting again.
|
|
9
9
|
Final re-checks return to Phase 2.2 before commit.
|
|
10
10
|
Skip in non-trellis projects (no .trellis/). Not for other subagents (trellis-research / trellis-debug).
|
|
11
11
|
---
|
|
12
12
|
|
|
13
13
|
# Trellis 路由器：implement / check 执行模式选择
|
|
14
14
|
|
|
15
|
-
主 agent 进入 Phase 2.1 实现路由或 Phase 2.2 检查路由时调用本 skill
|
|
15
|
+
主 agent 进入 Phase 2.1 实现路由或 Phase 2.2 检查路由时调用本 skill。当前任务内已有合法来源的最近 route 决策时，后续实现、修复、重检默认复用该决策；没有合法决策时才进入本 skill 或同编号 fallback。提交前确实需要最终复查时，回到 Phase 2.2 并复用当前任务的合法 check route，除非用户明确要求重选。
|
|
16
16
|
|
|
17
17
|
个人配置只写入 `.trellis/.route-prefs.tmp`。该文件匹配 `.trellis/.gitignore` 的 `*.tmp` 规则，属于开发者本地偏好，不纳入 git，也不影响其他开发者。
|
|
18
18
|
|
|
@@ -20,9 +20,11 @@ description: |
|
|
|
20
20
|
|
|
21
21
|
## Step 0: 识别目标与用户意图
|
|
22
22
|
|
|
23
|
-
个人 route 配置只决定“已获准执行后的模式”，不是开工授权。读取 `.trellis/.route-prefs.tmp` 前，必须确认当前 workflow 已允许进入对应 target：implement 需要任务已完成规划确认并处于 `in_progress`；check 用于 Phase 2.2
|
|
23
|
+
个人 route 配置只决定“已获准执行后的模式”，不是开工授权。读取 `.trellis/.route-prefs.tmp` 前，必须确认当前 workflow 已允许进入对应 target：implement 需要任务已完成规划确认并处于 `in_progress`；check 用于 Phase 2.2 检查执行，或用户明确要求最终复查 / 轻量检查。最终复查只有在 Phase 2.2 结果缺失、风险较高或用户明确要求复查时才回到 Phase 2.2；回到 Phase 2.2 后优先复用当前任务的合法 check route，除非用户明确要求重选/临时改/清除默认。如果仍在 planning、等待用户确认，或用户表达“等一下 / 我再想想”，停止，不读取个人配置。
|
|
24
24
|
|
|
25
|
-
|
|
25
|
+
合法 route 决策必须能追溯到 `trellis-route`、同编号 fallback 选项，或由本 skill 读取到的有效 `.trellis/.route-prefs.tmp` 配置。用户自然语言说过“inline/subagent”、compact summary、SessionStart 摘要、`codex-mode`、空 `.route-prefs.tmp`、旧单值偏好，都不能单独作为有效 route 决策。
|
|
26
|
+
|
|
27
|
+
当前任务内已有 target 匹配且来源合法的 route 决策时，后续实现、check 发现问题、用户指出刚检查过的实现有问题、修复后重检、提交前复查均默认复用最近 implement/check 路由；除非用户明确要求重选/临时改/清除默认，不再调用本 skill。
|
|
26
28
|
|
|
27
29
|
Codex inline mode 只表示主会话默认直接执行，不是 route 选项过滤器。即使当前上下文出现 `<codex-mode>inline...do not dispatch...</codex-mode>` 或 `workflow-state:in_progress-inline`，也不能推断“只能 inline”或跳过 subagent 选项；仍必须读取 `.trellis/.route-prefs.tmp`，或在无有效配置时展示正常 inline/subagent 选项。若本 skill 的紧邻路由决定是 subagent，本步骤允许主 agent dispatch 对应 implement/check sub-agent；禁止的是绕过 `trellis-route` 直接 dispatch。
|
|
28
30
|
|
|
@@ -224,6 +226,13 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
224
226
|
[来自个人 route 配置：`.trellis/.route-prefs.tmp` (<key>=<value>)。]
|
|
225
227
|
[说明：用户明确请求轻量检查，使用隐藏逃生口。]
|
|
226
228
|
|
|
229
|
+
route_decision:
|
|
230
|
+
target: <implement | check>
|
|
231
|
+
mode: <inline | subagent | check-all-inline | check-all-subagent | check-inline | check-subagent>
|
|
232
|
+
source: <trellis-route | route-prefs | numbered-fallback>
|
|
233
|
+
scope: task
|
|
234
|
+
task: <task.py current 的任务路径或 current>
|
|
235
|
+
|
|
227
236
|
接下来主 agent 应当：
|
|
228
237
|
- <路由表里对应的工具调用形式>
|
|
229
238
|
- [若 implement subagent 且 subagent_skip_compile=true：附加“跳过编译”prompt 段]
|
|
@@ -232,7 +241,7 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
232
241
|
- <要避免的工具调用>
|
|
233
242
|
```
|
|
234
243
|
|
|
235
|
-
中括号内行为条件性出现：仅命中个人配置时显示配置行；仅轻量 check 时显示隐藏逃生口说明；仅 implement subagent + skip_compile=true
|
|
244
|
+
中括号内行为条件性出现：仅命中个人配置时显示配置行；仅轻量 check 时显示隐藏逃生口说明；仅 implement subagent + skip_compile=true 时附加“跳过编译”段。`route_decision` 必须保留在回复、交接摘要或 compact summary 中；没有 `source` 的自然语言偏好不能被后续 agent 复用为 route。
|
|
236
245
|
|
|
237
246
|
---
|
|
238
247
|
|
|
@@ -241,7 +250,7 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
241
250
|
1. **个人配置私有**：`.trellis/.route-prefs.tmp` 是本地偏好，gitignored，不能进入提交计划。
|
|
242
251
|
2. **正常路由少打断**：命中个人配置时直接输出路由决定，不再重复询问。
|
|
243
252
|
3. **显式覆盖优先于配置**：用户要求临时改、重新选择或清除默认时，必须重新展示选项，不能让配置优先。
|
|
244
|
-
4.
|
|
253
|
+
4. **当前任务复用路由**：当前任务内已有合法来源的最近 implement/check 路由时，后续实现、修复、重检和复查默认沿用，不再次询问模式。
|
|
245
254
|
5. **check 默认全面检查**：普通 check 路由只展示 `check-all` inline/subagent，不推荐轻量 `trellis-check`。
|
|
246
255
|
6. **轻量 check 是隐藏逃生口**：只有用户明确请求 `light check` / `轻量检查` 时才可走轻量 `trellis-check`。
|
|
247
256
|
7. **决策与执行分离**：本 skill 只输出指令，下一轮由主 agent 调工具。
|
|
@@ -259,7 +268,8 @@ OLD_CHECK=$(awk -F= '$1=="check"{print $2}' "$PREF_FILE" 2>/dev/null | tail -n 1
|
|
|
259
268
|
- 没有用户明确请求时，把 check 降级到轻量 `trellis-check`。
|
|
260
269
|
- `AskUserQuestion` / `request_user_input` 不可用时，记录为 inline 或 subagent 路径并继续。
|
|
261
270
|
- 没有有效 check 配置、用户选择或最近本轮 check 路由决定时，自动执行 inline check。
|
|
262
|
-
-
|
|
271
|
+
- 没有 `source` 合法的 `route_decision`，就把“用户说过 inline/subagent”或 compact summary 当成已路由。
|
|
272
|
+
- check 发现问题后，把当前任务内已有合法 route 的修复/重检当成新的 route 边界再次询问模式。
|
|
263
273
|
- 给 check 任何模式附加“跳过编译”指令。
|
|
264
274
|
- 询问后忽视用户答案默认 subagent。
|
|
265
275
|
- 因 `<codex-mode>` 或 `in_progress-inline` 提到 inline，就自行把无配置 route 结果改成 inline 或隐藏 subagent 选项。
|
|
@@ -1,8 +1,10 @@
|
|
|
1
1
|
<!-- BEGIN skill-garden workflow-state in_progress_inline v0.6 -->
|
|
2
2
|
HIGHEST PRIORITY SKILL-GARDEN STATE GUARD (in_progress-inline):
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
3
|
+
This state block is a breadcrumb; the top-level skill-garden hub is the source of truth for route details.
|
|
4
|
+
Inline workflow-state is not an inline route decision. At Phase 2.1/2.2, reuse a valid current-task `route_decision` for the target when it exists; otherwise run `trellis-route(implement|check)` or ask the numbered fallback choices and wait.
|
|
5
|
+
A valid route decision must come from `trellis-route`, `numbered-fallback`, or `route-prefs` read by `trellis-route`; prose, compact/SessionStart summaries, `codex-mode`, empty prefs, and old single-value prefs are not enough.
|
|
6
|
+
Reuse the valid current-task route through later implementation, repair, recheck, and final re-check; reroute only on explicit reselect/override/use-X-this-time/clear-default or when no valid target decision exists.
|
|
7
|
+
Do not default to inline just because this state is inline or the helper is unavailable. Dispatch subagents only when the valid route decision selected subagent; otherwise execute inline in the main session.
|
|
6
8
|
After `trellis-check` / `trellis-check-all`, stop and report; point the user to Phase 3.4 `trellis-push` (or commit-only when needed). Do not run `/trellis:finish-work` unless the user explicitly asks after Phase 3.4 is complete.
|
|
7
9
|
This guard overrides any lower `Flow: ... -> /trellis:finish-work` line in this state block.
|
|
8
10
|
At Phase 3.4, code commit/push still goes through `trellis-push` (commit-only for commit-without-push); never bare `git commit`/`git push` on code (hub: Code Commit Confirmation Gate).
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
<!-- BEGIN skill-garden workflow-state in_progress v0.6 -->
|
|
2
2
|
HIGHEST PRIORITY SKILL-GARDEN STATE GUARD (in_progress):
|
|
3
|
-
|
|
4
|
-
Phase 2.2
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
If the helper is unavailable, ask numbered route choices and wait
|
|
3
|
+
This state block is a breadcrumb; the top-level skill-garden hub is the source of truth for route details.
|
|
4
|
+
At Phase 2.1/2.2, use the valid current-task `route_decision` for the target when it exists; otherwise run `trellis-route(implement|check)` or ask the numbered fallback choices and wait.
|
|
5
|
+
A valid route decision must come from `trellis-route`, `numbered-fallback`, or `route-prefs` read by `trellis-route`; prose, compact/SessionStart summaries, `codex-mode`, empty prefs, and old single-value prefs are not enough.
|
|
6
|
+
Reuse the valid current-task route through later implementation, repair, recheck, and final re-check; reroute only on explicit reselect/override/use-X-this-time/clear-default or when no valid target decision exists.
|
|
7
|
+
Do not spawn `trellis-implement` or `trellis-check*` unless the valid route decision selected subagent. If the helper is unavailable, do not default to inline; ask the numbered route choices and wait.
|
|
8
8
|
After `trellis-check` / `trellis-check-all`, stop and report; point the user to Phase 3.4 `trellis-push` (or commit-only when needed). Do not run `/trellis:finish-work` unless the user explicitly asks after Phase 3.4 is complete.
|
|
9
9
|
This guard overrides any lower `Flow: ... -> /trellis:finish-work` line in this state block.
|
|
10
10
|
At Phase 3.4, code commit/push goes through `trellis-push` (commit-only mode for commit-without-push); never bare `git commit`/`git push` on code (hub: Code Commit Confirmation Gate).
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
<!-- BEGIN skill-garden workflow-state no_task v0.6 -->
|
|
2
2
|
HIGHEST PRIORITY SKILL-GARDEN STATE GUARD (no_task):
|
|
3
|
-
Creating
|
|
4
|
-
After PRD ready and task started, next implementation action
|
|
5
|
-
If no active task exists, scan `.trellis/tasks/*/task.json` once per session for in-progress tasks with `last_push_snapshot`; surface completed_steps + next_step and suggest rebinding the active task before resuming.
|
|
6
|
-
Do NOT
|
|
7
|
-
If the turn is a meta edit to Trellis itself
|
|
3
|
+
Creating or resuming a task is not implementation permission.
|
|
4
|
+
After PRD is ready and the task is started, the next implementation action is Phase 2.1 `trellis-route(implement)` unless a valid current-task implement route decision already exists.
|
|
5
|
+
If no active task exists, scan `.trellis/tasks/*/task.json` once per session for in-progress tasks with `last_push_snapshot`; surface `completed_steps` + `next_step` and suggest rebinding the active task before resuming.
|
|
6
|
+
Do NOT call the harness built-in plan mode (`EnterPlanMode` / `ExitPlanMode`) for Trellis planning. It is not a substitute for Trellis task-creation consent, Trellis planning, or the route gate. For complex work, classify the turn, ask for task-creation consent, then use `trellis-brainstorm`.
|
|
7
|
+
If the turn is a meta edit to Trellis itself and Trellis tracking would be overkill, say so and ask to skip Trellis; never silently swap built-in plan mode in for the consent gate.
|
|
8
8
|
<!-- END skill-garden workflow-state no_task v0.6 -->
|
|
@@ -6,38 +6,37 @@
|
|
|
6
6
|
|
|
7
7
|
**Priority**: This hub overrides any conflicting Trellis workflow, skill, or command text for the scoped behaviors below.
|
|
8
8
|
|
|
9
|
-
**Scope**: Phase 2.1 implement routing, Phase 2.2 check/check-all routing,
|
|
9
|
+
**Scope**: Phase 2.1 implement routing, Phase 2.2 check/check-all routing, current-task route reuse, post-check stop, Phase 3.4 trellis-push, explicit Phase 3.5 finish-work bookkeeping, and push-progress recovery. State blocks should keep one short skill-garden sentinel; long-form rules live here.
|
|
10
10
|
|
|
11
11
|
**Mechanical rule**: use this hub as the source of truth. Do not add separate top-level skill-garden override sections or multiple skill-garden sentinels inside the same `workflow-state:*` block.
|
|
12
12
|
|
|
13
13
|
#### Routing Gate
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
A route decision is valid only when it is a current-task decision for the requested target (`implement` or `check`) and its structured `route_decision.source` is one of: `trellis-route`, `numbered-fallback`, or `route-prefs`.
|
|
16
16
|
|
|
17
|
-
Phase 2.
|
|
17
|
+
`route-prefs` is valid only when read by `trellis-route` after the workflow has already reached Phase 2.1 or Phase 2.2. The gitignored personal preference file `.trellis/.route-prefs.tmp` is developer-local execution-mode state; it must never be staged or committed, and it is never authorization to start work.
|
|
18
18
|
|
|
19
|
-
|
|
19
|
+
Before Phase 2.1 implement or Phase 2.2 check/check-all execution, use this order:
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
1. Reuse the valid current-task route decision for the requested target when one exists.
|
|
22
|
+
2. If the user explicitly asks to reselect, override, use another mode this time, or clear the default, ignore stored preferences for this decision and rerun `trellis-route` / the numbered fallback.
|
|
23
|
+
3. If no valid current-task decision exists for the target, run `trellis-route(target=implement|check)`. If the helper cannot ask through `AskUserQuestion` / `request_user_input`, ask the same numbered choices in normal chat and wait.
|
|
22
24
|
|
|
23
|
-
|
|
25
|
+
These are not valid route decisions by themselves: user prose such as "inline" or "I choose inline"; compact summaries; SessionStart summaries; `codex-mode`; empty `.trellis/.route-prefs.tmp`; old single-value prefs; and any remembered or summarized prior choice that does not carry a valid structured `route_decision`.
|
|
24
26
|
|
|
25
|
-
|
|
27
|
+
When a valid current-task implement/check decision exists, reuse it for later implementation in the same task, check failures, user-reported issues in the just-checked work, repair, recheck, and final re-check. Do not rerun `trellis-route` merely because check failed, code was repaired, or a final re-check is needed.
|
|
26
28
|
|
|
27
|
-
|
|
29
|
+
Phase 2.2 is the normal check execution point. Normal check routing returns only `trellis-check-all` paths: check-all inline or check-all subagent. Lightweight `trellis-check` is a hidden escape hatch only when the user explicitly asks for `light check` / `轻量检查`; it is not shown in normal check options.
|
|
28
30
|
|
|
29
|
-
|
|
31
|
+
`trellis-route` returns 2 normal modes for `target=implement` (inline/subagent) and 2 normal modes for `target=check` (check-all inline/check-all subagent).
|
|
32
|
+
Dispatch `trellis-implement`, `trellis-check`, or `trellis-check-all` only when the valid route decision selected subagent. If the valid route decision selected inline, execute inline in the main session.
|
|
30
33
|
|
|
31
34
|
Before invoking the skill, never:
|
|
32
35
|
- write pre-questions ("ready to start? / shall I proceed?")
|
|
33
36
|
- state "I lean towards X" or preview the inline/subagent options
|
|
34
37
|
- surface route options ahead of time
|
|
35
38
|
|
|
36
|
-
At
|
|
37
|
-
|
|
38
|
-
If the user says "temporary override", "reselect", "use X this time", "clear route default", or equivalent, the personal preference file must not take priority. `trellis-route` must show the override options again and let the user choose whether the choice is one-time, saved as the new default, or clears the default.
|
|
39
|
-
|
|
40
|
-
For normal check routing, default to `trellis-check-all` paths. Do not route to lightweight `trellis-check` unless the user explicitly asks for the hidden light-check escape hatch.
|
|
39
|
+
At Phase 2.1/2.2 boundaries, do not ask meta continuation questions. Either reuse the valid current-task route decision for the target, or obtain a new valid decision through `trellis-route` / numbered fallback.
|
|
41
40
|
|
|
42
41
|
#### Post-Check Stop Gate
|
|
43
42
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
|
-
"syncedAt": "2026-06-
|
|
2
|
+
"syncedAt": "2026-06-25T16:01:21.350Z",
|
|
3
3
|
"syncedFrom": "vendor/skill-garden/.trellis",
|
|
4
|
-
"sourceCommit": "
|
|
4
|
+
"sourceCommit": "97cb5d7e8bfda2c6504790e10cc2bf08e2f2d8fb",
|
|
5
5
|
"variants": {
|
|
6
6
|
"old": {
|
|
7
7
|
"claudeSkills": [],
|