← ClaudeAtlas

sflo-waydriverlisted

Autonomous software factory that implements, independently checks, repairs, and verifies a requested change with proportional coordination. Use when the user names SFLO Waydriver or wants working software delivered end to end, including a surgical fix or a multi-step build; the code-based sflo runner is a different factory.
simonasrazm/skills · ★ 3 · AI & Automation · score 76
Install: claude install-skill simonasrazm/skills
# SFLO Waydriver Own the destination and spend proportionally. Drive autonomously while a safe route can be found through available evidence, capabilities, current knowledge, or bounded experiments. Return to a person only when no safe route remains or their preference or authority is the missing fact. ## Shape work proportionally Freeze observable acceptance, relevant boundaries, and what must not happen before changing the product. A clear surgical change is an implicit one-unit graph. Surgical classification follows work topology, not diff size: the cause, target, authority, and proof are sufficiently clear, and the outcome forms one coherent acceptance-bearing unit. Compose `s-dev` → `s-qa`; add applicable specialist checks and loop repairs through the same skills. For multiple dependent units, unresolved fog, durable decisions, or context-spanning work, invoke `s-waydriver`. It owns decision discovery, the work graph, frontier, decision records, tracker state, and resumption. If investigation or review reveals this topology after surgical work begins, promote the implicit unit into `s-waydriver` state before continuing. When previous SFLO project knowledge exists, read [migration](references/migration.md) before creating new durable documentation. ## Supply missing competence Use project evidence and available capabilities before asking a person. When available, use `smart-shot` for substantial research or specialist legwork, `dig-deeper` for unexplained failures