Offer helpers (subagents) in Plan and Revise Plan

AI Assisted
This commit is contained in:
jparkerweb committed 2026-10-25 22:07:44 -07:00
1 parent a2b43d1188
commit b99a1a701f
16 files changed
+70 -28

No files matched your search

+1 -1
View File
@@ -4,7 +4,7 @@ Part of the web console contract (`console.md`). Read when a `Subagents:` block
arrives, or when your workflow notes say to report helpers.
On the skills that offer it (`implement`, `implement-review`, `quick-task`,
`review`, `pathfinder`), the person can turn **helpers** (subagents) on or off
`review`, `pathfinder`, `plan`, `revise-plan`), the person can turn **helpers** (subagents) on or off
from the top bar's Subagents button. Their pick is saved per project and per
skill, on until switched off, and reaches you as a standing instruction, only when it
changes.
+5
View File
@@ -15,3 +15,8 @@ Workflow notes for `plan`, part of the web console contract (`console.md`).
browser user is not watching.
- The Large checkpoint finish is a pause: a headline starting "Paused", no
`dashboard`, and `stop` at once.
- Plan offers the Subagents switch. A `Subagents:` block may arrive on `open`
output or a `wait` / `chat` pickup: follow `console-subagents.md` and the
skill's Helpers section, and report each helper as `helpers`. Post a helper
as `done` or `failed` before the sign-off it feeds, and every one before a
`finish`. Questions, sign-offs and the PLAN-DRAFT stay with you.
+8
View File
@@ -16,3 +16,11 @@ offers to execute or implement.** Pass `--spec specs/<feature>` to `open`, or
post `specDir` once you know it. The finish command is
`/plan2code-3-implement specs/<feature>/overview.md`; an abort's is
`/plan2code-1b-revise-plan specs/<feature>/overview.md`.
Revision offers the Subagents switch. A `Subagents:` block may arrive on
`open` output or a `wait` / `chat` pickup: follow `console-subagents.md` and
the skill's Helpers section, and report each helper as `helpers`. Lookup
helpers report back before the Step 2 review item goes up; phase-file helpers
report back before the Step 4 check. Every gate stays with you, and a helper's
`title`, `ask` and `result` follow the same rule as every label: nothing
offers to execute or implement.
+3 -3
View File
@@ -2061,9 +2061,9 @@
<section class="help-panel" data-tab="subagents">
<h3>Helpers (subagents)</h3>
<p>
On a build, a review and Pathfinder, Plan2Code can hand independent
pieces of work to helpers (subagents) while it keeps the conversation
with you. The <strong>Subagents</strong> button in the top bar, after
On a build, a review, Pathfinder, Plan and Revise plan, Plan2Code
can hand independent pieces of work to helpers (subagents) while it
keeps the conversation with you. The <strong>Subagents</strong> button in the top bar, after
Stop session, is lit while helpers are on.
</p>
<h4>The switch</h4>
+2 -2
View File
@@ -135,7 +135,7 @@ export const SKILLS = Object.freeze([
pose: "plan",
builds: false, phased: false, metered: true, templates: true,
weight: 2, started: "Plan started", ran: "Plan drafted", resume: null,
subagents: null,
subagents: "Use helpers for research and recon beside the conversation: reading the files and references the person points you to, mapping separate areas of the codebase in Phase 2, and gathering evidence on each open tech choice in Phase 4. In Phase 7, one fresh helper may cross-check the PLAN-DRAFT against the PLAN-CONVERSATION; confirm each gap it finds yourself. Keep every question, decision and sign-off, and the writing of the PLAN-DRAFT, with you. Recon and lookups at light strength, the cross-check at standard.",
states: ["none", "unrecognized", "diagnosed", "mapped", "planned"], marksNext: true,
greyed: {
default: "The plan is written. Revise it instead if it moved.",
@@ -160,7 +160,7 @@ export const SKILLS = Object.freeze([
pose: "plan",
builds: false, phased: false, metered: true, templates: false,
weight: 1, started: "Revise plan started", ran: "Plan revised", resume: "overview",
subagents: null,
subagents: "Use helpers for lookups at Steps 1 and 2: reading the code behind the affected tasks, and behind the completed tasks the change could undo. After the Step 2 approval, when the revision touches 3 or more phase files, one helper per phase file may apply the edits the approved plan spells out for it, editing under specs/ only. Keep the questions, the approval, overview.md, task numbering across phases and the consistency check with you, and re-read every file a helper edited. Lookups at light strength, low effort; phase-file edits at light, medium.",
states: ["documented", "building", "built"],
greyed: { default: "Needs a spec that is already written up" },
card: {