polly-e2e-devlisted

End-to-end test the polly multi-agent coding orchestrator's critical user journeys (CUJs). Two halves — a deterministic mock-LLM driver (polly_cuj.py) that boots a throwaway local server + mock LLM and asserts the substrate (boot, bridged sys_* tool dispatch, the blast_radius / spawn_bounds / headless_subagent_purpose_guard guardrails, fan-out delegation), and a live real-CLI recipe (real claude/codex/pi, real worktrees/PRs) for polly's actual judgment. Load when developing, testing, or debugging examples/polly — its config.yaml, the claude_code/codex/pi sub-agents, the investigate/fanout/cross-review skills, or the omnigent.inner.nessie.policies guardrails — or reproducing a polly orchestration bug.
sarptandoven/doppl-multiplayer · ★ 0 · Testing & QA · score 65

Install: claude install-skill sarptandoven/doppl-multiplayer

# polly orchestrator: end-to-end CUJ dev & testing `polly` (`examples/polly/`) is a multi-agent **coding orchestrator**: a `claude-sdk` "brain" that writes no code itself and delegates everything to three coding sub-agents — `claude_code` (claude-native), `codex` (codex-native), and `pi` (headless, multi-model). Its critical user journeys are orchestration behaviors, not single-turn answers: - **roster preflight** — first turn runs `command -v claude codex pi`, routes only to workers whose CLI resolved. - **investigate** — read-only work fanned to `explore`/`search` sub-agents; synthesize from their reports. - **fanout** — independent tasks, each in its own git worktree + sub-agent, each opening its own PR. - **cross-review** — an implementer's diff is verified by a **different-vendor** sub-agent (diff + contract only); blocking issues become fix-tasks. - **plan gate / inbox** — pull the human in at the plan gate; supervise via the inbox + autowake, never busy-poll. - **guardrails** (`omnigent.inner.nessie.policies`) — `blast_radius` (deny force-push / `rm -rf /`), `spawn_bounds` (cap dispatches per turn), `headless_subagent_purpose_guard` (every dispatch needs `args.purpose`). This skill tests those CUJs two ways. Use **both** — they cover different things: | Half | What it proves | Needs | |------|----------------|-------| | **Mock loop** (`polly_cuj.py`) | The **substrate/mechanics** — the brain is *scripted*, so this proves bundle load, server-side polic