Where is the active spec information stored?

The active specification ID is stored in .claude/spec-kit/memory/progress.yml within your local repository.

What does the set-current-spec skill do?

It updates a progress file in your project to tell Claude which specific feature or requirement you are currently working on, ensuring all subsequent commands stay in context.

What happens if I try to switch to a spec that doesn't exist?

The skill performs a validation check. If the directory is not found, it will report an error, list your available specs, and refuse to update the progress file with an invalid ID.

How do I trigger a spec switch?

You can simply tell Claude to 'switch to spec 002' or 'work on the user-auth feature' and the skill will automatically handle the update.

Is this compatible with other Spec-Kit commands?

Yes, this skill is designed to work in tandem with get-current-spec and specify commands to create a cohesive spec-driven development environment.

Spec-Kit: Set Current Specification

Name: Spec-Kit: Set Current Specification
Author: retsohuang

byretsohuang

•

Productivity & Workflow

Manages and persists the active project specification context to streamline spec-driven development workflows.

About

The set-current-spec skill is a core component of the Spec-Kit framework that enables Claude to maintain a persistent state of the current feature or requirement being addressed. By updating a centralized progress file, it ensures that all subsequent development, testing, and documentation tasks remain contextually aligned with the specific feature ID without requiring the user to repeatedly provide context. This skill includes built-in validation to ensure specified IDs exist and provides clear confirmation of the active working directory.

Key Features

Centralized state management via progress.yml
Integrated error handling with available spec listings
Persistent context tracking for active specifications
Automated directory validation before state updates
Seamless switching between multiple feature branches
1 GitHub stars

Use Cases

Resuming work on a specific feature after a development break to restore session context
Automatically setting the working context immediately after creating a new specification
Switching context between different feature specifications like '001-auth' and '002-payments'

About

Key Features

Centralized state management via progress.yml
Integrated error handling with available spec listings
Persistent context tracking for active specifications
Automated directory validation before state updates
Seamless switching between multiple feature branches
1 GitHub stars

Use Cases

Resuming work on a specific feature after a development break to restore session context
Automatically setting the working context immediately after creating a new specification
Switching context between different feature specifications like '001-auth' and '002-payments'