Skip to content

[Feature]: Spec Kit does not work on Windows PowerShell, only works in WSL/Linux #37

Description

@ausafulislam

Feature Category

Specify CLI (new commands, options)

Priority

Critical (blocking workflow)

Problem Statement

I tested Spec Kit / SpecifyPlus on my Windows PC and found that it works properly only inside WSL (Ubuntu/Linux). When running it in Windows PowerShell, many errors occur.

The main reason is that all scripts in the project are written as Linux .sh files and use commands like sed, grep, chmod, and others that do not work in PowerShell. As a result, several commands fail, and the toolkit cannot run correctly on native Windows.

Proposed Solution

Suggestion / Solution

It would be helpful if, during installation, the toolkit asked the user which system they are using (Linux, WSL/Ubuntu, or Windows PowerShell). This way, the installation process could guide the user appropriately and ensure that commands and scripts run correctly for their environment.

Currently, the tool works well only on WSL/Linux, so adding this check would improve usability for Windows users.

Alternatives Considered

No response

Examples/References

No response

Acceptance Criteria

No response

Breaking Change?

No

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions