Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want a stricter spec-first path for large coding-agent changes and are willing to trade speed for stronger planning, TDD gates, and review discipline.
Who should use it
Who should skip it
Skip MageByte-Zero/spec-superflow for now if you are only tracking items with a 'try now' verdict.
About this signal
MageByte-Zero/spec-superflow is tracked by RepoRadar as a workflow plugin in the AI Coding section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'worth watch' with a Gold tier and moderate setup difficulty. The standout signals for MageByte-Zero/spec-superflow are open-source/build quality (8.4) and workflow potential (8.4), while maturity (6.3) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned MageByte-Zero/spec-superflow a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The plugin writes workflow assets into local agent client environments, so review the install path and keep first use on a non-critical project; The full nine-step workflow is deliberately heavyweight and token-expensive, so it can slow or overcomplicate small changes.