feature-flow

feature-flow

A Claude Code plugin that enforces a full feature development lifecycle — from idea to merged PR — so you don't discover schema mismatches, deprecated APIs, or broken assumptions halfway through coding. You say "start: add user notifications" and it auto-detects your tech stack, queries live documentation for current patterns, walks you through brainstorming and design, then verifies that design against your actual codebase (columns, types, routes, constraints) before a single line of implementation is written. After implementation (done via TDD in an isolated git worktree), it runs a multi-agent code review pipeline with up to 7 specialized reviewers, auto-fixes findings, generates a CHANGELOG entry, and mechanically verifies every acceptance criterion before opening a PR.

The upfront design adds ~20-30 minutes but typically saves 2-4 hours of mid-implementation debugging per feature. It works with any tech stack — Next.js, Supabase, Django, Rails, Flutter, whatever — and gets smarter over time by writing discovered gotchas (like "PostgREST silently caps queries at 1000 rows") back into your project config so every future feature is checked against past lessons.

Requirements

• Claude Code CLI
• GitHub CLI (gh on PATH, authenticated via gh auth login) — used for issue creation, PR checks, review bot handling, and issue commenting/closing
• superpowers plugin (required — handles brainstorming, implementation planning, TDD, worktrees, and PR workflow)
• Context7 MCP plugin (required — provides live documentation lookups for any tech stack during design and implementation)

Recommended (for full code review coverage):

• pr-review-toolkit plugin (adds: code-simplifier, silent-failure-hunter, test-analyzer, type-design-analyzer)
• feature-dev plugin (adds: feature-dev:code-reviewer)
• backend-api-security plugin (adds: backend-security-coder)

Installation

From the marketplace

# Install required plugins first
claude plugins add superpowers
claude plugins add context7

# Install feature-flow
claude plugins add feature-flow

# Recommended plugins (for full code review coverage)
claude plugins add pr-review-toolkit
claude plugins add feature-dev
claude plugins add backend-api-security

From GitHub

# Install required plugins first
claude plugins add https://github.com/obra/superpowers
claude plugins add context7

# Install feature-flow
claude plugins add https://github.com/uta2000/feature-flow

# Recommended plugins (for full code review coverage)
claude plugins add pr-review-toolkit
claude plugins add feature-dev
claude plugins add backend-api-security

Per-project (manual)

Copy the agents/, skills/, hooks/, and references/ directories into your project's .claude/ directory. You still need the superpowers and context7 plugins installed separately.

Quick Start

After installing, open any project and tell Claude:

start: add user notifications

feature-flow will:

1. Scan your project files and auto-detect your platform and tech stack
2. Resolve Context7 documentation libraries for each detected technology
3. Create a .feature-flow.yml with your project context (first time only)
4. Classify the scope (quick fix → major feature)
5. Walk you through the right steps — brainstorm, look up docs, design, verify, implement, ship

The lifecycle adds ~20-30 minutes of upfront design but typically saves 2-4 hours of mid-implementation debugging per feature.

For a quick fix, just say what's broken — the lifecycle is streamlined: understand, fix (TDD), verify, PR.

Add --yolo to auto-select recommended options and skip confirmation prompts:

start: add user notifications --yolo

YOLO Mode

For experienced users who trust the lifecycle's recommended defaults:

start: add user notifications --yolo

YOLO mode auto-selects recommended options at every decision point (scope classification, brainstorming questions, issue confirmation, etc.) and logs each decision inline:

YOLO: Platform/stack → Accepted: web, [next-js, supabase]
YOLO: Scope → Feature
YOLO: brainstorming — Export trigger → Option A: button in toolbar

At completion, a full decision log table is printed so you can review what was decided.

What YOLO does NOT bypass: Quality gates (tsc, lint, tests), anti-pattern hooks, acceptance criteria verification, code review pipeline, and Context7 documentation lookups all run identically. YOLO only skips confirmation prompts — it doesn't skip work.