eagle-feature-flow

Orchestrate a nine-phase feature workflow from planning to commit.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/eagleisbatman/eagle-skills --skill eagle-feature-flow-eagleisbatman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eagle-feature-flow
Source: https://github.com/eagleisbatman/eagle-skills/tree/main/eagle-feature-flow
Command: npx skills add https://github.com/eagleisbatman/eagle-skills --skill eagle-feature-flow-eagleisbatman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents feature work from stalling or shipping with broken behavior by enforcing a complete, ordered workflow from planning through commit.

Core Features & Use Cases

  • Nine-phase feature lifecycle: Guides users through Plan → Tasks → Build → Test → Spectral Review → Fix → Anti-Slop → Final Test → Commit, in strict order.
  • Test and review gates: Requires green tests after build and after fixes, and addresses HIGH/CRITICAL findings from review before moving on.
  • Code-quality improvement pass: Runs Anti-Slop to remove over-abstraction, redundant comments, over-logging, and other AI-typical bloat.

Quick Start

Tell the agent to run the full dev cycle by asking for “feature flow” while describing the feature you want implemented, including what you expect the end result to do.

Frequently Asked Questions about eagle-feature-flow

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

FAQPage Schema
How do I automate the feature development workflow from planning to git commit?

You can automate feature development by running a nine-phase workflow that enforces ordered execution from planning and task breakdown through staged coding, testing, spectral review, and final commit. This prevents shipping broken behavior.

What is an anti-slop pass in code review and feature development?

An anti-slop pass is a code-quality improvement step that removes AI-typical bloat such as over-abstraction, redundant comments, and over-logging after the initial build and review phases, before final tests and commit.

How do I enforce testing gates before committing new code?

To enforce testing gates, the workflow requires green test suites after the build phase and after applying fixes. It also mandates remediating HIGH or CRITICAL findings from spectral review before allowing the workflow to advance to the commit stage.

What is the best way to ensure ordered execution for feature implementation?

The best way to ensure ordered execution is using a structured lifecycle: Plan, Tasks, Build, Test, Spectral Review, Fix, Anti-Slop, Final Test, and Commit. Explicit gates prevent advancing until previous stages pass successfully.

Can I use workflow orchestration to break down feature tasks before coding?

Yes, workflow orchestration includes a dedicated planning and task breakdown phase before the build stage. This ensures features are fully scoped and structured into actionable coding steps prior to implementation and testing.

Why does my feature workflow stall during the code review and testing phases?

Feature workflows stall during review and testing when explicit gates block advancement. The process requires remediating HIGH or CRITICAL spectral audit findings and passing test suites before proceeding to the anti-slop and commit phases.