Skip to content
8 changes: 4 additions & 4 deletions .herdrpowers/profiles/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Use `solo` for tasks that need neither complex decisions nor coding.

- Select a profile by setting `profile` in `.herdrpowers/config.yaml` to the filename without its extension.
Naming a profile in the task instructions selects it for that run only; leave the config unchanged.
Profiles contain only the `orchestrator`, `coder`, and `reviewers` composition keys.
Profiles contain only the `planning-design`, `orchestrator`, `coder`, `reviewers`, and `generalist` composition keys.
Omitted `coder` and `reviewers` keep the resolved role bindings; an omitted `orchestrator` keeps the reception pane as owner.
- `allow_agent_lifecycle` is a config boolean. Use literal `true` or `false`; `"true"` and `yes` are errors.
`false` (default): no agent starts, exits, or restarts. Set up any missing agents manually.
Expand All @@ -32,9 +32,9 @@ Use `solo` for tasks that need neither complex decisions nor coding.
- `claude` does not show model or effort in its footer by default. Without a statusLine, a `claude` target always fails to match.
Add this to `~/.claude/settings.json` (`jq` required):
`{"statusLine": {"type": "command", "command": "jq -r '\"\\(.model.display_name) \\(.effort.level // \"\")\"'"}}`
- `null` is standard YAML null. Preserve it in shipped templates. Bare `none` is a supported literal alias, not YAML null.
`coder: null` / `[]` / `none` means no separate coder.
`reviewers: []` / `null` / `none` selects owner review; it does not disable reviews.
- `null` is standard YAML null. Bare `none` is a supported literal alias, not YAML null.
`planning-design`/`coder`/`generalist`: `orchestrator` / `null` / `[]` / `none` binds to the owner.
`reviewers: [orchestrator]` / `[]` / `null` / `none` selects owner review; it does not disable reviews.
- `delegate` requires a fresh subagent every time, even when targeting the owner. An empty composition does not waive this requirement.
Disabled gates stay disabled. Selecting a composition must not change modes or gates.
- If the reception pane does not match the owner, always ask whether it should be `unused` or a `relay` before handoff or startup.
Expand Down
4 changes: 3 additions & 1 deletion .herdrpowers/profiles/astra-sol.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
planning-design: orchestrator
orchestrator:
codex:
model: GPT-6-Astra
Expand All @@ -6,4 +7,5 @@ coder:
codex:
model: GPT-6.1-Sol
effort: max
reviewers: []
reviewers: [orchestrator]
generalist: orchestrator
2 changes: 2 additions & 0 deletions .herdrpowers/profiles/fable-opus-panel.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
planning-design: orchestrator
orchestrator:
claude:
model: Fable 5.2
Expand All @@ -19,3 +20,4 @@ reviewers:
- cursor:
model: Grok 4.7
effort: Extra High
generalist: orchestrator
4 changes: 3 additions & 1 deletion .herdrpowers/profiles/fable-opus.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
planning-design: orchestrator
orchestrator:
claude:
model: Fable 5.2
Expand All @@ -6,4 +7,5 @@ coder:
claude:
model: Opus 5.5
effort: max
reviewers: []
reviewers: [orchestrator]
generalist: orchestrator
2 changes: 2 additions & 0 deletions .herdrpowers/profiles/fable-sol-panel.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
planning-design: orchestrator
orchestrator:
claude:
model: Fable 5.2
Expand All @@ -19,3 +20,4 @@ reviewers:
- cursor:
model: Grok 4.7
effort: Extra High
generalist: orchestrator
6 changes: 4 additions & 2 deletions .herdrpowers/profiles/opus-solo.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
planning-design: orchestrator
orchestrator:
claude:
model: Opus 5.5
effort: max
coder: null
reviewers: []
coder: orchestrator
reviewers: [orchestrator]
generalist: orchestrator
6 changes: 4 additions & 2 deletions .herdrpowers/profiles/sol-solo.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
planning-design: orchestrator
orchestrator:
codex:
model: GPT-6.1-Sol
effort: max
coder: null
reviewers: []
coder: orchestrator
reviewers: [orchestrator]
generalist: orchestrator
13 changes: 13 additions & 0 deletions changelogs/2026-11-11-generalist-profile-targets.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
change_type: pack-native
date: 2026-11-11
---

