Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 14 additions & 10 deletions .herdrpowers/profiles/README.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,28 @@
# Profiles

Names follow the owner-coder pattern (orchestrator-implementer). `panel` means four external reviewers; `solo` means no separate coder.
Names put the owner first. `ultra` means four external reviewers; `solo` means no separate coder.
YAML keys start with `orchestrator` when present, then `planning-design`; `generalist` stays last.

| File | Composition and purpose |
|---|---|
| `fable-sol-panel.yaml` | `Fable 5.2` owner, `GPT-6.1-Sol` coder, four external reviewers. Largest composition. |
| `fable-opus-panel.yaml` | `Fable 5.2` owner, separate `Opus 5.5` coder, four external reviewers. Largest composition. |
| `astra-sol.yaml` | `GPT-6-Astra` owner, `GPT-6.1-Sol` coder; the owner reviews. Conserves Codex tokens. |
| `fable-opus.yaml` | `Fable 5.2` owner, `Opus 5.5` coder; the owner reviews. Conserves Claude tokens. |
| `fable-sol-ultra.yaml` | `Fable 5.2` owner, `GPT-6.1-Sol` coder, four external reviewers. Largest composition. |
| `fable-opus-ultra.yaml` | `Fable 5.2` owner, separate `Opus 5.5` coder, four external reviewers. Largest composition. |
| `sol-astra.yaml` | `GPT-6.1-Sol` owner executes; `GPT-6-Astra` handles planning and reviews. Conserves Codex tokens. |
| `opus-fable.yaml` | `Opus 5.5` owner executes; `Fable 5.2` handles planning and reviews. Conserves Claude tokens. |
| `sol-solo.yaml` | `GPT-6.1-Sol` only. |
| `opus-solo.yaml` | `Opus 5.5` only. |

