arcane-scaling-benchmarks

How work flows through the Arcane repos — when to file an epic vs a standalone issue, how epic branches work, how sub-PRs route, who merges what, and how agents log decisions for the founder's final review. Apply when filing any issue or PR, when deciding which branch to target, when reviewing/merging, and when implementing a sub-issue of an epic.

Cloud worker that picks up a single GitHub issue and turns it into a single pull request. Triggered by GitHub Actions on `issues:[labeled]` with `claude-ready`, gated by either sender = `martinjms` (standalone path) OR the issue carrying `claude-working` (orchestrator dispatch path). Use this skill whenever the worker workflow fires; it's invoked via `/arcane-worker` from `.github/workflows/claude-issue.yml`. Determines mode automatically — fresh PR creation, continuing an existing PR with new retry guidance, or posting a BLOCKER on the parent epic PR — based on issue body and current PR state.

Central dispatcher and reviewer for an Arcane epic's sub-issues and sub-PRs. Triggered by GitHub Actions on labeled/unlabeled issues, opened/closed/synchronized PRs, submitted PR reviews, and created issue comments — but only when the event touches an active epic (epic issue or epic PR carries `orchestration-active`, OR sub-issue carries `claude-working`/`action-required`, OR PR base is an `epic/*` branch). Reads GitHub state, identifies which of 11 situations matches, executes that situation's playbook via `gh` CLI, and exits. **One decision per invocation. Stateless across invocations.** Use this skill whenever the orchestrator workflow fires; the workflow YAML invokes it via `/arcane-orchestrator`. Standalone (non-epic) issues are explicitly out of scope — those go through arcane-worker directly.

How to store, organize, retrieve, and collect information in the arcane-vault knowledge base. Covers the 4-layer progressive-disclosure structure, canonical vocabulary, entity authoring rules, the GLOSSARY-based term resolution protocol, and the daily vault-builder collection process. Apply when reading from or writing to the vault, when documenting architecture or decisions, and when running the daily vault collection agent.