What problem does it solve? When multiple features move through a brainstorm → design → plan → implement pipeline, it becomes hard to remember which features are open, which stage each one reached, and what to do next. This Skill reads the feature trackers, stage files, and git history in the repo and answers that question with a single status table, without ever modifying anything. ## Core Features & Use Cases - Per-stage status table: Shows storm, design, plan, and implement status for every feature under features/, sorted by most recent activity, with a suggested next-step command per row. - In-progress detection: Inspects plan-stage commits on the current git branch to report partially implemented features (e.g. "in progress — Stage 3"). - Read-only and fault-tolerant: Never creates folders, edits trackers, or commits; missing trackers, unparseable timestamps, or absent git repos degrade to fallbacks with a closing note instead of failing. - Use Case: After a week of parallel work, run the skill to see that v7 is mid-implementation at Stage 2, v6 still needs a plan, and v4 is ready to implement — then jump straight to the right command. ## Quick Start Ask the assistant to list the features currently in flight in this repo, optionally including completed ones by passing the argument "all".