AGENT SKILL

bubbles-workflow-execution-loops

Run per-round synchronous workflow execution loops correctly. Use when orchestrating a multi-round workflow, dispatching specialist subagents, handling round-based remediation, or interpreting a workflow mode's execution policy. Covers authorized direct execution, dispatch-and-wait, batch-then-summarize prohibition, and mapped-mode execution.

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

01 前言 Front Matter

name
bubbles-workflow-execution-loops
description
Run per-round synchronous workflow execution loops correctly. Use when orchestrating a multi-round workflow, dispatching specialist subagents, handling round-based remediation, or interpreting a workflow mode's execution policy. Covers authorized direct execution, dispatch-and-wait, batch-then-summarize prohibition, and mapped-mode execution.

03 SKILL.md 正文

Bubbles Workflow Execution Loops

Goal

Execute workflow modes round-by-round with synchronous dispatch-and-wait, no report-only sweep completion, and no batch-then-summarize shortcuts.

When to use

  • Orchestrating any workflow mode that runs rounds (full-delivery, stochastic sweeps, fix-cycle, finding-driven loops)
  • Dispatching specialist subagents and waiting for their RESULT-ENVELOPE
  • Executing a mapped mode directly from the active authorized runner
  • Reading a workflow mode definition to understand its loop policy

Non-negotiables

  1. Synchronous dispatch-and-wait per round. The orchestrator dispatches one (or a small batch of) specialist agents, waits for each terminal envelope, processes findings, and then decides the next round. Batch-then-summarize is forbidden.
  2. Mapped-mode execution. When a trigger has a mapped workflow mode, the active runner resolves and executes that contract directly. Do not run only the trigger phase.
  3. Wait for mapped-mode terminal envelope. Before the runner advances, every mapped mode phase owner's terminal result must be in run state.
  4. No report-only sweep completion. A sweep that emits only a summary without round-level mapped-mode execution is incomplete; the workflow agent rejects this shape.
  5. No runner nesting. Workflow execution occurs only in the authorized top-level runner. It invokes specialist phase owners directly and records executionModel: direct-authorized-runner.

Authoritative modules

  • agents/bubbles_shared/workflow-execution-loops.md — full per-round protocol
  • agents/bubbles_shared/workflow-fix-cycle-protocol.md — fix-cycle round semantics, finding-set closure
  • agents/bubbles_shared/workflow-orchestration-core.md — dispatcher contract
  • agents/bubbles_shared/workflow-delegation-core.md — natural-language routing + work selection ownership
  • bubbles/workflows/modes.yaml — per-mode loop policy (requiredGates, phaseRelevance, triggerWorkflowModes)
  • bubbles/workflows.yaml — execution options + gate/phase wiring (resolver composes both files)

04 同仓库更多 Skills

pkirsanov
pkirsanov/smackerel

smackerel-trace-capture

Wire Smackerel's concrete validate-plane stack into the framework trace-driven defect-discovery method. Use when running live-category tests (integration/e2e/e2e-ui/stress) against the ephemeral test stack; capturing SLO or trace evidence; hunting latency/error/perf bugs from spans; querying the test-stack Jaeger or Prometheus; or touching `.specify/runtime/observability`. Concrete smackerel endpoints + the exact `capture-slo.sh` command; do NOT duplicate `bubbles-observability-adapter` — this only adds the wiring.

测试与质量
★ 1
pkirsanov
pkirsanov/smackerel

smackerel-no-defaults

Enforce Smackerel's NO-DEFAULTS / fail-loud SST policy. Use when editing config, Docker Compose, deploy adapters, docs, instructions, skills, env handling, host bind addresses, or any runtime value that could be hidden by fallback syntax.

运维与部署
★ 1
pkirsanov
pkirsanov/smackerel

bubbles-workflow-mode-resolution

Resolve a Bubbles workflow mode against `bubbles/workflows.yaml`, including template inheritance, status ceilings, gate wiring, and decision policy. Use when picking a mode for a request, when a guard reports a mode-related failure, or when extending workflows.yaml with a new mode or template. Covers natural-language intent routing and the workflow registry consistency rules.

Skill与智能体开发
★ 1
pkirsanov
pkirsanov/smackerel

bubbles-vscode-agent-constraints

Design agents that fit the VS Code Copilot Chat runtime instead of fighting it. Use when authoring or editing any `*.agent.md`; when adding `tools:`, `agents:`, `handoffs:`, `model:`, `user-invocable:`, or `disable-model-invocation:` frontmatter; when designing an orchestrator that dispatches specialists; when a design implies agent-calls-agent-calls-agent chaining; when a subagent dispatch silently no-ops or an agent cannot be selected in the dropdown; or when writing a governance rule about delegation that the runtime cannot actually enforce. Prevents multi-level-subagent designs, prose-only dispatch laws, and frontmatter/body contradictions.

视觉设计Skill与智能体开发
★ 1
pkirsanov
pkirsanov/smackerel

bubbles-upkeep-cadence

How to schedule, dispatch, and record recurring operational upkeep tasks (backup, restore-drill, BCDR-drill, patch-cycle, secret-rotation, flag-cleanup, compliance-sweep). Use when authoring or modifying `config/upkeep-calendar.yaml`, when investigating a missed task, when reading the upkeep ledger, or when adding a new task type.

★ 1
pkirsanov
pkirsanov/smackerel

bubbles-test-integrity

Enforce real, specification-driven test quality during any test work. Use when writing tests, implementing scope test plans, reviewing test coverage, or validating DoD test items. Triggers include writing tests, adding test coverage, implementing scope tests, reviewing test plans, marking test DoD items, and verifying Gherkin scenario coverage.

内容创作者测试与质量写作与文案
★ 1