Uta2000 Feature Flow
uta2000-feature-flow is a Claude Code plugin for the Validate phase that enforces acceptance-criteria discipline, checks, and verification across AI-assisted feature work.
by uta2000 · github.com/uta2000/feature-flow
Enforce acceptance-criteria discipline across AI-assisted feature work with hooks, checks, antipattern detection, and verification aligned to Superpowers-style workflows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install uta2000-feature-flow@uta2000/feature-flowBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:uta2000/feature-flow") and the paste-ready config with skillselion.get_install_config("plugin:uta2000/feature-flow").
What it does
uta2000-feature-flow is a Claude Code plugin that instills acceptance criteria discipline when you build features with agents: explicit criteria, automated checks, antipattern detection, and verification hooks across the feature lifecycle. Solo builders who lose scope when models improvise can register it to force written done-conditions before implementation accelerates, then re-check against those criteria before merge or release. Keywords point at hooks, Superpowers alignment, Context7 library queries, and standards enforcement—treat it as a process guardrail layered on top of coding skills, not a generator for UI or infra. Canonical shelf is Validate/scope because the highest leverage is defining and freezing criteria early; expect continued value in Build/pm and Ship/testing as criteria drive review and test expectations.
Highlights
- Acceptance-criteria enforcement and verification for AI-assisted feature development
- Automated checks, antipattern detection, and lifecycle-oriented hooks in one plugin bundle
- Integrates with Superpowers, Context7-style library queries, and standards-oriented workflows per plugin keywords
- Designed for feature-flow discipline from design through verification, not one-off codegen
- Single-plugin bundle (pluginCount: 1) from uta2000/feature-flow
Why builders use it
AI-assisted features often ship without clear acceptance criteria, so agents optimize for plausible code instead of provable done-ness.
After install, your workflow can gate features on explicit criteria, automated checks, and verification hooks before you treat a slice as complete.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 4 stars, 0 votes.
FAQ
Who is uta2000-feature-flow for?
It is for solo developers and small teams using Claude Code who need repeatable acceptance criteria when agents implement features.
When should I use uta2000-feature-flow?
Use it when scoping a feature and whenever you want enforcement through build and pre-ship verification, not only at the first planning message.
How do I add uta2000-feature-flow to my agent?
Add the uta2000/feature-flow plugin in Claude Code, enable its hooks per the repo README, and align your Superpowers or planning skills so criteria are written before implementation.
Comments
Share how you use uta2000-feature-flow, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.