# Planning-design and generalist profile keys; orchestrator alias for coder

Profiles accept `planning-design` and `generalist` with the same values as
`coder`. All three take a
nested target or bare `orchestrator`; `orchestrator`, null, `[]`, and `none`
bind to the owner; `reviewers: [orchestrator]` selects owner review. Shipped
profiles set `planning-design: orchestrator` and `generalist: orchestrator`; solo profiles set `coder: orchestrator`
and `reviewers: [orchestrator]`.
8 changes: 4 additions & 4 deletions commands/init.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ selection is an explicit error, not a reason to silently clear it.
|---|---|---|
| `planning-design` | one target, or `orchestrator` | Who plans and designs; the alias resolves to the active owner. Preserve custom target bindings |
| `reviewer` | a **list** of targets | One review per entry. A profile's explicit empty reviewers instead selects the owner; it does not disable reviews |
| `coder` | one agent type | The heavier-judgment role: complex coding, test authoring, whole-branch review |
| `coder` | one target, or `orchestrator` | The heavier-judgment role: complex coding, test authoring, whole-branch review |
| `generalist` | one target, or `orchestrator` | Simple coding, inspection, tests, and routine operations; preserve custom target bindings |
| `fallbacks.<agent>` | a list of string targets | Ordered substitutes for unavailable/exhausted agents; no effort constraint |

Expand All @@ -110,8 +110,8 @@ and write nested targets. Fallback keys/substitutes keep bare-kind or
`kind@model` string syntax. Preserve supplied strings, including `Calude` and
the unequal `muse-1.0-wonder` / `muse-wonder-1.0` spellings; no fuzzy aliases.

State the empty-value rules explicitly: profile `coder: null`/`[]`/`none`
means no separate coder; `reviewers: []`/null/`none` means owner review.
State the empty-value rules explicitly: profile `planning-design`/`coder`/`generalist`
`orchestrator`/null/`[]`/`none` binds to the owner; `reviewers: [orchestrator]`/`[]`/null/`none` means owner review.
Legacy `roles.<role>.agents: []` still disables the task when no profile
overrides that binding. Lists replace, and a matched empty fallback list is
authoritative. A fallback never inherits the primary effort.
Expand Down Expand Up @@ -322,7 +322,7 @@ Re-read every written file and confirm:
- top-level `profile` is null/`none` or a valid simple name whose selected local/shipped file exists and validates; errors remain explicit rather than clearing selection;
- top-level `allow_agent_lifecycle` is a YAML boolean, not a string, null, or a field nested in a profile or `delegation`, and `bash <pack>/skills/using-herdr-sibling-panes/scripts/agent-lifecycle.sh policy`, run from the repository, prints the approved value — that helper is what enforces it at runtime;
- new role targets are one-kind mappings with only optional nonempty model/effort strings, effort requires model, and bare `orchestrator` aliases/custom bindings were preserved;
- profiles contain only the three composition keys with the absent/empty semantics above; original string spelling and reviewer order are intact;
- profiles contain only the five composition keys with the absent/empty semantics above; original string spelling and reviewer order are intact;
- all missing shipped templates were installed, every pre-existing profile file is byte-identical, and repeat init preserved the chosen profile, assignments, gate enablement, delegation, and permission;
- the shipped profiles README was installed only if absent; any pre-existing local README is byte-identical;
- `delegation.pane_scope` is one of `tab`, `workspace`, `session`, and `delegation.execution` is one of `parallel`, `serial`;
Expand Down
12 changes: 7 additions & 5 deletions docs/roles.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,13 @@ Customize the repo file, not `roles.yaml` — plugin installs are read-only, and
After merging repo config over shipped roles, overlay only keys present in the
selected `.herdrpowers/profiles/<name>.yaml`, repo-local first and shipped only
if absent locally. Invalid names, files, or targets are explicit errors. Profiles
contain only `orchestrator`, `coder`, and `reviewers`; omitted slots keep resolved
roles. Explicit empty coder (`null`, `[]`, `none`) means solo; empty reviewers
(`[]`, null, `none`) select the owner without disabling a gate. Lists replace.
Preserve custom planning-design/generalist bindings, added roles, assignments,
modes, and gates. A concrete coder matching the owner is still a separate worker.
contain only `planning-design`, `orchestrator`, `coder`, `reviewers`, and `generalist`;
omitted slots keep resolved roles. Planning-design/coder/generalist `orchestrator`, `null`, `[]`, or `none` binds to the
owner (solo coder); owner reviewers
(`[orchestrator]`, `[]`, null, `none`) select the owner without disabling a gate. Lists replace.
Preserve planning-design/generalist bindings the profile omits,
added roles, assignments, modes, and gates. A concrete coder matching the owner
is still a separate worker.