For the two largest compositions, choose the coder from whichever subscription has the larger token allowance.
The smaller compositions use owner reviews to leave more tokens available for reviewing heavier work.
The two smaller compositions keep execution on the cheaper owner and delegate only planning and reviews to the upper model.
They override `assignments.plan-and-design.mode` to `delegate`; other assignment fields retain config/default values.
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 `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.
Profiles allow `planning-design`, `orchestrator`, `coder`, `reviewers`, `generalist`, `fallbacks`, `delegation`, and `assignments`.
Composition slots replace bindings; override maps merge per key, including each assignment's fields. Omitted keys keep config/default values.
Lists replace, including `[]`; empty override maps change nothing. Null, scalars, and lists are invalid override maps.
An omitted `orchestrator` keeps the reception pane as owner. Lifecycle permission remains config-only.
- `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.
`true`: the owner starts missing targets in available shell panes within scope and ends only idle agents it started.
Expand All @@ -36,9 +40,9 @@ Use `solo` for tasks that need neither complex decisions nor coding.
`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.
Apply resolved modes and gates after profile overrides; a resolved disabled gate stays off.
- If the reception pane does not match the owner, always ask whether it should be `unused` or a `relay` before handoff or startup.
- Fallback strings belong in the config or default roles. They do not inherit the original target's `effort`.
- Fallback strings may be overridden per key in a profile. They do not inherit the original target's `effort`.
Preserve `Calude`, `muse-1.0-wonder`, and `muse-wonder-1.0` exactly. Do not merge distinct names through fuzzy matching or spelling repairs.

See the [composition, selection, and handoff contract](https://github.com/transparent-pegasus/herdrpowers/blob/main/skills/orchestration/references/profiles.md) for details.
11 changes: 0 additions & 11 deletions .herdrpowers/profiles/astra-sol.yaml

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
planning-design: orchestrator
orchestrator:
claude:
model: Fable 5.2
effort: max
planning-design: orchestrator
coder:
claude:
model: Opus 5.5
Expand Down
11 changes: 0 additions & 11 deletions .herdrpowers/profiles/fable-opus.yaml

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
planning-design: orchestrator
orchestrator:
claude:
model: Fable 5.2
effort: max
planning-design: orchestrator
coder:
codex:
model: GPT-6.1-Sol
Expand Down
17 changes: 17 additions & 0 deletions .herdrpowers/profiles/opus-fable.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
orchestrator:
claude:
model: Opus 5.5
effort: max
planning-design:
claude:
model: Fable 5.2
effort: max
coder: orchestrator
reviewers:
- claude:
model: Fable 5.2
effort: max
assignments:
plan-and-design:
mode: delegate
generalist: orchestrator
2 changes: 1 addition & 1 deletion .herdrpowers/profiles/opus-solo.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
planning-design: orchestrator
orchestrator:
claude:
model: Opus 5.5
effort: max
planning-design: orchestrator
coder: orchestrator
reviewers: [orchestrator]
generalist: orchestrator
17 changes: 17 additions & 0 deletions .herdrpowers/profiles/sol-astra.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
orchestrator:
codex:
model: GPT-6.1-Sol
effort: max
planning-design:
codex:
model: GPT-6-Astra
effort: max
coder: orchestrator
reviewers:
- codex:
model: GPT-6-Astra
effort: max
assignments:
plan-and-design:
mode: delegate
generalist: orchestrator
2 changes: 1 addition & 1 deletion .herdrpowers/profiles/sol-solo.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
planning-design: orchestrator
orchestrator:
codex:
model: GPT-6.1-Sol
effort: max
planning-design: orchestrator
coder: orchestrator
reviewers: [orchestrator]
generalist: orchestrator
2 changes: 1 addition & 1 deletion CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ When editing pack behavior, edit `skills/` or `commands/` directly. `docs/` hold
## Pack Invariants

- **Dispatch follows the canonical profiles contract.** Read `skills/orchestration/references/profiles.md` before routing. Separate delegated targets use reset-backed Herdr panes through `using-herdr-sibling-panes`. With a selected profile, self-target `delegate` requires a fresh in-process subagent for work and reviews, including solo coder/empty reviewers; other owner-session modes permit inline work/self-review and optional subagents at the active owner's judgment. Missing mandatory subagent capability is inability, never inline delegation or a passed gate. Without a profile, preserve legacy routing and fresh-subagent orchestrator-mode reviews. Workers never re-delegate. Skill-authorship testing still uses fresh API/reset-pane samples under `writing-skills`, never in-session sampling.
- **Roles and task names, not tool names.** Skills name roles and delegation tasks. Resolve repo `.herdrpowers/config.yaml` over shipped `skills/orchestration/roles.yaml`, then overlay only composition keys present in the selected profile. Preserve custom roles, planning-design/generalist bindings, assignments, modes, and gates. Bare `orchestrator` is a dynamic active-owner alias. `roles.yaml` is the default layer, never a consumer customization point. This checkout is the upstream plugin; do not initialize it as a consumer merely to edit payload behavior.
- **Roles and task names, not tool names.** Skills name roles and delegation tasks. Resolve repo `.herdrpowers/config.yaml` over shipped `skills/orchestration/roles.yaml`, then overlay only keys present in the selected profile. Composition slots replace bindings; fallbacks, delegation, and assignments merge per key, including task fields. Preserve custom roles and omitted bindings/settings; lists replace, including empty lists. Bare `orchestrator` is a dynamic active-owner alias. `roles.yaml` is the default layer, never a consumer customization point. This checkout is the upstream plugin; do not initialize it as a consumer merely to edit payload behavior.
- **The YAML is the source of truth for defaults; prose points at it.** No skill, command, or doc restates a shipped `role`/`mode` value — they name what a task covers and say "read the resolved assignment". A `| Default |` column in a payload table is a bug: it goes stale silently and gives agents a second, wrong answer. Adding a role, a delegation task, or a `delegation:` key means updating `roles.yaml` plus the tables in `skills/orchestration/SKILL.md`, `commands/init.md`, and `docs/roles.md` — the tables, not defaults inside them.
- **Delegation never crosses the orchestrator's tab unless the repo says so.** `delegation.pane_scope` defaults to `tab`; an out-of-scope pane is not a candidate, not a fallback target, and not counted toward an agent type's availability. A payload file that selects panes without filtering on `tab_id` is a bug. Scope is never widened mid-run — that is a configuration change, and configuration is read-only inside a run.
- **Targets and list slots are explicit.** New role/profile targets use nested `{kind: {model: ..., effort: ...}}`; effort requires model. Legacy non-fallback `kind@model` is migration input only. Separate list slots need distinct kinds or distinct pinned models (case-insensitive, neither containing the other); effort alone adds no independence. Model/effort must match live footer evidence before keys and after reset; unknown evidence fails closed. Never switch an existing agent's settings. Fallback keys/substitutes retain exact effort-free strings; a matched empty list is authoritative and primary effort is discarded. Preserve `Calude` and the unequal Muse spellings.
Expand Down
14 changes: 8 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Coordinates planning, implementation, testing, and review across agent panes.
| task loop | `subagent-driven-development` | `pane-driven-development` |
| parallel work | `dispatching-parallel-agents` | panes, bounded by idle panes and worktrees |
| entry point | skills trigger themselves | `commands/` workflows, plus the same skills |
| routing | fixed in the skill | `.herdrpowers/config.yaml` over `roles.yaml`, plus an optional composition profile |
| routing | fixed in the skill | `.herdrpowers/config.yaml` over `roles.yaml`, plus an optional profile |
| who writes tests | the implementer, always | the `test-authoring` assignment |
| review | one reviewer subagent | a role bound to a list of agent types: one review per entry |

Expand Down Expand Up @@ -86,18 +86,20 @@ Repository settings stay outside the plugin and survive updates:
worktree directory (`WORKTREE_DIRECTORY`, default `.worktrees/`).
- `.herdrpowers/config.yaml`: agent roles, task assignments, delegation scope,
review settings, the selected `profile`, and `allow_agent_lifecycle`.
- `.herdrpowers/profiles/`: composition profiles — who orchestrates, codes,
and reviews, each with a model and reasoning effort. Init installs the six
- `.herdrpowers/profiles/`: presets for role targets, models/effort, and
optional fallback, delegation, and assignment overrides. Init installs the six
shipped ones without overwriting yours; their
[README](.herdrpowers/profiles/README.md) explains the names.

```yaml
profile: fable-sol-panel # or name one in the task; null selects none
profile: fable-sol-ultra # or name one in the task; null selects none
allow_agent_lifecycle: false # true: the orchestrator may start and end agents in panes
```

A profile replaces only the roles it names; assignments and review gates stay
as configured. Model and effort must match what each pane shows in its
A profile overrides only present keys. Omitted keys keep config/default
values; maps merge per key and lists replace, including empty lists.
Assignment overrides may change modes and review gates; lifecycle permission
remains config-only. Model and effort must match what each pane shows in its
footer. With `allow_agent_lifecycle: true` the orchestrator starts the
selected composition's missing agents in idle shell panes and ends the ones it
started; with `false`, the default, it never starts or ends an agent. See
Expand Down
26 changes: 26 additions & 0 deletions changelogs/2026-11-11-profile-overrides-and-presets.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
change_type: pack-native
date: 2026-11-11
---

# Profile overrides and revised presets

Profiles can override `fallbacks`, `delegation`, and `assignments` per key,
including individual assignment fields. Omitted keys keep config/default
values; lists replace, including empty lists. Lifecycle permission remains
config-only. The lifecycle helper accepts the frozen resolved pane scope
through `HERDRPOWERS_PANE_SCOPE`, preserving profile scope overrides while
keeping its permission and scope guards.

Rename `fable-sol-panel.yaml` and `fable-opus-panel.yaml` to
`fable-sol-ultra.yaml` and `fable-opus-ultra.yaml` without changing their
targets. Replace `astra-sol.yaml` and `fable-opus.yaml` with `sol-astra.yaml`
and `opus-fable.yaml`: Sol/Opus owns execution, Astra/Fable handles planning
and one review, all at `max` effort. Both set `coder` and `generalist` to
`orchestrator` and override only `assignments.plan-and-design.mode` to
`delegate`. Presets put `orchestrator` first when present, then
`planning-design`; `generalist` remains last.

Synchronize workflow/skill instructions, configuration docs, preset names,
and npm package expectations. Add regression coverage for resolved lifecycle
scope, including narrowing, invalid values, and unchanged permission denial.
2 changes: 1 addition & 1 deletion commands/execute.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Do not edit workflow files unless the user's current request explicitly asks to

## Orchestration

Read `orchestration`, its [profiles contract](../skills/orchestration/references/profiles.md), and `using-herdr-sibling-panes` before routing work. Resolve repo config over shipped roles, then only composition keys present in the selected profile. Freeze the active owner, targets, assignments, gates, scope, strategy, and lifecycle policy. A profile never rewrites modes or gate enablement; a disabled gate is skipped and named in the report.
Read `orchestration`, its [profiles contract](../skills/orchestration/references/profiles.md), and `using-herdr-sibling-panes` before routing work. Resolve repo config over shipped roles, then only keys present in the selected profile. Freeze the active owner, targets, assignments, gates, scope, strategy, and lifecycle policy. Profile assignment overrides resolve before routing; a resolved disabled gate is skipped and named in the report.

Routing comes from `assignments:`, not from this file, and the resolved YAML is the source of truth for every default — read each task's `role` and `mode` there rather than recalling one. This workflow touches `complex-coding` / `simple-coding`, `test-authoring`, `fix-round-test-authoring`, `review-fixes`, `chores`, `verification`, `documentation-impact-review`, `task-review`, `fix-round-re-review`, and `final-branch-review`. A review task whose effective role binds to a list runs once per entry.
- Plan revisions follow `plan-and-design`; final synthesis stays with the active owner.
Expand Down
2 changes: 1 addition & 1 deletion commands/execute_parallel.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Do not edit workflow files unless the user's current request explicitly asks to

## Orchestration

Read `orchestration`, its [profiles contract](../skills/orchestration/references/profiles.md), and `using-herdr-sibling-panes` before routing work. Resolve repo config over shipped roles, then only composition keys present in the selected profile. Freeze the active owner, targets, assignments, gates, scope, strategy, and lifecycle policy. A profile never rewrites modes or gate enablement; a disabled gate is skipped and named in the report.
Read `orchestration`, its [profiles contract](../skills/orchestration/references/profiles.md), and `using-herdr-sibling-panes` before routing work. Resolve repo config over shipped roles, then only keys present in the selected profile. Freeze the active owner, targets, assignments, gates, scope, strategy, and lifecycle policy. Profile assignment overrides resolve before routing; a resolved disabled gate is skipped and named in the report.

Routing comes from `assignments:`, not from this file, and the resolved YAML is the source of truth for every default — read each task's `role` and `mode` there rather than recalling one. This workflow touches implementation tracks (`complex-coding` / `simple-coding`), `test-authoring`, `fix-round-test-authoring`, `review-fixes`, `chores`, `verification`, `documentation-impact-review`, `task-review`, `fix-round-re-review`, and `final-branch-review`. A review task whose effective role binds to a list runs once per entry.
- Track extraction, integration, and final synthesis stay with the orchestrator.
Expand Down
2 changes: 1 addition & 1 deletion commands/full_cycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Do not edit workflow files unless the user's current request explicitly asks to

## Orchestration

Read `orchestration`, its [profiles contract](../skills/orchestration/references/profiles.md), and `using-herdr-sibling-panes` before routing work. Resolve repo config over shipped roles, then only composition keys present in the selected profile. Freeze the active owner, targets, assignments, gates, scope, strategy, and lifecycle policy. A profile never rewrites modes or gate enablement; a disabled gate is skipped and named in the report.
Read `orchestration`, its [profiles contract](../skills/orchestration/references/profiles.md), and `using-herdr-sibling-panes` before routing work. Resolve repo config over shipped roles, then only keys present in the selected profile. Freeze the active owner, targets, assignments, gates, scope, strategy, and lifecycle policy. Profile assignment overrides resolve before routing; a resolved disabled gate is skipped and named in the report.

Routing comes from `assignments:`, not from this file, and the resolved YAML is the source of truth for every default — read each task's `role` and `mode` there rather than recalling one. This workflow touches `plan-and-design`, `complex-coding` / `simple-coding`, `test-authoring`, `fix-round-test-authoring`, `review-fixes`, `chores`, `verification`, and every review gate from `plan-review` through `final-branch-review`. A review task whose effective role binds to a list runs once per entry.
- Separate delegated targets use reset-backed Herdr panes, even when a concrete target matches the owner's model. With a selected profile, self-target `delegate` requires a fresh in-process subagent for work and reviews, including empty reviewers; other owner-session modes permit inline work/self-review and optional subagents at the active owner's judgment. Report self-review honestly. Without a profile, keep legacy routing and fresh-subagent orchestrator-mode reviews. Workers never re-delegate.
Expand Down
Loading
Loading