github/spec-kit

Choose this fork if you want a localized Traditional Chinese Spec Kit and value adapted templates/docs over freshness. Avoid it if you need the latest upstream CLI behavior, extensions, and fixes.

Choose this fork if you want Spec Kit repurposed into a research workflow with publishing, quality-gate, and agent-context tooling. Choose upstream if you want the broader, more current Spec Kit ecosystem and better compatibility with the original spec-driven setup.

Choose this fork if you want a more customized, automation-heavy Spec Kit with internal workflow assets and agent-centric scaffolding. Choose upstream if you want the safest, most up-to-date, and best-supported baseline, because this fork is substantially divergent and behind current upstream.

Choose this fork if you want a more opinionated, engineer-aware Spec Kit variant with extra automation and project-state handling. Stick with upstream if you want broad compatibility, fresher maintenance, and the lowest migration risk.

Choose this fork if you want a more opinionated, workflow-heavy Spec Kit variant with custom product/architect extensions and evaluation tooling. Stay with upstream if you want the broader community baseline, simpler upgrade path, and fewer renamed or removed pieces.

Prefer this fork if you need Roo-specific Spec Kit behavior and are willing to own the rebase cost. Prefer upstream if you want the latest Spec Kit fixes, broader community catalog coverage, and lower maintenance risk.

Choose this fork if you want Spec Kit re-centered around PMF discovery and validation for AI SaaS. Choose upstream if you want the broader, faster-moving general-purpose toolkit with more recent fixes and a lower-maintenance path.

Choose this fork if your priority is a more opinionated spec-driven workflow with richer command templates and onboarding guidance. Choose upstream if you care more about staying current with fixes, agent compatibility updates, and community catalog growth.

Prefer this fork if you want a JavaScript-first Spec Kit distribution and are willing to own divergence from upstream. Prefer upstream if you want the latest maintained Python CLI and the full current feature set.