uta2000/feature-flow

Claude Code plugin: acceptance criteria discipline for AI-assisted development

4Stars on the repository
19Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

cleanup-merged

01

uta2000/feature-flow

Skill Claude CodeCodex

Cleans up worktrees, local branches, remote branches, and handoff files for merged or closed PRs. Invoked automatically by merge-prs after a successful merge, and opportunistically by start: at session kickoff. Safe to run manually at any time — all actions are idempotent.

4 1mo ago C 64 tokens original MIT

consult-codex

02

uta2000/feature-flow

Skill Claude CodeCodex

Consult the codex MCP server as a second AI opinion via a three-phase Claude-orchestrated flow. Use for proactive reviews (design, plan, code) or reactive stuck recovery. Requires codex.enabled=true in .feature-flow.yml and a configured codex MCP server.

4 1mo ago A 60 tokens original MIT

create-issue

03

uta2000/feature-flow

Skill Claude CodeCodex

This skill should be used when the user asks to "create an issue", "create a GitHub issue", "open an issue", "write up an issue", "file an issue", or after a design has been verified and needs to be captured as a trackable GitHub issue for implementation. Also handles updating an existing issue when an issue number is…

4 1mo ago A 79 tokens original MIT

design-document

04

uta2000/feature-flow

Skill Claude CodeCodex

This skill should be used when the user asks to "write a design doc", "create a design document", "document the design", "write up the design", "write a spec", "spec this out", or when brainstorming is complete and decisions need to be captured before implementation planning.

4 1mo ago A 61 tokens original MIT

design-verification

05

uta2000/feature-flow

Skill Claude CodeCodex

This skill should be used when the user asks to "verify the design", "check the design against the codebase", "validate the design doc", "check for blockers", "will this design work", or after writing a design document to catch schema conflicts, type mismatches, and pipeline assumptions before implementation, "check…

4 1mo ago A 84 tokens original MIT

merge-prs

06

uta2000/feature-flow

Skill Claude CodeCodex

Merges feature-flow PRs in batch. Invoked directly with PR numbers or patterns (standalone mode), or as "merge-prs feature-flow" to merge all labeled PRs (cross-session mode).

4 1mo ago A 46 tokens original MIT

session-report

07

uta2000/feature-flow

Skill Claude CodeCodex

Use when the user asks to "analyze a session", "session report", "review session performance", "how did that session go", "token usage report", "cost report", or wants to understand the performance, cost, and quality of a completed Claude Code session. Accepts a session JSON file path as input.

4 1mo ago A 68 tokens original MIT

settings

08

uta2000/feature-flow

Skill Claude CodeCodex

View and manage Feature-flow settings — YOLO stops, notifications, branches, design preferences, standards, and more. Use when the user asks to "configure", "change settings", "update config", or "/settings".

4 1mo ago B 46 tokens original MIT

spike

09

uta2000/feature-flow

Skill Claude CodeCodex

This skill should be used when the user asks to "run a spike", "test an assumption", "do a proof of concept", "de-risk", "validate an API", "check if X works", "prototype", "build a PoC", or when a design document contains risky technical unknowns that need validation before committing to implementation.

4 1mo ago A 72 tokens original MIT

start

10

uta2000/feature-flow

Skill Claude CodeCodex

This skill should be used when the user asks to "start:", "start a feature", "build a feature", "implement a feature", "new feature", "start working on", "I want to build", "let's build", "add a feature", or at the beginning of any non-trivial development work. It orchestrates the full lifecycle from idea to PR…

4 1mo ago B 86 tokens original MIT

uta2000/feature-flow

Skill Claude CodeCodex

Use when asked to "verify acceptance criteria", "check criteria", or "verify the implementation against the plan" during active feature development. Do NOT trigger for issue management (close issue, comment), worktree cleanup, or post-merge/post-PR operations.

4 1mo ago A 59 tokens original MIT

uta2000/feature-flow

Skill Claude CodeCodex

Run after writing an implementation plan to validate that every task has machine-verifiable acceptance criteria. Drafts missing criteria automatically from task context. Use after writing plans or when reviewing existing plans.

4 1mo ago A 42 tokens original MIT