workflow-detection

Workflow type detection identifies whether you're running Epic or Feature workflows by analyzing workspace layout, Git branches, and state. This Skill centralizes that detection across all phase and deployment commands, eliminating duplication and returning a standardized JSON payload with type, base_dir, slug, branch, source, and is_worktree fields.

Yes, workflow detection works with both Bash and PowerShell environments. The Skill provides separate scripts for each: detect-workflow-paths.sh for Bash and detect-workflow-paths.ps1 for PowerShell, exposing path variables for downstream commands in both shells.

When automated detection fails based on workspace layout and Git state, the Skill falls back to prompting the user for input. It returns exit code 0 on successful detection or exit code 1 on failure, allowing scripts to handle both outcomes.

Workflow detection identifies Git worktrees and includes worktree-specific fields in the JSON output when is_worktree is true. This allows commands to apply worktree-aware logic for type detection and downstream processing.

Workflow detection returns a JSON payload containing type (Epic or Feature), base_dir (repository root), slug (workflow identifier), branch (current Git branch), source (detection method used), and is_worktree (boolean), plus additional fields when working within a Git worktree.

Centralizing workflow detection across 44 commands reduces code duplication, ensures consistency in how Epic and Feature workflows are identified, and simplifies maintenance when detection logic needs updates across your entire command suite.