Let helpers run at a strength matched to their job, chosen in the Subagents dialog

AI Assisted
This commit is contained in:
jparkerweb committed 2026-10-25 15:33:35 -07:00
1 parent 5f91fb665f
commit 1d146cce6f
23 files changed
+482 -73

No files matched your search

+20 -4
View File
@@ -22,11 +22,21 @@ Subagents: on (revision 2) — a console setting, not typed by the person.
Hand independent work to helpers if your tools allow it; otherwise carry on alone.
Report each helper on the page (console-subagents.md); questions for the person stay with you.
If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.
Hand independent tasks in a phase to helpers: tasks that touch different files and do not depend on each other. Keep tasks that share files, the phase's tests and the sign-off with you.
Match each helper's strength and effort to its job, as helper-strength.md says; when your tools cannot set them, start the helper without them.
Hand independent tasks in a phase to helpers: tasks that touch different files and do not depend on each other. Keep tasks that share files, the phase's tests and the sign-off with you. Pick each helper's strength and effort from helper-strength.md's table: light for a 1-2 file task the task file spells out, standard for multi-file or debugging work.
Helper strength: balanced (the table in helper-strength.md as written).
At most 3 helpers at once.
```
beside `"subagents": { "state": "on", "revision": 2, "max": 3, "instruction": "…" }`.
beside `"subagents": { "state": "on", "revision": 2, "max": 3, "instruction": "…", "strength": "balanced" }`.
The `Helper strength:` line carries the person's profile, and replaces the
Balanced default when they pick another:
- `balanced`: the table in `helper-strength.md` as written (the default).
- `thrifty`: one step lighter in strength and effort; reviews never below standard.
- `best`: strongest and high effort for every helper except lookups, which stay light.
- `session`: set no model or effort on any helper.
An edit while on arrives as `Subagents: on (revision 3, replaces revision 2) — …`
with the whole block again; switching off arrives as one line:
`Subagents: off (revision 4) — don't start new helpers for the rest of this session.`
@@ -39,6 +49,9 @@ card, and it is never recorded under `specs/`.
- **On:** hand independent work to helpers if your tools allow it, at most
`max` at once, following the instruction lines. `max` is advisory: your
harness's own limit still applies.
- **Strength:** start each helper at the strength and effort
`helper-strength.md` (in the skill's `references/`) gives for its job,
following its fallback order. Read it when you first start a helper.
- **A higher revision replaces a lower one.** Follow the latest block only.
- **Off:** start no new helpers for the rest of the session. Let running ones
finish and report them.
@@ -56,13 +69,16 @@ page never hears from a helper directly:
```jsonc
{ "helpers": [
{ "id": "h1", "title": "Read the store helpers", "ask": "Find every caller of readSubagentSetting.", "state": "running" },
{ "id": "h2", "title": "Check the tests", "ask": "Run the subagents tests and report failures.", "state": "done", "result": "All 9 pass." }
{ "id": "h2", "title": "Check the tests", "ask": "Run the subagents tests and report failures.", "state": "done", "result": "All 9 pass.", "strength": "light", "effort": "low" }
] }
```
- `id` (non-empty), `title` (at most 80 characters), `ask` (at most 400) and
`state` (`running`, `done` or `failed`) are required; `result` (at most 200)
is the one line you add once a helper ends. Anything else is exit `3`, and
is the one line you add once a helper ends. `strength` (`light`,
`standard`, `strongest` or `inherit`) and `effort` (`low`, `medium` or
`high`) are optional: report what the helper actually ran with, and
`inherit` when its strength could not be set. Anything else is exit `3`, and
the house rules on completion markers and metric-like words cover `title`,
`ask` and `result`.
- Merged by `id`: post a helper again with its new `state` and `result` and it