addyosmani/factory

Factory Implement claims one ready GitHub issue, applies fail-closed gates, and uses an independent verifier before opening a draft pull request. Use it when you want a controlled issue-to-PR workflow with fresh verification context.

Factory Implementation claims one ready GitHub queue item, implements it end to end, runs gates and independent verification, then opens a draft PR. Use it for a single ready-to-implement issue or the implementation routine.

Factory Monitor inspects factory health, stale work, CI, security advisories, and recent run evidence without implementing fixes. Use it to review system status and write a unique run record.

Factory Monitor runs scheduled checks for CI failures, gate health, dependency advisories, queue staleness, and documentation drift. Use it for nightly or weekly monitoring that files issues and writes a run record.

Factory Spec turns an ambiguous factory issue into human-approved product, behavior, design, and implementation slices. Use it interactively before implementation and keep approval gates in the loop.

Factory Spec turns a ready-to-spec queue item into an approved plan through four human review gates. Use it when scope must be decided before code exists, such as for a feature, migration, or other interactive planning task.

Factory Status shows the factory control room from live GitHub labels, open PRs, recent run records, gate health, and charter limits. Use it when you need a current readout without changing any work.

Factory Triage classifies GitHub issues into the factory’s live label queue and writes an auditable snapshot. Use it for backlog triage or a scheduled triage run.

Factory Triage classifies incoming issues into a labeled queue, tries cheap reproduction, and writes an auditable QUEUE.md snapshot. Use it when sorting backlog items, running scheduled triage, or deciding what the factory should pick up next.

Factory Tuning reviews factory evidence and suggests tighter or looser constraints without changing the charter. Use it for periodic constraint reviews and to record accepted human decisions.

Factory Verify independently checks a factory pull request, including fail-closed gates, negative test proof, scope, and load-bearing review. Use it when you need to verify changes against the factory contract and charter.

Factory Verify checks an open factory PR before human review by rerunning gates, proving the test fails without the fix, and checking scope and test tampering. Use it when verifying a PR or independently reviewing a change.