From evanflow
Orchestrates full EvanFlow development loop (brainstorm → plan → execute → TDD → iterate → STOP) end-to-end when triggered by 'evanflow this' or similar phrases.
npx claudepluginhub evanklem/evanflow --plugin evanflowThis skill uses the workspace's default tool permissions.
Single entry point for the EvanFlow workflow. The user gives you an idea or task and asks to "evanflow it" — you take responsibility for walking the whole loop end-to-end, picking the right sub-skill at each step, and respecting checkpoints where the user must stay in control.
Loads EvanFlow shared vocabulary (deep modules, deletion test, vertical slice, grill) and invocation rules for evanflow-* skills. Use for new tasks when unsure which applies or to ground reasoning.
Implements features using multi-AI workflow with Codex and Gemini CLIs in Double Diamond Develop phase. Auto-activates on 'build X', 'implement Y', 'create Z', or 'develop feature' requests.
Orchestrates all code-modifying development tasks like bug fixes, enhancements, and new features using adaptive phases for analysis, specs, TDD, implementation, and verification.
Share bugs, ideas, or general feedback.
Single entry point for the EvanFlow workflow. The user gives you an idea or task and asks to "evanflow it" — you take responsibility for walking the whole loop end-to-end, picking the right sub-skill at each step, and respecting checkpoints where the user must stay in control.
You are the conductor; the other evanflow-* skills are the orchestra.
See evanflow meta-skill for the shared vocabulary (deep modules, deletion test, vertical slice, grill, mockup quick-mode).
Trigger phrases (or anything semantically equivalent):
SKIP when:
evanflow-debug, etc.) — let them control granularlyConfirm you've understood the idea in your own words, in one sentence. Examples:
"Got it — you want to add an
archivedflag to messages so cancelled ones drop off the dashboard."
Then ask one calibration question if scope isn't obvious:
"Quick scope check: is this a small targeted change or a feature with multiple components?"
If the user signals quick/small → consider whether a full evanflow loop is overkill. Offer a shortcut: "This sounds small — want me to skip brainstorming/planning and just TDD it directly? Or run the full loop anyway?"
Announce: "Step 1: brainstorming via evanflow-brainstorming."
Invoke evanflow-brainstorming:
Mockup quick-mode bypass: if the user originally said "show me mockups" rather than "implement," skip the full loop and produce mockups directly (HTML files, Figma frames, ASCII layouts — whatever the project uses). No spec, no plan, no TDD ceremony.
Checkpoint: before continuing, the user must explicitly approve the design. Not a tacit yes — actual confirmation.
Announce: "Step 2: writing the plan via evanflow-writing-plans."
If scope is small (one file, one behavior change), skip to Phase 3 with a verbal plan ("I'll write a failing test for X, then minimal impl"). Otherwise:
Invoke evanflow-writing-plans:
evanflow-coder-overseer to the user as the execution path instead of sequential executing-plans. Lay out signals on both sides. User picks.If the user picks coder-overseer, structure the plan with a per-coder section + cohesion contract upfront.
Checkpoint: before continuing, the user must approve the plan.
Announce based on user's pick:
evanflow-executing-plans."evanflow-coder-overseer."Sequential path — invoke evanflow-executing-plans:
evanflow-tdd for any production codeParallel path — invoke evanflow-coder-overseer:
subagent_type: evanflow-overseer if available)Inside both paths, every code-writing task goes through evanflow-tdd — it's the discipline running inside the execute harness, not a phase that comes after. Per-cycle: RED → GREEN → REFACTOR (refactor with the fresh test as safety net, not deferred to the end). Behavior through public interface, watch each test fail before writing impl, assertion correctness check.
Announce: "Step 4: self-review loop via evanflow-iterate."
Invoke evanflow-iterate:
chromium --headless --screenshot=..., then read the PNGAnnounce: "Implementation complete. Stopping here per EvanFlow's no-auto-finish rule."
Report:
Do NOT stage files, commit, push, merge, or open a PR. Wait for user direction.
Watch for drift symptoms throughout (re-asking established questions, contradicting earlier decisions, restating constraints already set). At any clean phase boundary (after design approval, after plan approval, after execution success), if the session feels heavy, proactively offer:
"We just finished [phase X]. Context is getting heavy — want me to invoke
evanflow-compactto summarize anchors and prep for/clearbefore the next phase?"
Don't force it. Let the user decide.
evanflow meta + this skill's specifics)STOP. The user controls integration.This skill IS the entry point. It hands off TO other evanflow skills, not the other way around. The only "hand-off" out of evanflow-go is STOP at Phase 5, returning control to the user.
Special-purpose skills can be invoked mid-flow when relevant:
evanflow-glossary to update CONTEXT.md, then continueevanflow-improve-architecture first, then resumeevanflow-design-interface before planevanflow-debugevanflow-prd → writing-plansThese don't break the flow — they're sub-tools used inside the appropriate phase.
Without an entry-point orchestrator, the user has to know which evanflow-* skill to invoke at each step. That defeats the cohesion property. With evanflow-go, the user says "evanflow this" once and the right sub-skill fires at the right time, with the right checkpoints preserved.
The skill is conductor, not autopilot. Checkpoints are real (brainstorm approval, plan approval, iterate hand-back). The user always has the option to interrupt, switch paths, or take manual control.