Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want AI coding work to leave behind clear scope, intent, and change history instead of disappearing into chat transcripts.
Who should use it
Who should skip it
Skip Fission-AI/OpenSpec unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
Fission-AI/OpenSpec is tracked by RepoRadar as a developer tool in the Coding Workflows 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. The standout signals for Fission-AI/OpenSpec are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) 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 Fission-AI/OpenSpec a composite score of 8.7 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 88.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
It is designed to steer real code changes through AI assistants, so test it in a non-critical repo before you make it part of a production delivery path; A strong spec workflow can still add process overhead if the team applies it to tiny fixes that do not need proposal or task artifacts; The framework improves structure, not judgment, so reviewers still need to verify that the assistant's plan matches the codebase reality.