specflow-viewerlisted

# specflow-viewer ## When to use **This skill is callable-only** — it carries no trigger surface in the skill listing and is not routed into automatically. Run it when the developer invokes `/specflow-viewer`, or when another skill's instructions name it. Regenerating a client-facing site is a deliberate act, not something a resembling sentence should trip. What follows is its scope, not its triggers. Generate a polished, self-contained HTML page (`specs.html`) for browsing a Specflow project's two-layer spec tree — both the developer specs under `.specflow/specs/` and the high-level business specs under `.specflow/specs-business/`, plus the per-folder `_overview.md` docs that explain each group, all parsed and rendered as a client-facing site with a Business⇄Developer toggle, sidebar tree (folders surface their first-sentence summary as a subtitle, click a folder to read its overview), search across spec content AND folder overviews, cross-link sections (Implements / Implemented by) between the two layers, an "Unmapped" badge on dev specs missing an `implements:` link to a business spec, acceptance-criteria cards, dependency chips, and an optional test-status overlay. Use this skill PROACTIVELY whenever the user wants to show, present, export, publish, share, or hand off Specflow specs in a browsable format — including phrasings like "generate the spec viewer", "build the spec page", "make the HTML specs", "render the spec tree", "export specs as HTML", "spec browser", "s