specflow-viewerlisted

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"
pedropacheco95/cortex · ★ 1 · Testing & QA · score 74

Install: claude install-skill pedropacheco95/cortex

# specflow-viewer Generates **one self-contained HTML file** that presents a Specflow project's full two-layer spec tree (business + developer) as a polished, client-facing documentation site. CSS, JS, all spec data, all folder overviews, and the cross-tree mapping inline into a single file — no server, no build, no external assets. The user double-clicks it and it works. > **Cortex awareness:** on a Cortex project, the viewer MAY read the Purpose lines of > the insight per-file entries (`.cortex/insight/anatomy/<path>.md`) to enrich > rendering (e.g. file summaries alongside the specs that govern them). No Cortex > reads are required — the spec trees remain the only mandatory input. ## When to use Trigger whenever the user wants a browsable, shareable view of a Specflow project's specs — at either layer, or both. Typical phrasings: - "Generate the spec viewer" / "build the spec page" / "make the HTML specs" - "Show the business specs to the stakeholder" / "render the business view" / "client-facing specs" - "Show the folder overviews" / "render the group descriptions" - "Where are the unmapped specs?" / "show me the business→dev mapping" / "coverage view" - "Render the spec tree" / "export specs as HTML" / "publish the specs" - "Spec browser" / "spec dashboard" / "spec viewer" - Anything about handing off, delivering, or sharing Specflow specs with a non-developer audience Do NOT use for: - Editing or generating spec Markdown itself (use the Specflow methodology skills