What problem does it solve? When multiple feature-development skills (storm, design, plan, implement) each need to know which versioned feature folder to write into, duplicating that resolution logic causes drift and inconsistency. This internal helper centralizes folder resolution so all four skills stay aligned on versioning, naming, and stage-file paths. ## Core Features & Use Cases - Folder and version resolution: Scans features/ for existing feature-v<N>-<description> folders and decides whether to continue the latest feature or create a new one, enforcing contiguous version numbers. - Stage file path computation: Returns the exact stage .md path and prerequisite file path the calling skill must read or write, as a parseable output block. - Tracker seeding: Creates the feature folder and copies the plugin's feature-tracker.html template into place when a new feature is started. - Use Case: When a user runs /dev:feature-plan without naming a version, this skill determines the latest in-progress feature, verifies the design stage file exists, and hands back the exact plan file path to write. ## Quick Start Invoke this skill from another feature skill with an argument string like stage=plan, version=3 to resolve the target feature folder and stage file path.