A mismatched reception pane always asks **unused or relay** before owner handoff
or startup, even if a matching owner exists. The explicit handoff transfers
Expand Down
8 changes: 4 additions & 4 deletions skills/orchestration/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,9 @@ The base files share this schema:
- **`allow_agent_lifecycle`** — top-level strict boolean, separate from composition/delegation; defaults false. False starts and ends no agent. True lets the active owner start a resolved target that has no live match and end idle agents the task started, only through `agent-lifecycle.sh`, which enforces the value. Read the profiles reference before any startup, exit, or recovery action, including owner handoff and fallback.

Merging is per key, not per file. Lists replace rather than concatenate.
Profile keys override conflicting role bindings only when present; omitted
keys preserve them. A profile never changes assignments, gate enablement, or
delegation defaults. Empty profile reviewers select the owner, while a legacy
Profile keys override the planning-design, orchestrator, coder, reviewer, or generalist binding
only when present; omitted keys preserve them. A profile never changes
assignments, gate enablement, or delegation defaults. Empty profile reviewers select the owner, while a legacy
empty role list keeps its disabling semantics if no profile overrides it.

Report assignment keys not defined by `roles.yaml`: otherwise their intended
Expand Down Expand Up @@ -119,7 +119,7 @@ Resolve every task the workflow will touch before its first delegation, not when
A role declared with `agents:` runs **one delegation per entry**, and you wait
for all before acting. A one-entry list is a deliberate single delegation.
A legacy empty role list disables that task unless a profile overrides the
binding. Profile `reviewers: []`/null/`none` instead selects the active owner;
binding. Profile `reviewers: [orchestrator]`/`[]`/null/`none` instead selects the active owner;
an enabled review still runs and `delegate` still requires a fresh subagent.

Three rules bind wherever a list role is used:
Expand Down
15 changes: 9 additions & 6 deletions skills/orchestration/references/profiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,15 +46,18 @@ the directory holding `skills/`, three levels above this file.
execution strategy, and lifecycle permission for the run. Do not rewrite
configuration or switch profiles to escape a missing agent or a gate.

Profiles contain only `orchestrator`, `coder`, and `reviewers`. Each is
optional in a custom profile; shipped compositions live in the six YAML
Profiles contain only `planning-design`, `orchestrator`, `coder`, `reviewers`,
and `generalist`.
Each is optional in a custom profile; shipped compositions live in the six YAML
assets, which are the source of truth for their values and reviewer order.

