SuperAPI AI Directory

effective-flow

Coding & development

View repository

Updated 10-16 08:46

About this skill

Effective Flow

Effective Flow bundles complete software-engineering lifecycle coverage as tools invoked via effective-flow <tool> (version 1.64.0 (cdd9320)).

This router skill is deliberately thin. It carries the tool catalog, the dispatch rule, and the minimal universal worker-resolution and leaf-handoff bootstrap under "Rules"; a tool's full, tool-specific instructions are loaded from tools/<tool>.md only when needed. This keeps the session lean and avoids token exhaustion from preloading all tools.

Invocation

  • Claude Code: /effective-flow <tool> [arguments]
  • Codex: $effective-flow <tool> [arguments]

The portable instructions below use effective-flow <tool> as harness-neutral notation; invoke the skill with the syntax of the active harness.

Dispatch rule

  1. No or unknown <tool>: Output the grouped tool list below for orientation so the user can choose the right tool, and do nothing else. Do not guess which tool might be meant.
  2. Valid <tool>: Read the file tools/<tool>.md in this skill directory and follow it verbatim. Pass the remaining arguments through to the tool unchanged. Do not read any further tool files in the process — only the one that corresponds to the invoked tool.

For the apply tool, its instructions may in turn load an appropriate internal file (tools/apply-plan.md, tools/apply-review.md, or tools/apply-issues.md), depending on the detected source. These internal files are not directly invocable via effective-flow.

Some retired tool names stay invocable as deprecated aliases. They are deliberately absent from the catalog below, so rule 1 does not apply to them, and the tool file of an alias is the one case in which rule 2 allows a second tool file to be read:

  • effective-flow pr-review is the deprecated former name of effective-flow merge-gate. Read tools/pr-review.md, which reports the deprecation and then follows tools/merge-gate.md with the arguments unchanged.

Tools

The tools are grouped below by usage intent.

Understand what to do

Analysis & planning before code

  • effective-flow concept — Creates the concept for a new application – complete, but still on the surface.
  • effective-flow investigate — Finds the cause of a bug or surprising behavior – pure analysis, no code.
  • effective-flow plan — Routes issue references to issue planning or writes an actionable local plan – without code.
  • effective-flow open-plans — Shows which plans are still open when you pick the thread back up.
  • effective-flow plan-issue — Completes the planning for issues that still need clarification.

Implement a change

from a clarified plan/issue to code

  • effective-flow apply — Starts implementation from a finished source (plan, issue or review finding).
  • effective-flow build — Fully implements a new feature – plan, code, tests, review, completion.
  • effective-flow fix — Fixes a specific bug with a minimal, regression-guarded intervention.
  • effective-flow refactor — Improves structure or readability without changing behavior.
  • effective-flow docs — Creates or updates documentation without changing product behavior.
  • effective-flow maintain — Runs recurring maintenance: dependency updates and security fixes.
  • effective-flow iterate — Feeds PR review notes and instructions back into an existing PR as new commits.

Ensure quality

  • effective-flow review — Checks code for quality and findings – or, more deeply, an existing plan.

Deliver changes

  • effective-flow deliver — Delivers confirmed local changes as coherent commits in a clean pull request.
  • effective-flow commit — Commits the staged changes with a fitting commit message.
  • effective-flow pr — Opens a pull request from your branch (GitHub or Forgejo).
  • effective-flow merge-gate — Drives an open pull request through checks, bot notes, and – if allowed – the merge.

Set up & info

  • effective-flow setup — Sets up Effective Flow from a workflow profile, Express defaults, or a guided wizard.
  • effective-flow cleanup — Cleans migration remnants and safely reports or removes verified Effective Flow worktrees.
  • effective-flow version — Shows the installed Effective Flow version.

Language support

Scope Depth
Frontend JavaScript/TypeScript, Node.js backend/CLI, Rust Specialist implementer and reviewer
Other clearly identified product code Disclosed reduced-depth implementer and qualitative reviewer, following repository-native conventions
Tooling, CI, configuration, repository metadata Tooling-only generic implementer plus technical validation

The workflow is complete across its lifecycle; it does not claim equal specialist expertise in every language. Unknown product languages route automatically to the reduced-depth path after a visible notice. A genuinely ambiguous file role or unsafe-to-infer native command requires focused clarification instead of a guess.

Rules

  • Never load multiple tool files "just in case"; always only the currently invoked tool (plus, if applicable, the single internal apply source).
  • Specialist workers (implementers, reviewers, validators, test/docs writers …) are not effective-flow tools. Only the workflow/tool orchestrator may start worker roles or analysis fan-out, using bundled workers/effective-flow-<worker>.md contracts delegated through the host harness's built-in general-purpose subagent mechanism; workers are leaf executors and never delegate further. Invoking a tool is the user's standing request for exactly that internal delegation. Load or delegate only the selected worker, never the full worker set.
  • Start each worker with zero inherited turns when supported, otherwise the smallest host-supported history, and give it a compact self-contained handoff: objective, relevant artifact paths, scoped paths and ownership, execution and runtime-state roots when writes are allowed, resolved language, authority and write limits, and completion protocol. A worker returns missing essential context to the orchestrator instead of starting a child.