Ai

GitHub Spec Kit v0.8.1 Improves Branch Planning and Expands Preset Support

GitHub Spec Kit v0.8.1 Improves Branch Planning and Expands Preset Support

GitHub’s spec-kit v0.8.1 delivers a focused update that improves how teams work with project specifications across custom Git branch setups, modernizes its integration model, and broadens preset support for more specialized workflows. The release is small in version number but meaningful in practice, especially for users relying on branch-aware planning commands and reusable specification presets.

What Changed

The most important fix in v0.8.1 addresses planning behavior on custom Git branches. The update makes /speckit.plan work more reliably by using .specify/feature.json, which helps the tool resolve feature planning context correctly outside standard branch assumptions. For teams using non-default branching strategies, that should reduce friction in day-to-day spec workflows.

The release also replaces the older prompts-based MarkdownIntegration approach with a new SkillsIntegration model for the vibe feature set. This is a notable architectural shift because it points toward a more structured and extensible way to manage integrated capabilities inside spec-kit, rather than relying on the previous prompt-driven markdown flow.

Several quality-of-life fixes are included as well. Command references are now resolved correctly based on integration type, handling dot-versus-hyphen naming differences more accurately. Another fix swaps out an xargs-based trimming approach for sed, improving handling of descriptions that include quotes.

On the preset and catalog side, the community preset table has been moved to the docs site, catalog metadata has been enriched, the lean preset README has been improved, and the Jira preset is now registered in the community catalog. The release also adds a new screenwriting preset, expanding spec-kit into a more specialized content and workflow use case.

Why It Matters

For engineering and product teams, the custom-branch planning fix is the headline improvement. It makes spec-kit more practical in real-world repositories where branch naming and flow often differ from the default path expected by tooling. That kind of reliability matters when specification commands are part of a repeatable planning workflow.

The move to SkillsIntegration also suggests spec-kit is maturing beyond a simpler prompt-layer implementation. That may make future integrations easier to maintain and extend, which is important for teams standardizing internal specification practices around AI-assisted tooling.

The new Jira and screenwriting presets show that the project is continuing to widen its applicability. Jira support is useful for enterprise teams connecting specs with established delivery workflows, while the screenwriting preset hints at broader use beyond traditional software-only planning.

Overall, v0.8.1 is a practical refinement release: not a major headline-grabber, but a solid update that improves branch compatibility, integration design, and preset coverage for users adopting spec-kit in more varied environments.

Official Source: https://github.com/github/spec-kit/releases/tag/v0.8.1