Offer the Subagents switch on five more skills

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-02 13:13:31 -08:00
1 parent ef4d86258b
commit d7abcd2ac6
16 files changed
+99 -30

No files matched your search

+7
View File
@@ -29,6 +29,13 @@ The FIRST thing you do, before anything else — before Auto-Discovery: ask **we
- Do NOT implement - documentation only
- If no filesystem access, output 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):
- **Lookups while you write:** the files, seams and sizes behind the work a task names, so the details a builder needs rest on the real code; one lookup per helper, each returning facts with `file:line`.
Keep with you: the breakdown, the task writing and every question. Strength and effort per references/helper-strength.md. No helpers? Do the same work yourself.
## Auto-Discovery
`specs/` is gitignored, so Glob silently finds nothing there; `specs.mjs` reads it directly.
+7
View File
@@ -46,6 +46,13 @@ Check if `./AGENTS.md` exists:
- **No git writes.** Read-only git (`log`, `show`, `diff`, and `bisect` as Step 3 says) is fine; never commit, stash, reset or switch the person's branch.
- Plain words. Name the files and functions; skip jargon the person did not use.
## 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):
- **Step 3, read-only lookups:** the code path a suspect change touches, a suspect function's callers and the docs behind the failing behavior; one suspect per helper, each returning facts with `file:line`, never a verdict.
Keep with you: the reproduction, any bisect, the cause judgment and every question. Strength and effort per references/helper-strength.md. No helpers? Do the same work yourself.
## Process
### Step 1: The Bug
+7
View File
@@ -31,6 +31,13 @@ The FIRST thing you do, before anything else in this file — before the Awarene
Before making any updates, orient yourself to current project state: read `AGENTS.md` and `README.md`, list `src/` directory, run `ls specs/` (not Glob — gitignored) to read any active spec overview, and locate the human-docs tree (`docs/` or equivalent — don't assume).
## 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):
- **Re-checking the project:** one area per helper; each reports what moved since AGENTS.md was written and where it shows.
Keep with you: every question, and the edits to AGENTS.md and the `.agents-docs/` files. Strength and effort per references/helper-strength.md. No helpers? Do the same work yourself.
---
## Step 1: Pre-flight Check
+7
View File
@@ -47,6 +47,13 @@ Prefix the file with:
This file provides guidance to AI coding agents working with code in this repository.
```
## 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):
- **Mapping the project:** one area per helper; each reports what the area holds, how it builds and runs, and the conventions it follows, with `file:line` where it matters.
Keep with you: every question, the judgment on what matters and the writing of AGENTS.md and its notes. Strength and effort per references/helper-strength.md. No helpers? Do the same work yourself.
---
## Progressive Discovery
+8
View File
@@ -49,6 +49,14 @@ Check if `./AGENTS.md` exists:
- **The counts are leads, not verdicts.** A script ranks; you read the code and judge.
- Plain words. Name the files and functions; skip jargon the person did not use.
## 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):
- **Step 2a:** the area's files and the leads its history names, one per helper; each returns facts with `file:line` or a commit hash, never a judgment.
- **Step 2b:** reading the top candidates the counts name, one per helper, reporting what it found.
Keep with you: the judgment, the citations, the ranking, the pick and every question. Strength and effort per references/helper-strength.md. No helpers? Do the same work yourself.
## Process
### Step 1: Mode and Area
+1 -1
View File
@@ -1,5 +1,5 @@
# Helper Strength
> 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.
> Shared by the skills that start helpers (subagents): Init, Init Update, Pathfinder, Plan, Revise Plan, Document, Quick Task, Implement, Implement + Review, Review, X-ray and Diagnose. Read it when you first start a helper in a session. Never invoked as a skill.
## The words
+1 -1
View File
@@ -1,6 +1,6 @@
# Helpers (Subagents)
The console points here when a `Subagents:` block reaches you. On the skills that offer it (`implement`, `implement-review`, `quick-task`, `review`, `pathfinder`, `plan`, `revise-plan`) the person turns helpers on or off from the top bar's Subagents button, per project and skill. It reaches you as a standing instruction, only when it changes.
The console points here when a `Subagents:` block reaches you. On the skills that offer it (`init`, `init-update`, `pathfinder`, `plan`, `revise-plan`, `document`, `implement`, `implement-review`, `quick-task`, `review`, `xray`, `diagnose`) the person turns helpers on or off from the top bar's Subagents button, per project and skill. It reaches you as a standing instruction, only when it changes.
## What arrives
+2 -1
View File
@@ -2242,7 +2242,8 @@
<section class="help-panel" data-tab="subagents">
<h3>Helpers (subagents)</h3>
<p>
On a build, a review, Pathfinder, Plan and Revise plan, Plan2Code
On most skills (all but the dashboard, Finalize, Changelog, Git and
Handoff), 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.
+5 -5
View File
@@ -75,7 +75,7 @@ export const SKILLS = Object.freeze([
pose: "init",
builds: false, phased: false, metered: true, templates: false,
weight: 2, started: "Init started", ran: "Init run", resume: null,
subagents: null,
subagents: "Use helpers to map the project in parallel, one per area: what it holds, how it builds and runs, and the conventions it follows. Keep every question, the judgment on what matters and the writing of AGENTS.md with you. Recon at light strength, low effort.",
states: "any",
greyed: { default: "AGENTS.md is already written. Refresh it instead." },
card: {
@@ -95,7 +95,7 @@ export const SKILLS = Object.freeze([
pose: "init",
builds: false, phased: false, metered: true, templates: false,
weight: 2, started: "Init update started", ran: "Init update run", resume: null,
subagents: null,
subagents: "Use helpers to re-check areas in parallel: what has moved since AGENTS.md was written, and where it shows. Keep every question and the edits to AGENTS.md and its notes with you. Recon at light strength, low effort.",
states: "any",
greyed: { default: "Needs an AGENTS.md. Set the project up first." },
card: {
@@ -186,7 +186,7 @@ export const SKILLS = Object.freeze([
pose: "document",
builds: false, phased: false, metered: true, templates: false,
weight: 2, started: "Document started", ran: "Spec documented", resume: "overview",
subagents: null,
subagents: "Use helpers for lookups while you write the phases: the files, seams and sizes behind the work a task names. Keep the breakdown, the writing and every question with you. Lookups at light strength, low effort.",
states: ["planned"], marksNext: true,
greyed: {
default: "Needs a drafted plan first",
@@ -355,7 +355,7 @@ export const SKILLS = Object.freeze([
pose: "diagnose",
builds: false, phased: false, metered: true, templates: false,
weight: 1, started: "Diagnose started", ran: "Diagnose run", resume: null,
subagents: null,
subagents: "Use helpers for the reading both modes lean on: explain mode's area files and history leads, and rough-spots mode's top candidates, one helper per area or candidate. Keep the judgment, the citations, the ranking, the pick and every question with you. Lookups at light strength, low effort.",
states: "any",
greyed: null,
card: {
@@ -376,7 +376,7 @@ export const SKILLS = Object.freeze([
pose: "changelog",
builds: false, phased: false, metered: true, templates: false,
weight: 1, started: "Changelog started", ran: "Changelog run", resume: null,
subagents: null,
subagents: "Use helpers for side lookups while you narrow: the code path a suspect change touches, a suspect function's callers, and the docs behind the failing behavior. Keep the reproduction, any bisect, the cause judgment and every question with you. Lookups at light strength, low effort.",
states: "any",
greyed: null,
card: {