| Profile key | When absent | When present |
|---|---|---|
| `orchestrator` | Keep the legacy owner, the pane receiving the user's task | One nested target selects the active owner; null, `none`, and lists are invalid |
| `coder` | Keep the resolved `roles.coder` binding | One nested target replaces that binding; null, `[]`, or literal `none` binds it to the active owner, with no separate coder |
| `reviewers` | Keep the resolved `roles.reviewer` binding | A nonempty list of nested targets replaces that binding in order; `[]`, null, or literal `none` binds it to the active owner, with no external reviewers |
| `planning-design` | Keep the resolved `roles.planning-design` binding | One nested target replaces that binding; bare `orchestrator`, null, `[]`, or literal `none` binds it to the active owner |
| `generalist` | Keep the resolved `roles.generalist` binding | One nested target replaces that binding; bare `orchestrator`, null, `[]`, or literal `none` binds it to the active owner |
| `coder` | Keep the resolved `roles.coder` binding | One nested target replaces that binding; bare `orchestrator`, null, `[]`, or literal `none` binds it to the active owner, with no separate coder |
| `reviewers` | Keep the resolved `roles.reviewer` binding | A nonempty list of nested targets replaces that binding in order; `[orchestrator]`, `[]`, null, or literal `none` binds it to the active owner, with no external reviewers |

**Empty profile reviewers choose a reviewer; they do not disable a gate.**
An enabled review still runs, and an explicitly delegated review still needs
Expand All @@ -65,9 +68,9 @@ the selected profile has not overridden it; profile omission must not
reactivate it. The profile's explicit empty `coder` or `reviewers` replaces
that binding, so legacy empty-list disabling no longer applies to it.

Owner selection does not replace `planning-design` or `generalist` bindings.
An existing `agent: orchestrator` is a dynamic alias for the active owner;
custom bindings to other targets remain intact, as do all user-added roles.
custom `planning-design`/`generalist` bindings remain intact when the profile
omits that key, as do all user-added roles.
A concrete coder/reviewer target remains a separate worker even when its
kind/model equals the owner's. Only an owner alias or a mode resolving to
the owner is a self-target.
Expand Down
27 changes: 26 additions & 1 deletion tests/orchestration-profiles/profiles.test.mjs
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
import assert from 'node:assert/strict';
import { existsSync, mkdtempSync, readdirSync, rmSync, statSync } from 'node:fs';
import { existsSync, mkdtempSync, readFileSync, readdirSync, rmSync, statSync } from 'node:fs';
import { tmpdir } from 'node:os';
import { join } from 'node:path';
import { spawnSync } from 'node:child_process';
Expand All @@ -25,6 +25,31 @@ test('the six named profile templates are available as files', () => {
for (const name of names) assert.ok(statSync(join(profiles, name)).isFile(), `${name} must be a file`);
});

test('every shipped profile routes planning-design and generalist tasks to its selected owner', () => {
for (const name of names) {
const source = readFileSync(join(profiles, name), 'utf8');
assert.match(source, /^planning-design: orchestrator\n/, `${name} must start with planning-design: orchestrator`);
assert.match(source, /^generalist: orchestrator$/m, `${name} must bind generalist to the orchestrator`);
}
});

test('the profile contract binds coder and generalist orchestrator or none to the owner', () => {
const contract = readFileSync(join(root, 'skills/orchestration/references/profiles.md'), 'utf8');
for (const key of ['planning-design', 'generalist', 'coder']) {
assert.match(contract, new RegExp(`\\| \`${key}\` \\|[^\\n]*bare \`orchestrator\`, null, \`\\[\\]\`, or literal \`none\` binds it to the active owner`));
}
});

test('solo profiles bind coder and reviewers to the orchestrator alias', () => {
for (const name of ['opus-solo.yaml', 'sol-solo.yaml']) {
const source = readFileSync(join(profiles, name), 'utf8');
assert.match(source, /^coder: orchestrator$/m, name);
assert.match(source, /^reviewers: \[orchestrator\]$/m, name);
}
const contract = readFileSync(join(root, 'skills/orchestration/references/profiles.md'), 'utf8');
assert.match(contract, /\| `reviewers` \|[^\n]*`\[orchestrator\]`, `\[\]`, null, or literal `none` binds it to the active owner/);
});

test('npm distribution includes the six orchestration profiles and their README, nothing else local', () => {
const cache = mkdtempSync(join(tmpdir(), 'herdr-profile-pack-'));
try {
Expand Down
Loading