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

+10
View File
@@ -43,6 +43,16 @@ Check if `./AGENTS.md` exists:
- NEVER write implementation code; keep responses conceptual, detailed specs belong in the final PLAN-DRAFT only
- If no file access, output content in code blocks with file path headers
## Helpers
When your tool can start helpers (subagents) and they are not switched off for this run (on the web console a `Subagents:` block says which, console-subagents.md), hand them the work whose answer does not hang on the conversation still to come:
- **Phase 1:** reading each file, folder or reference the person names, and the domain research; one source per helper.
- **Phase 2:** mapping separate areas of the codebase, one area per helper (structure, one component's real behavior, one integration point). Each returns facts with `file:line`, never a design.
- **Phase 4:** evidence on each open tech choice (current version, upkeep, fit with the stack); the recommendation stays yours.
- **Phase 7, step 3:** one fresh helper, briefed only with the PLAN-CONVERSATION and the PLAN-DRAFT, lists the gaps between them; confirm each yourself before you add it.
Keep with you: every question, confidence score, decision and sign-off, Phases 3, 5 and 6, and the writing of the PLAN-DRAFT (its sections cross-reference each other and rest on decisions only this session holds). Pick each helper's strength and effort from references/helper-strength.md. Every helper reports back before that phase's sign-off. No helpers? Do the same work yourself.
---
### Check for Existing Progress
+8
View File
@@ -31,6 +31,14 @@ The FIRST thing you do, before anything else in this file — before Step 1, bef
- `node "<S>/specs.mjs" status <spec>`: phases, task counts by marker, `checks`, `pending`.
- `node "<S>/specs.mjs" mark <spec> --phase <N> --to open`: re-open a completed phase in overview.md.
## Helpers
When your tool can start helpers (subagents) and they are not switched off for this run (on the web console a `Subagents:` block says which, console-subagents.md):
- **Steps 1 and 2, read-only lookups:** the code behind each affected task (its functions and files as they stand now, for Step 3's code references), and the code behind completed tasks the change could undo, so **Completed Work at Risk** rests on evidence. One area per helper.
- **Step 3, only after approval, when the revision touches 3 or more phase files:** one helper per `phase-X.md` whose edits the approved plan spells out. Run `mark` for every re-opened phase before starting them, since it rewrites that phase file too. Its brief carries that file's approved changes, the `🔄 REVISED` / `🆕 ADDED` formats, and the rule that it edits that one file under `specs/` and nothing else.
Keep with you: every question, the Step 2 approval, overview.md (`mark`, Revision History), the waiting brief's line, dependencies and numbering across phases, and Steps 4 to 6. Re-read every file a helper edited against the approved plan before Step 4. Strength and effort per references/helper-strength.md. No helpers? Do the same work yourself.
## Required Context
Find the spec with `specs.mjs list`, then request these files if not provided:
+4 -2
View File
@@ -1,5 +1,5 @@
# Helper Strength
> Shared by the skills that start helpers (subagents): Pathfinder, Quick Task, Implement, Implement + Review and Review. Read it when you first start a helper in a session. Never invoked as a skill.
> Shared by the skills that start helpers (subagents): Pathfinder, Plan, Revise Plan, Quick Task, Implement, Implement + Review and Review. Read it when you first start a helper in a session. Never invoked as a skill.
## The words
@@ -17,10 +17,12 @@ Never write a model or vendor name in a brief, a report or a file, and never inv
| Helper's job | Strength | Effort |
|---|---|---|
| Lookups, reading code, checking docs, recon | light | low |
| Revise Plan edit to one phase file, spelled out in the approved plan | light | medium |
| Build task in 1 or 2 files, with the change spelled out in the task | light | medium |
| Build task across several files, integration work, debugging | standard | medium |
| Build task needing a design decision the spec leaves open | strongest (or keep it yourself) | high |
| Pathfinder research question, sketch | standard | medium |
| Plan's PLAN-DRAFT cross-check against the conversation | standard | medium |
| Review analysis, focused scope | standard | high |
| Review analysis, branch or full scope, or touching security, auth or data | strongest | high |
@@ -28,7 +30,7 @@ Decide from these signals: how many files the job touches, whether the task spel
## Floor and escalation
- A review helper never runs below `standard`.
- A review helper, or Plan's PLAN-DRAFT cross-check, never runs below `standard`.
- A retry, after a helper fails or after its work fails the phase's tests, goes one strength up and at least `medium` effort. Never retry at the same strength.
- When a `strongest` helper fails, its task comes back to you.
+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: {