dyflolisted

Repository-agnostic hybrid dev loop. Routes an incoming ticket (GitHub Issue, Jira, or any adapter) into one of two lanes by label: an AUTONOMOUS lane (small/mundane work → the dyflo-watcher runs it headless, one-ticket-one-PR-exit) or a HITL lane (big/risky work → a research stage computes blast radius and picks an architecture pattern, emits a draft ADR you approve, then TRIP plans/implements/releases with human gates). Use when the user says "dyflo", "assign this ticket", "research this issue before I plan it", "route this ticket", "set up the hybrid agent loop", "run the research stage", or wants the launcher that turns on assign-or-do-it-yourself. The research stage is the core: it fuses Graphify blast radius + the vendored pattern catalog and MAY conclude "no pattern needed" — downgrading a small ticket straight to the autonomous lane with zero ceremony. Non-goals: it does not merge PRs, does not schedule cron/launchd, and never escalates a small ticket into unattended execution — the research stage onl
Amanuel2x/dyflo · ★ 0 · Code & Development · score 70

Install: claude install-skill Amanuel2x/dyflo

# Dyflo — hybrid autonomous + HITL dev loop (`/dyflo`) One entry point wraps any repo. From it you either **assign** work (hand off a ticket, the system routes it) or **do the work yourself** (an interactive session with Graphify + ponytail + TRIP loaded). Small work runs headless; big work runs through research → your approval → TRIP. ``` ticket → adapter → ROUTER (by label) ├── label:auto ───────────────► AUTONOMOUS LANE (watcher: 1 ticket → PR → exit) └── label:hitl / unlabeled ───► RESEARCH STAGE (this skill's core) │ no pattern needed → relabel auto ─┐ ▼ │ draft ADR → 👤 approve → /TRIP-1-plan …│ ▲───────────────────────────────────┘ ``` ## The lanes | Lane | Label | Who runs it | Human gate | |------|-------|-------------|------------| | Autonomous | `auto` | `dyflo-watcher`, headless `claude -p` | none (PR only; a human merges — run `/code-review <pr#>` first, plus `/security-review` if the diff touches auth/secrets/validation) | | HITL | `hitl` / unlabeled | research stage → TRIP | ADR approval, plan, diff | The router **only downgrades** (research may relabel `hitl`→`auto`). It never auto-escalates a small ticket into unattended execution. That is the one safety invarian