← ClaudeAtlas

swfactorylisted

Drive the Airflow software factory from any AI coding harness through the swf CLI. Use for Codex, Claude Code, Grok, Cursor, OpenCode, custom agents, or another outer harness that should submit, inspect, gate, and verify governed work without becoming a second scheduler.
zozo123/ariflow-swfactory · ★ 1 · AI & Automation · score 72
Install: claude install-skill zozo123/ariflow-swfactory
# Software Factory The AI harness is the entry point. `swf` is its control surface. Apache Airflow is the only lifecycle scheduler. Factory Cells own durable issue x target identity and epoch fencing. Sandboxes are disposable execution. The factory owns publication. Install this skill with any skills.sh-compatible harness: ```bash npx skills add zozo123/ariflow-swfactory --skill swfactory ``` ## Outer harness mode Use one stable session pair `(harness, factory_id)` for the lifetime of the outer agent session. Different harness processes or independent sessions use different factory ids, even when they drive the same repository. ```bash swf doctor swf submit --harness codex --factory-id codex-session-17 --issue 1203 swf submit --harness claude --factory-id claude-session-22 --issue 1205 swf runs list swf cells list swf attention ``` The convenience wrapper is equivalent: ```bash scripts/swf_harness.sh <harness> <factory-id> --issue <issue> [submit args...] ``` ### Rules - Reuse the exact session identity on retries so submission dedupe is deterministic. - Many sessions may submit different issue x target Cells against the same repository concurrently. - The same issue x target Cell has one writer. A competing session must be queued, fenced, or refused. - Never invent stage transitions in the harness. Airflow schedules spec, plan, build, test, review, approval, delivery, and cleanup. - Never pass backend, GitHub publication, or service credentials into stage sandbox