Skip to content

How should the SPECIFY FEATURE environment variables be configured? #1426

@migodev42

Description

@migodev42

Description

I am seeking clarification on the correct way to implement the SPECIFY_FEATURE environment variable within spec-kit. Currently, I am attempting to isolate or prioritize specific features during execution, but the configuration does not seem to be recognized by the system.

Attempted Configurations

I have tried the following methods to define the variable, but neither has yielded the expected results:

  1. Via .env file:
    Added the following line to the root .env file:
SPECIFY_FEATURE="xxx-feature"
  1. Via Agent Definition (e.g., QWEN.md):
    Included the variable within the metadata/configuration section of the Agent file:
SPECIFY_FEATURE="xxx-feature"

Observed Behavior

Despite these definitions, the system appears to ignore the SPECIFY_FEATURE flag, when I use /speckit.specify it always create a new branch.

Questions

  • What is the intended scope and priority for the SPECIFY_FEATURE variable?
  • Is there a specific syntax or a different configuration file (e.g., a global config or CLI flag) required to make this effective?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions