enekesabel/dev-flow

Perfil de enekesabel

Última actividad de origen registrada: 19 de octubre de 2026 a las 12:47

Catálogo de SkillsMP actualizado: 26 de octubre de 2026 a las 11:37

skills recopiladas: 3

Estrellas en GitHub: 2
Forks en GitHub: 0

README del repositorio

Archivo de origen del README: README.md

Leer el README original

Mostrar README completo

## What is DevFlow DevFlow is a set of behavioral instructions and skills that let engineers concentrate on what matters: being there for the **Decisions** that matter, while leaving the busywork to agents. It's constantly evolving as I learn what works and what doesn't. ## Motivation ### Divergence and Convergence Every piece of work moves between **Divergence** and **Convergence**. Divergence explores: trying things, investigating, prototyping what could work. Convergence decides: collapsing what you found into commitments you'll defend over time. With agents, Divergence costs almost nothing, so the work can expand faster than you can converge it, and Decisions start getting made without you. ### Flow **Flow** is the state of being present in the work: challenged but clear, each move connected to the next. Every move opens **Tension**, a gap between what exists and what could be. Working alone, you feel when it's too much to hold and you converge: name something, delete a path, write a test. Agents don't feel that. The Tension builds out of sight and comes back as a review full of Decisions you weren't there for, with context you now have to reconstruct. ### Staying in the Loop DevFlow is an attempt to keep you in the loop on the things that matter to you, and to make sure you get informed when an agent diverges from what you agreed. ## How it works DevFlow assumes you work with two kinds of agents: **Coordinators** and **Workers**. One kind you talk to, the other you don't. Coordinators don't build, and DevFlow applies only to them. Their responsibility is aligning with you, handing the work out to Workers, and checking the work they've done. Use smart models for Coordinators. Coordinators keep a **Ledger** of **Proposals** and Decisions, separating what came from you, what came from agents, and what came from external sources. They also pay attention to how engaged you are in each topic. Where you're involved, they keep you in the loop. Where you don't seem involved, or you've delegated the Decisions, they don't bother you unless something touches what you own. Before sending a Worker a **Brief** (a spec, a plan, whatever your workflow dictates or you ask for), they align with you on the open Proposals that must be resolved to make the Brief complete. They don't bother you with what's already settled or what doesn't need your attention. Once the work is done, the Coordinator checks it against the agreed Brief and points out where the Workers diverged, so you're aware and can course correct. ## What DevFlow isn't DevFlow isn't an agent coordination framework or SDLC loop. Coordinators delegate through whatever mechanism you already use, and DevFlow plays well with other skills (for example [Matt Pocock's](https://github.com/mattpocock/skills)) and frameworks like [OpenSpec](https://github.com/Fission-AI/OpenSpec). It's just a behavioral layer that keeps your agents aligned and doesn't dictate how you work. ## Install In Claude Code: ``` /plugin marketplace add enekesabel/dev-flow /plugin install dev-flow@dev-flow ``` Installing changes nothing in an ordinary session. DevFlow is only active when you start it. ## Start DevFlow ``` claude --agent dev-flow:devflow ``` Or pick the `dev-flow:devflow` output style (`/output-style dev-flow:devflow`, or the session's Output style menu in the desktop app). To make it the default, set `"outputStyle": "dev-flow:devflow"` in `~/.claude/settings.json`. ## Skills DevFlow comes with a set of skills: some apply to DevFlow only, others work on their own and bring software development best practices. A Coordinator may invoke any of them automatically while you work with it. Outside DevFlow, you have to invoke them explicitly. | Skill | Use it for | Outside DevFlow | | --- | --- | --- | | [system-architecture](skills/system-architecture/README.md) | Documenting a system's architecture, with evidence, and drawing it as a diagram that switches between environments. | `/dev-flow:system-architecture` | | [use-skill](skills/use-skill/README.md) | Letting agents run skills only you can invoke, when you name them in plain words or in a handoff. | Works on its own: name the skill | | [recall](skills/recall/SKILL.md) | Restoring what you and the Coordinator agreed, after compaction or a resumed session. | DevFlow only | ## What's coming next - **software-design**: how your system manifests in code: modules, layers and how they're organized. - **test-design**: tests that protect one clear requirement, at one level, through the right seam, and change only when that requirement changes. Star the repo or follow me on X at [@enekes_abel](https://x.com/enekes_abel) for updates.

Cargando el README del repositorio…

Publicaciones

Ver todos →

Ábel Énekes

@enekes_abel19 oct 2026 16:22 UTC

Anuncio de un SkillCoordinar tareas entre agentes

Resumen de la publicación · inglés

use-skill lets you name a skill in plain words and have the agent run it like a slash command, keeping skills user-invoked and clarifying ambiguous matches.

Publicación original

Ver detalles del Skill · dev-flow/skills-use-skill

Skills en este repositorio

clasificación pendiente

skill

ocupación

descripción

actualizado

recall

sin clasificar

Use when you are the DevFlow Coordinator and the Ledger is missing or incomplete in your context: after compaction, on resuming a conversation, or when it feels thin. Otherwise use only when explicitly told to.

Idioma del texto original: inglés

2026-10-19

system-architecture

sin clasificar

Use when you are the DevFlow Coordinator and the conversation turns to a software system's architecture: identifying it, discussing it, or documenting it (what its boundary is, what runs inside it, where it runs, how its parts communicate), or when writing,…

Idioma del texto original: inglés

2026-10-19

use-skill

sin clasificar

Use when the user tells you to use a skill, by its name, its author or what it does, that is not in your list of skills, before you try to invoke it. Also when a listed skill shares a word with the one they named but their wording, such as an author, points…

Idioma del texto original: inglés

2026-10-18

Mostrando 3 de 3 skills recopiladas.

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/enekesabel/dev-flow.