evanflow

Load the EvanFlow vocabulary and guide evanflow-* skill invocation.

417|18|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/evanklem/evanflow --skill evanflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evanflow
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies how to initiate and govern the EvanFlow loop by loading the shared vocabulary and directing which evanflow-* skill to invoke, ensuring consistent language and user-controlled progress.

Core Features & Use Cases

  • Loads the unified EvanFlow vocabulary (terms like Module, Interface, Depth, Seam, Grill) to ensure shared understanding across skills.
  • Describes exactly when to invoke each evanflow-* skill, guiding users through brainstorming, planning, execution, and iteration.
  • Acts as the conductor for the full loop, enforcing checkpoints and the no-auto-commit/no-auto-finish policy.

Quick Start

Say 'let's evanflow this' to begin the full loop with evanflow-go.

Frequently Asked Questions about evanflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is TDD orchestration and how does it manage a development loop?

TDD orchestration coordinates a development loop by loading shared vocabulary and directing which execution skill to invoke, ensuring consistent language and user-controlled progress across brainstorming, planning, and iteration phases.

How do I start a new TDD task when I am unsure which execution skill applies?

To start a new TDD task, invoke the orchestration skill to load the unified vocabulary, receive grounding guidance, and determine the correct execution skill for your specific brainstorming or planning phase.

Does the EvanFlow orchestration loop auto-commit code or auto-finish tasks?

The orchestration loop does not auto-commit code or auto-finish tasks. It enforces a strict governance policy requiring explicit user direction and manual approval before any git operations are executed.

How does shared vocabulary governance work across multiple TDD orchestration skills?

Shared vocabulary governance works by loading unified terms like Module, Interface, Depth, Seam, and Grill to ensure shared understanding across skills, providing grounding and clear handoffs during execution.

Can I use this orchestration skill to enforce checkpoints during software execution?

You can use this orchestration skill to enforce checkpoints during software execution. It acts as a conductor for the full loop, managing handoffs and ensuring user-controlled progress throughout the task lifecycle.