dark-factory

dark-factory — one pattern, two modes

This skill runs the Dark Factory GitHub-orchestration pattern. There is one command, two modes — pick by how the human participates:

Both modes are the same conceit — issues flowing through dev → review → merge behind GitHub-native gates — at two autonomy levels. Don't blend them in one run.

Always do first (both modes)

1. Read config/team.json — repos, your identity (.self.github), roster (.members), board (.board), base branches (.base_branches), policy, and the autonomous-mode constants (.board.project_id / .status_field_id / .status_options, .autonomous.*). scripts/lib.sh exposes most of it to the shell.
2. Credential & scope preflight — run bash scripts/preflight.sh <autonomous|interactive> and read the report before doing any work. It proves, by making real read-only API calls (not by trusting declared scopes), that gh is authenticated and the token actually has the capabilities this run needs: repo write on every .repos repo, Projects v2 access for board moves (autonomous), webhook admin for the listener, and the opt-in teams CLI when comms are on. gh auth login's default scopes include neither project nor admin:repo_hook, so board moves and webhook registration fail silently without it. If it prints RESULT: FAIL, STOP and give the user the exact remediation it emits (usually a gh auth refresh -h github.com -s … line) — do not boot the factory on credentials that don't work. RESULT: OK (with warnings) is safe to proceed; each ⚠ has a documented fallback — note them in your summary.
3. source scripts/lib.sh — gives you REPOS, base_branch <repo>, notify_all / notify_subset / notify_user, request_reviews.sh, webhook helpers.
4. Read reference/budget.md — the REST-vs-GraphQL rate discipline. It governs every gh call in either mode; the factory has run the GraphQL pool to zero before. Not optional.
5. Read reference/verification.md — the Iron Law: no completion claim ("done / green / passing / clean") without fresh verification evidence. It governs every board move, agent report, and gh pr create / merge / approve, and is enforced at the PR boundary by the verify-before-completion hook.
6. Worktree discipline (any code change): one worktree per task at /tmp/wt-<issue>, branched off fresh origin/<base>, its own dependency install; never work in the main checkout; remove it after merge. (Full rules in the mode docs.)