菜单
Planner prompts live in goldfive. This skill redirects and describes the harmonograf-side touchpoints for planner output changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Understand and safely change heartbeat interval, stuck threshold, and timeout constants — client cadence, server detection math, frontend signal.
Add a new AnnotationKind — proto, storage, ingress RPC, optional downstream delivery to agents, frontend authoring UI, tests.
Add a new agent Capability — proto enum, client advertisement, server ingest, frontend gating in the control UI.
Add a new ControlKind — capability advertisement, client handler, server routing, ack semantics, frontend button, and tests — all the way through.
Add a new drift kind end-to-end. Goldfive owns the detector + enum; harmonograf reflects the kind through the intervention aggregator and the UI timeline.
Script a complex multi-turn FakeLlm scenario — function calls, tool chains, drift events, side-effect hooks, partial responses — for deterministic adk test coverage.
| name | hgraf-update-planner-prompt |
| description | Planner prompts live in goldfive. This skill redirects and describes the harmonograf-side touchpoints for planner output changes. |
The planner is in
goldfive. Harmonograf no
longer owns client/harmonograf_client/planner.py. Prompt changes,
schema tweaks, and refine-path logic all belong in goldfive.
If you want to change:
PlanSubmitted / PlanRevised event schema →
proto/goldfive/v1/events.proto.You only come back here if the output shape of a goldfive event changes in a way that harmonograf's ingest or frontend needs to learn about:
server/harmonograf_server/ingest.py's _handle_goldfive_event
fan-out covers run_started / goal_derived / plan_submitted /
plan_revised / task_* / drift_detected / run_completed /
run_aborted. New variants need a case; new field on an existing
variant usually just rides through in convert.py.
If the planner starts emitting a new field we want to persist
(e.g. a confidence score or plan digest), add it to
storage/base.py's TaskPlan dataclass and sqlite.py's CREATE
TABLE + conditional ALTER TABLE. See hgraf-migrate-sqlite-schema.
The frontend consumes plan shape via
frontend/src/rpc/goldfiveEvent.ts and TaskRegistry. If the new
field affects rendering — revision severity colour, banner text,
DAG layout hints — you'll need to thread it through.
Harmonograf-side planner changes are exercised by:
server/tests/test_ingest_goldfive_event.py — conversion round-trip.server/tests/test_task_plans.py — storage CRUD.frontend/src/__tests__/interventions.test.ts if the
aggregator cares.Planner prompt regression goes in goldfive's test suite. Harmonograf CI does not gate on planner output quality.
hgraf-migrate-sqlite-schema for persistence.dev-guide/server.md for the ingest dispatch.