evanflow-go

Orchestrate EvanFlow loops with phase gates, approvals, and no-auto-commit rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? EvanFlow-go coordinates end-to-end orchestration of the EvanFlow loop, handling phases from brainstorming to STOP with explicit checkpoints and no automatic commits. ## Core Features & Use Cases

  • Orchestrates the full EvanFlow loop across multiple sub-skills (brainstorming, planning, executing, TDD, iterate) and coordinates phase gates.
  • Enforces explicit user approvals at design and plan boundaries, supports parallel coder-overseer modes for multi-unit plans, and provides clear phase announcements.
  • Enables integration with specialty evanflow skills and sub-skills, ensuring consistent hand-offs and traceable workflows.
  • Real-world use: a product team uses evanflow-go to run a multi-skill feature workflow with checkpoints and quality checks. ### Quick Start Say "evanflow this" to initiate the full loop and hand off control to the appropriate sub-skills.

Frequently Asked Questions about evanflow-go

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

FAQPage Schema
How do I orchestrate a multi-unit TDD workflow with explicit checkpoints?

You orchestrate a multi-unit TDD workflow with explicit checkpoints by using a conductor skill to coordinate sub-skills across brainstorming, planning, execution, and iteration phases. The system enforces phase boundaries, explicit approvals, and no-auto-commit rules to ensure structured hand-offs.

What is the best way to coordinate parallel coder and overseer workflows in a multi-skill project?

The best way to coordinate parallel coder and overseer workflows in a multi-skill project is to use an orchestration skill that manages phase gates. It coordinates parallel workflows across multiple units while enforcing explicit user approvals at design and plan boundaries.

Can I enforce manual approvals and prevent automatic commits during test-driven development?

Yes, you can enforce manual approvals and prevent automatic commits during test-driven development. The orchestration loop implements explicit user approvals at design and plan boundaries and enforces a strict no-auto-commit rule throughout the execution phases.

How do I integrate specialty skills into a multi-phase development loop?

You integrate specialty skills into a multi-phase development loop by using an orchestration conductor that exposes hooks for these skills. This ensures consistent hand-offs, structured phase announcements, and traceable workflows across brainstorming, planning, execution, and STOP checkpoints.

Does this orchestration approach work for managing phase boundaries from brainstorming to STOP?

Yes, this orchestration approach works for managing phase boundaries from brainstorming to STOP. It coordinates the full loop end-to-end, ensuring explicit approvals and quality checks are met before moving between brainstorming, planning, executing, TDD, and iteration phases.