Discofork
Repository brief

Fission-AI/OpenSpec

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:57:38.959Z
1mo ago

Fission-AI/OpenSpec

OpenSpec is an MIT-licensed Node.js/TypeScript CLI for spec-driven development with AI coding assistants. It is actively maintained, widely used, and built around a workflow for proposing, applying, and archiving feature specs in a project repo.

GitHub
Loading tags...
Stars35,894
Forks2,374
Default branchmain
Last pushed2026-03-11T07:54:38Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if Chinese-language usability matters more than being exactly current with upstream. Choose upstream if you want the newest OpenSpec workflow changes first.

Prefer this fork if Chinese-language support and cleaner Chinese-generated artifacts matter more than staying current with upstream. Prefer upstream if you need the newest commands, workflows, and release parity.

Choose this fork if you want the customized assistant and completion workflow it adds, and you are comfortable trading away a lot of upstream freshness. If you want the newest OpenSpec capabilities, upstream is the safer default.

Choose this fork if your primary use case is game design and you value localized, game-specific spec templates. Choose upstream if you want the latest OpenSpec features, broader tool support, and lower long-term maintenance risk.

Prefer this fork if you want a LightSpec-specific, skill-centric workflow and are comfortable with divergence from OpenSpec. Prefer upstream if you want the broader, more mature OpenSpec command set, templates, and compatibility.

Choose this fork if your main need is a Japanese-localized OpenSpec experience with clearer onboarding and workflow docs. Stay with upstream if you want the absolute latest release behavior and do not need localization.

Choose this fork if you want an almost-upstream OpenSpec with Qoder branding. Do not choose it if you want new capabilities or the latest upstream workflow improvements; upstream is the better fit for that.

Choose upstream instead unless you specifically need a frozen baseline; this fork offers no added capability and is substantially behind current OpenSpec.

Choose this fork if your priority is release automation and cross-platform reliability. Choose upstream if you want the newest spec-workflow features and the most actively maintained command surface.

Prefer upstream unless you specifically need this older snapshot. The fork adds no visible capabilities, while upstream has continued to evolve.