Skip to content

greenfield: in Pane, ask and relay the way the pane skill says; workers pass their status file - #211

Draft
tbrownio wants to merge 1 commit into
mainfrom
approvals-system
Draft

tbrownio wants to merge 1 commit into
mainfrom
approvals-system

Conversation

@tbrownio

@tbrownio tbrownio commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This is the Agent Farm package (P2) of the approvals-system plan. Pane's generated approvals text, its "Asking the person in Pane" section, becomes the only place that says how an agent asks inside Pane. Agent Farm stops giving its own Pane asking rules. It keeps needs_you, the Q-n and D-n numbering and the interview method, and points to the pane skill everywhere else. The Pane side is being finished in a separate Pane PR.

What changed (greenfield 0.0.52)

  • Standing rules, Questions for the person. Pane-specific card rules are replaced by one pointer: "In Pane, ask and relay the way the pane skill says". A Session worker now reports blocked with its status file, runpane report --state blocked --question "Q-n: <title>" --summary-file <status file>. This undoes greenfield: blocked workers report the question and its options, not the status file #205's ban on passing the status file. That ban existed only because raw JSON showed on cards, and Pane #1298 fixed that: Pane now builds the card from needs_you. The literal-argument quoting rule stays. Standalone agents in Pane follow the pane skill's which-card rule; AskUserQuestion stays the rule elsewhere.
  • needs_you shape. It gains a top-level why, one or two sentences of at most 240 characters, which becomes the card's subtitle, and an optional summary path to an .html Summary page. Both are in the JSON example and the field list. title is documented too.
  • relay.md. In Pane, relaying a worker's question always uses runpane notify --relays <item>, never AskUserQuestion. Outside Pane the relay is unchanged.
  • Interview skill. In Pane it follows the which-card rule. Interview rounds whose answers are recorded go to an approval card, and a quick clarification may use Claude's own card.
  • greenfield/orchestrator in Pane. coordination.md and orchestrate-sessions now say that in a Pane Session the orchestrator follows Pane's bundled orchestrate-sessions, the one the Session's pane-orchestrator guide loads. From Greenfield's skill it takes only roles, bundles and document destinations, review policy and validation levels. Outside a Pane Session, Greenfield's skill applies in full.
    • Limitation: a profile can't choose its skills by host. The compiler has no host-conditional skill field. So the profile still ships Greenfield's orchestrate-sessions on every host, and in Pane the precedence is set by these instructions, not by the loaded skill list.
  • The plugin README is updated to match, and a J9 test covers the pointer, --summary-file, why/summary, --relays, the interview rule and the orchestrator split. The test also checks that the standing rules don't restate Pane's card rules.

bigbrain's pinned copy of interview is left as it is; it's pinned on purpose. No profile files were edited.

Checks run

  • pnpm typecheck: pass
  • pnpm test: 348 pass, 0 fail, 9 skipped
  • node scripts/install-smoke.mjs: pass
  • node dist/cli.js plugin validate plugins/greenfield (temp HOME and --config-root): pass
  • node scripts/sync-bigbrain-from-greenfield.mjs --check: copies and checksums current

Validation deferred: CI, QA and review not yet run.

Not published: the plugin and npm package aren't released, and no machine's plugin copy has been refreshed.


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

…rs pass their status file

Standing rules, relay.md, coordination, orchestrate-sessions and the interview
skill point to the pane skill's "Asking the person in Pane" section instead of
restating Pane's card rules. A Session worker reports blocked with
--summary-file <status file> again (undoing #205's ban, which #1298 made
unnecessary), relaying in Pane always uses runpane notify --relays, and
needs_you gains a top-level why (the card's subtitle) and an optional summary
page. In a Pane Session the orchestrator follows Pane's bundled
orchestrate-sessions and takes only roles, bundles, review policy and
validation levels from Greenfield's.

Bumps greenfield to 0.0.52.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant