AGENT SKILL

proactive-ticket-orchestrator

Orchestrate proactive coding agent tickets using deterministic admission gates, follow-up ownership, and serialized outbox delivery planning. Do not use for single-turn chat prompts or unauthenticated webhook injection.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
proactive-ticket-orchestrator
description
Orchestrate proactive coding agent tickets using deterministic admission gates, follow-up ownership, and serialized outbox delivery planning. Do not use for single-turn chat prompts or unauthenticated webhook injection.

02 资源文件 3

03 SKILL.md 正文

Proactive Ticket Orchestrator

proactive-ticket-orchestrator codifies the attention-minimizing proactive agent architecture distilled from deepseek-ai/dsh-superagent-prototype. It governs how external triggers (GitHub issues, pull requests, CI events, Feishu threads) are admitted, routed to isolated per-ticket Executors, and replied to without flooding human attention.

See CARD.md for the companion summary card and mandatory invariants checklist. Consult config.default.yaml for baseline operational budgets and ../agent-harness-architect/SKILL.md for harness boundary design.


1. Deterministic Admission Gate

Evaluate every incoming TriggerEnvelope against an explicit AdmissionRuleSet before invoking semantic LLM assessment:

  1. Bot Guard: Unlisted bots are dropped immediately; listed bots can at most produce inferred candidates when addressing the agent or reporting CI.
  2. Sender-Scope Matrix: Classify (listed vs unlisted, addressed vs unaddressed) into explicit, inferred, or ignore.
  3. Accept Mode Enforcement: When accept_mode == "off", all inferred candidates are dropped; when accept_mode == "record_only", inferred candidates are logged without dispatching side effects.

Completion criterion: Every trigger receives a deterministic GateOutcome with policy_version recorded.


2. Follow-Up Ownership & Mandate Routing

Prevent duplicate tickets and authority creep on active threads:

  1. Executor Follow-Up Ownership: Human replies on a Thread with active/resumable Ticket subscriptions route directly to those Ticket Executors (deliver_to_ticket), bypassing fresh Eval.
  2. Restricted Main-Session Control: While an Executor owns a follow-up, the Main Session may only stop work; accept, attach, and ignore are refused.
  3. Single Hand-Back: An Executor may hand back an out-of-scope follow-up once, releasing it to fresh Eval.

Completion criterion: Trigger routed deterministically to deliver_to_ticket, queue_eval, or drop_ignored.


3. Serialized Outbox Delivery Planning

Order outbound replies per (ticket_id, channel_id) lane without claiming atomic DB/outbox commits:

  1. Deterministic Sequence Ordering: Partition pending OutboxReplyItem payloads by (ticket_id, channel_id) lane and sequence order so acknowledgements precede results while unrelated tickets proceed in parallel.
  2. Per-(Ticket, Channel) Serialization: Hold items behind an in-flight lane in blocked_behind_head while emitting the lane head in ready_to_send.

Completion criterion: Outbound replies partitioned into ready_to_send and blocked_behind_head lanes.


The Three Foundational Pillars

1. Attention-Cost Minimization

Confirm once, stay silent while executing, ask one concrete structured question at a time, and stop by impact rather than effort.

2. Deterministic Gate Before Semantic Eval

Never let untrusted message bodies or prompt injections override allowlists, bot guards, or Mandate scope.

3. Synchronous State, Asynchronous Effects

Commit domain transitions synchronously and drain external Assessor, Executor, and Outbox side effects post-commit.


Anti-Patterns

  • Unbounded Bot Fan-Out — Treating bot comments or CI webhooks as explicit requests instead of capping them at inferred candidates.
  • Follow-Up Split-Brain — Running fresh Eval on a human reply already owned by a live Ticket's Executor, spawning duplicate tickets.
  • Outbox Race Inversion — Sending a final result or error before the Ticket's acknowledgement on the same conversation lane.
  • Monolithic Prompt Questions — Burying blocking design questions inside long markdown reports instead of emitting one structured Attention field.

04 同仓库更多 Skills

SpectreDeath
SpectreDeath/Brain-Harness

ui-behavior-primitive-architect

Architect, audit, and verify zero-dependency headless UI behavior primitives, WebMCP agent bridges, WAI-ARIA/SSR/RTL tri-modal checks, and framework expert routing. Do not use for static CSS theme styling or backend database migrations.

★ 0
SpectreDeath
SpectreDeath/Brain-Harness

trustgraph-ontology-governor

Govern knowledge graphs, SHACL-AF triple policies, OntologyRAG subclass validation, PROV-O dual named graphs, and Laya entropy decision scoring. Do not use for relational SQL queries or generic web scraping.

★ 0
SpectreDeath
SpectreDeath/Brain-Harness

shim-harness-governor

Govern universal CLI agent loops, 4-tier tool permissions, ancestor-symlink workspace sandboxes, deterministic-first command routing, collision-safe MCP namespacing, and layered skill loading. Do not use for static UI styling or external SQL analytics.

★ 0
SpectreDeath
SpectreDeath/Brain-Harness

graphiti-zep-memory-governor

Govern bi-temporal knowledge graphs with Graphiti future-edge clamping, MinHash/LSH entity dedup, RRF/MMR reranking, and Zep typed ontologies. Do not use for static SQL joins or generic web crawling.

★ 0
SpectreDeath
SpectreDeath/Brain-Harness

agora-mcp-workbench-architect

Architect, audit, and orchestrate Agora Workbench MCP servers, loopback sidecars, unified state graphs, gateway/dispatcher connectors, and policy-enforced data lakes. Do not use for static frontend CSS styling or non-MCP desktop GUI automation.

★ 0
SpectreDeath
SpectreDeath/Brain-Harness

skill-eval-assurance-runner

Evaluate and assure agent skills using small-N Wilson confidence intervals, unbiased pass^k reliability, deterministic trajectory graders, preflight boundary honesty, and sealed digest verification. Do not use for subjective prose review or unconstrained production deployment.

★ 0