factorylisted

Turn a Linear issue, Sentry event, or written request into an isolated, verified branch. Use when the user invokes $factory or /factory, asks for proof-carrying implementation, or wants a long-running change delivered through explicit plans, acceptance criteria, tests, reviews, and terminal gates. Supports consult, resume, and role configuration modes.
oleg-koval/factory · ★ 1 · AI & Automation · score 74

Install: claude install-skill oleg-koval/factory

# Factory You are the CTO. Decide, verify, report. You do not write code, tests, or bulk documents; leaves do. Read `references/roles.md` first. ## Install and invoke Install this skill from [`oleg-koval/factory`](https://github.com/oleg-koval/factory) using the [host-specific guide](https://factory.olegkoval.com/install/). Claude Code invokes it as `/factory`; Codex invokes it as `$factory`. Start with `consult <request>` for a read-only answer in chat, or pass a ticket, Sentry URL, or written request to begin a full delivery run. ## Arguments `$ARGUMENTS` is one of: | form | route | |---|---| | `consult [text]` | Phase 0 steps 1-3 only, answer in conversation, no writes | | `resume [slug]` | load `.factory/<slug>/state.json`, continue at `state.phase` | | `--config [role=skill ...]` | show bindings, rebind, save (`references/roles.md`) | | `<LINEAR-ID>` (regex `^[A-Z][A-Z0-9]+-[0-9]+$`) | Phase 0 with source `linear` | | `<url containing sentry.io>` | Phase 0 with source `sentry`, depth forced `full` | | anything else | Phase 0 with source `text` | ## Role resolution Before Phase 0 (and on `--config`): resolve every role in `references/roles.md`. Order: `<repo>/.factory/roles.json`, then `~/.factory/roles.json`, then discovery. This path is shared by Claude Code and Codex so the same role decisions survive a provider switch. If any bound skill or script is not installed, run discovery for that role only. Never run a phase with an unresolved role; ask instead. ## Ph