/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

github/spec-kit

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-30T12:06:54.459Z

3mo ago

github/spec-kit

github/spec-kit is a popular, actively maintained Python-based open source toolkit for Spec-Driven Development. It is centered on the `specify` CLI, which bootstraps projects from bundled templates and scripts so teams can start from specifications rather than hand-building everything from scratch. The repo looks most interesting as a fork if you want to customize the workflow, templates, extensions, or presets around spec-driven project setup rather than just consume a library.

Loading tags...

Stars83,640

Forks7,153

Default branchmain

Last pushed2026-03-27T19:04:15Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want a heavily expanded, opinionated Spec Kit variant for multi-agent AI system delivery and production workflows. Stick with upstream if you want the smaller, faster-moving, general-purpose Spec Kit experience with less maintenance risk.

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.

Fork comparison

panaversity/spec-kit-plus

54/100

slowing

significant_divergence

Choose this fork if you want a heavily expanded, opinionated Spec Kit variant for multi-agent AI system delivery and production workflows. Stick with upstream if you want the smaller, faster-moving, general-purpose Spec Kit experience with less maintenance risk.

Likely purpose

An opinionated fork that turns Spec Kit from a general Spec-Driven Development bootstrapper into a broader playbook and toolkit for multi-agent AI system delivery, with added patterns, templates, and workflows for production-oriented stacks and AI tooling.

Best for

Teams building multi-agent AI products that want opinionated scaffolding and process assets.; Fork maintainers who prefer documentation-heavy, workflow-driven customization over a minimal CLI.; Engineers adopting OpenAI Agents SDK, MCP, A2A, Kubernetes, Dapr, or Ray as part of a standardized delivery stack.; Users who want reverse-engineering, testing, and architecture-history artifacts integrated into the development process.

Additional features

Expanded documentation and playbooks under `docs-plus` for AI CLI workflows, composable agent architectures, developer environments, and AI pair programming.
A new `sp.reverse-engineer` command for codebase archaeology and reverse-engineering workflows.
Positioning around multi-agent production stacks, including OpenAI Agents SDK, MCP, A2A, Kubernetes, Dapr, and Ray.
More operational guidance and hardening content, including local testing scripts, Docker verification tests, and production hardening notes.
A stronger emphasis on specs, architecture history, prompt history, tests, and automated evaluations as first-class artifacts.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

It is materially behind upstream, with 159 commits behind the parent, so adopters should expect upstream bugfixes and release updates to lag.
A prior multi-feature git worktree support enhancement was explicitly reverted, so that parallel-development workflow is not currently a reliable part of the fork.
The fork appears to be less focused on the upstream general-purpose `specify` bootstrapper experience and more on an opinionated AI-systems playbook, which may make the original lightweight Spec Kit flow harder to find or reuse.
It trails upstream by 159 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Much richer guidance for teams building agentic AI systems.
Better fit for production-minded adopters who want patterns, templates, and workflows rather than a minimal starter kit.
Adds a specialized reverse-engineering workflow and broader environment coverage.
Large documentation surface suggests strong process codification and onboarding material.

Risks

Fork divergence is large enough that upstream compatibility may weaken over time.
The fork is behind upstream, so adopters may miss fixes and changes landing in the main project.
The added breadth may increase complexity for teams that only want the original Spec Kit bootstrapper.
Reverted worktree support suggests some parallel-development workflows may be unstable or intentionally disabled.

github/spec-kit · Discofork