How does the skill identify if I am working on an epic or a feature?

The skill uses a priority system: it first checks for specific directory structures (epics/ or specs/), then analyzes the current Git branch name, and finally looks at the state.yaml file.

Can this be used in CI/CD pipelines?

Absolutely. It is designed to be environment-agnostic and works seamlessly in GitHub Actions, GitLab CI, and other automated platforms.

What happens if the detection fails?

If the skill cannot determine the workflow type, it returns an 'unknown' status and exit code 1, which triggers a manual prompt for the user to select the workflow type.

Does this skill support Windows environments?

Yes, it includes both Bash scripts for Unix-like systems and PowerShell (.ps1) scripts for native Windows support.

Spec-Flow Workflow Detection

Name: Spec-Flow Workflow Detection
Author: marcusgoll

bymarcusgoll

•

Productivity & Workflow

Automates the identification of epic and feature workflows to streamline Spec-Driven Development tasks.

About

The Workflow Detection skill provides a centralized mechanism for Claude Code to determine the active project context within the Spec-Flow framework. By analyzing workspace files, Git branch patterns, and internal state files, it eliminates redundant detection logic across dozens of commands. It provides a single source of truth for path resolution, ensuring that phase commands like clarify, plan, and implement always target the correct epic or feature artifacts regardless of the operating system or environment.

Key Features

Cross-platform support for Bash (Linux/macOS) and PowerShell (Windows)
Automatic path variable generation for specs, plans, and tasks
Seamless integration with Git worktrees and CI/CD pipelines
Multi-layered detection via files, Git branches, and state files
Centralized detection logic for epics and feature workflows
18 GitHub stars

Use Cases

Standardizing artifact management across large-scale multi-sprint projects
Routing deployment commands to the correct environment based on workflow type
Automatically locating specification files during the planning phase

About

Key Features

Cross-platform support for Bash (Linux/macOS) and PowerShell (Windows)
Automatic path variable generation for specs, plans, and tasks
Seamless integration with Git worktrees and CI/CD pipelines
Multi-layered detection via files, Git branches, and state files
Centralized detection logic for epics and feature workflows
18 GitHub stars

Use Cases

Standardizing artifact management across large-scale multi-sprint projects
Routing deployment commands to the correct environment based on workflow type
Automatically locating specification files during the planning phase