Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who already trust terminal coding agents for real work but want a more structured planner-to-executor handoff than an improvised one-shot prompt.
Who should use it
Who should skip it
Consider robzilla1738/supergoal lower priority if you already have a working solution in this category.
About this signal
robzilla1738/supergoal is tracked by RepoRadar as a agent workflow in the Developer Tools section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. robzilla1738/supergoal leads on workflow potential (9.8) and open-source/build quality (8.4); its lowest signal is setup ease (6.4), so factor that in before investing setup time. 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 robzilla1738/supergoal a composite score of 8.3 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 31.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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It is explicitly designed to launch autonomous file edits and shell work through Claude Code or Codex, so start in disposable repos until you trust the generated phase specs and retry behavior; The workflow writes ROADMAP, STATE, and phase artifacts into your working area, so decide where that operational metadata belongs before rolling it into a clean production tree; The safety story depends on the underlying agent runtime permissions as much as the plugin itself, so validate the whole harness rather than assuming the slash command enforces safe boundaries on its own.