跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

browser-game

Turn an incomplete browser-game brief into evidence-bound checkpoints and standard-stamped successor delivery.

DanMcInerney · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add DanMcInerney/orchflows --skill browser-game

技能说明


name: browser-game description: Turn an incomplete browser-game brief into evidence-bound checkpoints and standard-stamped successor delivery. disable-model-invocation: true

Require: one incomplete product request as brief, and workspace, the git-backed product repository — the only invocation inputs. Missing fields never become defaults: an empirical gap becomes a declared experiment, a kind: user-only gap one verbatim question for the root to relay, and neither blocks the other.

tickets.py frame-open <run> --goal-file <program-goal> --workflow browser-game

Record, do --standard orch-content --isolation required: one versioned program record in workspace for brief, conforming to its program-record schema and intake-authority policy. Each Q-01–Q-12 field is recorded independently with its disposition, authority kind, owner, rationale, evidence and revision; each omitted material field carries a stable open-question or decision identity; a settled decision keeps its revision and invalidation trigger. browser_game_validate.py runs against it before filing.

Evidence, do --standard orch-research handed the record's artifact line: one fixed evidence packet for the independently schedulable empirical fields affecting the record's next transition. Each experiment matches its source field's open decision_id, predeclares every required field and settles only its matched cells. Negative, null and inconclusive results stay visible; a control or experiment without the policy's complete recorded trigger identity stays inactive.

Checkpoint, one judge --standard orch-content over both artifact lines: exactly one disposition — advance, revise, experiment, user-decision-required or stop — bound to its governing requirement, the fixed record revision and evidence identity. Its findings validate against the checkpoint contract. Only where that disposition is lawful does one further do --standard orch-content materialize the standard-separated successor plan, each ordered entry preserving its artifact identity, artifact kind, matching standard, run/root identities, dependencies and planned/opened status.

Never: invent a stack, cohort, support promise, budget, fallback, provider or release policy; settle a user-only field from evidence or paraphrase its question before relay; represent absence as agreement or overwrite a settled decision; infer advance from task completion; open a successor whose kind, standard, predecessor identity, dependency or root identity is unresolved; hide one artifact kind behind another's identity; or file anything the instance validator rejects.

Return: tickets.py frame-close <run> <frame> --done <check> on the terminal checkpoint — record and evidence identities, disposition, open question or successor identities and the invalidation boundary, all observable without historical input.