Sync upstream web console updates into v2.5.1: six new starter templates (19 in all) rewritten as Markdown sections with revised content, picking a template selects its first [blank], and a real helper report now removes the "working alone" marker instead of being hidden by it

AI Assisted
This commit is contained in:
jparkerweb committed 2026-10-07 16:42:16 -07:00
1 parent c16bc81ff2
commit 482e97a090
117 files changed
+4011 -1162

No files matched your search

@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
@@ -36,85 +36,271 @@ export function needsRoleNudge(looks) {
return !Object.hasOwn(looks, "role");
}
// The wording is approved (PLAN-DRAFT Appendix A); a change is a page change.
// The wording was revised in v2.5.1 (Markdown sections); a change is a page change.
const template = (id, label, lines) => Object.freeze({ id, label, text: lines.join("\n") });
export const TEMPLATES = Object.freeze({
"engineering-spec": template("engineering-spec", "Engineering spec", [
"Engineering spec for: [the feature or change, in a sentence]",
"Who reads it: the engineers who will build and review it.",
"What it should pin down: the behaviour, the parts of the code it touches, the interfaces between them, and how we'll know it works.",
"What I already know: [constraints, links, earlier attempts]",
"## Engineering spec",
"[the feature or change, in a sentence]",
"",
"## Who reads it",
"The engineers who will build and review it.",
"",
"## What it should pin down",
"The behaviour, the parts of the code it touches, the interfaces between them, the simpler options we're turning down, and how we'll know it works.",
"",
"## Out of scope",
"[what this deliberately won't do]",
"",
"## What I already know",
"[constraints, links, earlier attempts]",
]),
"product-requirements": template("product-requirements", "Product requirements", [
"Product requirements for: [the feature, in a sentence]",
"Who it's for: [the users], and the product, design and engineering people deciding on it.",
"What it should pin down: the problem, who has it, what success looks like, and what waits for later.",
"What I already know: [customer asks, data, deadlines]",
"## Product requirements",
"[the feature, in a sentence]",
"",
"## Who it's for",
"[the users], and the product, design and engineering people deciding on it.",
"",
"## What it should pin down",
"The problem, who has it, the evidence it's real, and how we'll measure success.",
"",
"## Not doing",
"[what this release leaves out]",
"",
"## What I already know",
"[customer asks, data, deadlines]",
]),
"design-decision": template("design-decision", "Design decision", [
"A design decision to work out: [the choice we're facing, in a sentence]",
"Who it's for: the engineers and architects who will live with it.",
"What it should pin down: the options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"Constraints: [performance, compatibility, deadlines, team skills]",
"## Design decision",
"[the choice we're facing, in a sentence]",
"",
"## Who it's for",
"The engineers and architects who will live with it.",
"",
"## What it should pin down",
"The options, the trade-offs of each, the one we pick and why, and what it costs us later.",
"",
"## Constraints",
"[performance, compatibility, deadlines, team skills]",
]),
"test-strategy": template("test-strategy", "Test strategy", [
"Test strategy for: [the feature or area]",
"Who reads it: QA and the engineers writing the tests.",
'What it should pin down: what\'s risky, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"What exists today: [current tests, known gaps]",
"## Test strategy",
"[the feature or area]",
"",
"## Who reads it",
"QA and the engineers writing the tests.",
"",
"## What it should pin down",
'What\'s riskiest, meaning what costs most if it breaks, what gets tested at which level (unit, integration, end to end, by hand), the test data needed, and what "done" means.',
"",
"## What exists today",
"[current tests, known gaps]",
]),
"scoping-rollout": template("scoping-rollout", "Scoping & rollout", [
"Scoping and rollout for: [the feature or project]",
"Who reads it: the engineering manager, the product lead and the team.",
"What it should pin down: what's in the first release and what waits, the build order, risks to the timeline, and how it reaches users (flags, stages, who goes first).",
"Constraints: [dates, people, dependencies]",
"## Scoping and rollout",
"[the feature or project]",
"",
"## Who reads it",
"The engineering manager, the product lead and the team.",
"",
"## What it should pin down",
"What's in the first release and what waits, the build order, risks to the timeline, how it reaches users (flags, stages, who sees it first), and how we roll it back.",
"",
"## Constraints",
"[dates, people, dependencies]",
]),
"brainstorm-notes": template("brainstorm-notes", "Brainstorm → curated notes", [
"Brainstorm to turn into curated notes: [the topic or rough idea]",
"Who reads the notes: [the team or people this goes to]",
"What I want out of it: the ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"Starting thoughts: [anything already on your mind]",
"## Brainstorm to curated notes",
"[the topic or rough idea]",
"",
"## Who reads the notes",
"[the team or people this goes to]",
"",
"## What I want out of it",
"The ideas worth keeping, grouped, with the open questions, and the ones we dropped and why.",
"",
"## Starting thoughts",
"[anything already on your mind]",
]),
"bug-investigation": template("bug-investigation", "Bug investigation", [
"Bug to investigate: [what's going wrong, in a sentence]",
"Steps to reproduce: [1. ... 2. ...]",
"Expected: [what should happen]. Actual: [what happens instead]",
"Where and since when: [environment, version, first seen]",
"## Bug investigation",
"[what's going wrong, in a sentence]",
"",
"## Steps to reproduce",
"1. [first step]",
"2. [next step]",
"",
"## Expected",
"[what should happen]",
"",
"## Actual",
"[what happens instead]",
"",
"## How often",
"[every time, sometimes, once]",
"",
"## Error or logs",
"[paste the exact text]",
"",
"## Where and since when",
"[environment, version, first seen]",
]),
"small-change": template("small-change", "Small change", [
"Small change: [what to change, in a sentence]",
"Where: [the file, screen or command, if you know it]",
"Done when: [how you'll tell it worked]",
"## Small change",
"[what to change, in a sentence]",
"",
"## Where",
"[the file, screen or command, if you know it]",
"",
"## Leave alone",
"[anything that must not change]",
"",
"## Done when",
"[the command to run or the thing to check]",
]),
"copy-tweak": template("copy-tweak", "Copy / content tweak", [
"Change the wording of: [the screen, message, email or doc]",
"Current text: [paste it]",
"New text: [paste it, or describe the tone you want]",
"Who reads it: [the people who see it]",
"## Copy or content tweak",
"[the screen, message, email or doc]",
"",
"## Current text",
"[paste it]",
"",
"## New text",
"[paste it, or describe the tone you want]",
"",
"## Who reads it",
"[the people who see it]",
]),
"ui-polish": template("ui-polish", "UI polish", [
"UI polish on: [the screen or component]",
"What looks or feels off: [spacing, alignment, colour, states, small screens]",
"What good looks like: [a reference, screenshot or description]",
"Leave alone: [anything that must not move]",
"## UI polish",
"[the screen or component]",
"",
"## What looks or feels off",
"[spacing, alignment, colour, states, small screens]",
"",
"## What good looks like",
"[a reference, screenshot or description]",
"",
"## Leave alone",
"[anything that must not move]",
]),
"visual-prototype": template("visual-prototype", "Visual prototype", [
"A throwaway visual prototype of: [the screen or component]",
"What to show: [the states or flows to click through]",
"What I want to learn: [the question it should answer]",
"Where it lives: a prototypes/ folder [or its own branch], never wired into the real code.",
"## Visual prototype",
"[the screen or component to mock up]",
"",
"## What to show",
"[the states or flows to click through]",
"",
"## What I want to learn",
"[the question it should answer]",
"",
"## Where it lives",
"A prototypes/ folder [or its own branch], never wired into the real code.",
]),
"add-a-test": template("add-a-test", "Add a test", [
"Add a test for: [the function, behaviour or bug]",
"Cases to cover: [the normal case, the edge cases, the bug it guards against]",
"Where tests live: [the test file or folder, if you know it]",
"## Add a test",
"[the function, behaviour or bug]",
"",
"## Cases to cover",
"- [the normal case]",
"- [the edge cases]",
"- [the failure or bug it guards against]",
"",
"## Where tests live",
"[the test file or folder, if you know it]",
]),
"record-decision": template("record-decision", "Record a decision", [
"Record a decision we've already made: [the decision, in a sentence]",
"Why: [the reasons, and what we turned down]",
"What it commits us to: [the consequences]",
"Save it as an ADR in: docs/adr/ [or wherever this repo keeps them]",
"## Record a decision",
"[the decision we've already made, in a sentence]",
"",
"## Why",
"[what forced the choice, and the options we turned down]",
"",
"## What it commits us to",
"[the consequences]",
"",
"## Save it in",
"docs/adr/ [or wherever this repo keeps them]",
]),
refactor: template("refactor", "Refactor", [
"## Refactor",
"[what to restructure, in a sentence]",
"",
"## Why now",
"[what the current shape makes hard]",
"",
"## Behaviour that must not change",
"[the public API, outputs or tests that must stay the same]",
"",
"## Done when",
"[the tests that must still pass, and the shape it ends in]",
]),
"performance-problem": template("performance-problem", "Performance problem", [
"## Performance problem",
"[what's slow, in a sentence]",
"",
"## How it's measured today",
"[the number, and how you got it]",
"",
"## Target",
"[the number that counts as fixed]",
"",
"## Where",
"[the endpoint, page, query or job]",
]),
"dependency-upgrade": template("dependency-upgrade", "Dependency upgrade", [
"## Dependency upgrade",
"[the package, from version to version]",
"",
"## Why",
"[security fix, a feature we need, end of support]",
"",
"## Known breaking changes",
'[release notes link, or "not checked yet"]',
"",
"## Done when",
"[the build, tests or checks that must pass]",
]),
spike: template("spike", "Spike", [
"## Spike",
"[the question to answer, in a sentence]",
"",
"## Why it matters",
"[the decision waiting on the answer]",
"",
"## Time box",
"[how long before we stop and decide anyway]",
"",
"## Answered when",
"[the evidence that would settle it]",
]),
integration: template("integration", "Integration", [
"## Integration",
"[the system we're connecting to, and why]",
"",
"## What flows",
"[the data or events, and in which direction]",
"",
"## Their side",
"[API docs, auth method, rate limits, test sandbox]",
"",
"## When it fails",
"[what should happen if they're down or slow]",
]),
"data-migration": template("data-migration", "Data migration", [
"## Data migration",
"[what moves or changes shape]",
"",
"## Size and downtime",
"[row counts, and whether users can stay on while it runs]",
"",
"## Rollback",
"[how we undo it if it goes wrong]",
"",
"## Done when",
"[the checks that prove nothing was lost]",
]),
});
@@ -123,28 +309,28 @@ const orders = (byRole) => Object.freeze(Object.fromEntries(Object.entries(byRol
// One full order per role per skill. No "none" row: Not set reads Engineer's.
export const TEMPLATE_ORDERS = Object.freeze({
pathfinder: orders({
engineer: ["engineering-spec", "design-decision", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "engineering-spec", "design-decision", "test-strategy"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "design-decision", "brainstorm-notes"],
engineer: ["engineering-spec", "design-decision", "spike", "integration", "test-strategy", "scoping-rollout", "product-requirements", "brainstorm-notes"],
pm: ["product-requirements", "brainstorm-notes", "scoping-rollout", "spike", "engineering-spec", "design-decision", "integration", "test-strategy"],
architect: ["design-decision", "engineering-spec", "integration", "spike", "scoping-rollout", "test-strategy", "product-requirements", "brainstorm-notes"],
designer: ["brainstorm-notes", "product-requirements", "design-decision", "spike", "engineering-spec", "scoping-rollout", "integration", "test-strategy"],
qa: ["test-strategy", "engineering-spec", "spike", "product-requirements", "integration", "scoping-rollout", "design-decision", "brainstorm-notes"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "spike", "test-strategy", "design-decision", "integration", "brainstorm-notes"],
}),
plan: orders({
engineer: ["engineering-spec", "bug-investigation", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "test-strategy", "design-decision", "bug-investigation"],
architect: ["design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "test-strategy", "bug-investigation"],
qa: ["test-strategy", "bug-investigation", "engineering-spec", "product-requirements", "scoping-rollout", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "product-requirements", "test-strategy", "bug-investigation", "design-decision"],
engineer: ["engineering-spec", "bug-investigation", "refactor", "performance-problem", "integration", "data-migration", "design-decision", "test-strategy", "scoping-rollout", "product-requirements"],
pm: ["product-requirements", "scoping-rollout", "engineering-spec", "integration", "test-strategy", "design-decision", "performance-problem", "bug-investigation", "data-migration", "refactor"],
architect: ["design-decision", "engineering-spec", "data-migration", "integration", "refactor", "scoping-rollout", "performance-problem", "test-strategy", "product-requirements", "bug-investigation"],
designer: ["product-requirements", "design-decision", "engineering-spec", "scoping-rollout", "performance-problem", "test-strategy", "bug-investigation", "integration", "refactor", "data-migration"],
qa: ["test-strategy", "bug-investigation", "performance-problem", "engineering-spec", "data-migration", "integration", "product-requirements", "scoping-rollout", "refactor", "design-decision"],
em: ["scoping-rollout", "engineering-spec", "data-migration", "product-requirements", "test-strategy", "integration", "bug-investigation", "performance-problem", "refactor", "design-decision"],
}),
"quick-task": orders({
engineer: ["small-change", "bug-investigation", "add-a-test", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "add-a-test", "record-decision"],
architect: ["record-decision", "small-change", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "add-a-test", "record-decision"],
qa: ["add-a-test", "bug-investigation", "small-change", "ui-polish", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "add-a-test", "bug-investigation", "copy-tweak", "ui-polish", "visual-prototype"],
engineer: ["small-change", "bug-investigation", "refactor", "add-a-test", "dependency-upgrade", "performance-problem", "ui-polish", "record-decision", "copy-tweak", "visual-prototype"],
pm: ["copy-tweak", "small-change", "visual-prototype", "ui-polish", "bug-investigation", "performance-problem", "add-a-test", "record-decision", "dependency-upgrade", "refactor"],
architect: ["record-decision", "refactor", "small-change", "dependency-upgrade", "performance-problem", "bug-investigation", "add-a-test", "visual-prototype", "ui-polish", "copy-tweak"],
designer: ["ui-polish", "visual-prototype", "copy-tweak", "small-change", "bug-investigation", "performance-problem", "add-a-test", "refactor", "dependency-upgrade", "record-decision"],
qa: ["add-a-test", "bug-investigation", "performance-problem", "small-change", "dependency-upgrade", "ui-polish", "refactor", "copy-tweak", "visual-prototype", "record-decision"],
em: ["small-change", "record-decision", "dependency-upgrade", "add-a-test", "bug-investigation", "performance-problem", "refactor", "copy-tweak", "ui-polish", "visual-prototype"],
}),
});
@@ -88,7 +88,7 @@ export function cleanSetting(input) {
export const FRAME_LINES = Object.freeze([
"Hand independent work to helpers if your tools allow it; otherwise carry on alone.",
"Report each helper on the page (console.md → Standing instructions); questions for the person stay with you.",
'With no way to start helpers, report one "working alone" entry for this skill run instead.',
'If your tools cannot start helpers at all, report one "working alone" entry for this skill run instead; a real helper report removes it.',
]);
export const PATHFINDER_RESEARCH_LINE = "Research questions always use helpers, whatever this switch says.";
@@ -201,11 +201,14 @@ export function switchLabel(frame) {
}
// What the Subagents tab draws: the working-alone note, or one row per helper
// in the order the agent reported them. A result shows once the helper ended.
// in the order the agent reported them. A real helper supersedes the
// working-alone marker, so the note only draws when no helper was ever
// reported. A result shows once the helper ended.
export function helperRows(helpers) {
const list = Array.isArray(helpers) ? helpers.filter(isPlainObject) : [];
if (list.some((h) => h.alone === true)) return { alone: true, rows: [] };
const rows = list.map(({ id, title, ask, state, result }) => ({
const real = list.filter((h) => h.alone !== true);
if (!real.length) return { alone: list.some((h) => h.alone === true), rows: [] };
const rows = real.map(({ id, title, ask, state, result }) => ({
id,
title,
ask,
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
+2 -2
View File
@@ -1,6 +1,6 @@
{
"name": "Plan2Code",
"version": "2.5.0",
"version": "2.5.1",
"description": "A structured 4-step workflow methodology for AI-assisted software development",
"keywords": [
"ai",
@@ -17,6 +17,6 @@
"url": "https://github.com/jparkerweb/plan2code"
},
"homepage": "https://github.com/jparkerweb/plan2code",
"releaseDate": "2026-10-06",
"releaseDate": "2026-10-07",
"mode": "utility"
}
@@ -667,7 +667,7 @@ your next `chat` check.
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.md → Standing instructions); questions for the person stay with you.
With no way to start helpers, report one "working alone" entry for this skill run instead.
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.
At most 3 helpers at once.
```
@@ -716,8 +716,11 @@ page never hears from a helper directly:
- Questions for the person stay with you, never with a helper: most harnesses
give helpers no way to ask, and an answer only reaches the agent holding the
session.
- **No way to start helpers?** Post one `{ "id": "alone", "alone": true }`
- **No way to start helpers at all?** Post one `{ "id": "alone", "alone": true }`
entry for the skill run instead. The tab then says you are working alone.
It is a claim about your tools, not about the moment — post it only when no
helper mechanism exists. Reporting a real helper removes it, so an early
`alone` can never hide a later helper.
- **Pathfinder:** research questions always use helpers and are always
reported, whatever the switch says. The switch governs recon, sketches and
lookups beside the conversation.
@@ -1211,6 +1211,10 @@ export function applyPatch(state, patch) {
if (!Array.isArray(v)) throw new Error('"helpers" must be an array');
if (!v.every(isPlainObject)) throw new Error('"helpers" entries must be objects, each { id, title, ask, state }');
next.helpers = mergeKeyed(next.helpers, v, "id", {}, "helpers");
// A real helper report supersedes the working-alone marker, whether it
// arrives after one or beside one.
if (next.helpers.some((h) => isPlainObject(h) && h.alone !== true))
next.helpers = next.helpers.filter((h) => !(isPlainObject(h) && h.alone === true));
break;
case "docs":
if (!Array.isArray(v)) throw new Error('"docs" must be an array');
@@ -4345,8 +4345,11 @@ function templateRow(item, input, entries, check) {
save();
paint();
input.focus();
const start = text.indexOf("[");
const end = start < 0 ? -1 : text.indexOf("]", start);
try {
input.setSelectionRange(text.length, text.length);
if (end > start) input.setSelectionRange(start, end + 1);
else input.setSelectionRange(text.length, text.length);
} catch {}
};
@@ -1540,8 +1540,9 @@
on the Ask tab if one should stop.
</li>
<li>
<strong>Working alone</strong> means your agent has no way to start
helpers here, so it is doing the work itself.
<strong>Working alone</strong> means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
</li>
<li>
Pathfinder always uses helpers for its research questions, whatever
Loaded 100 of 117 files, more files were not shown because too many files have changed in this diff. Show more