What problem does it solve? Stakeholders and product owners cannot read Playwright spec files, so they have no transparent answer to "what scenarios are we running, and why?". This Skill turns an existing E2E suite into a printable, non-technical inventory document. ## Core Features & Use Cases - Scenario Extraction & Cross-Referencing: Parses tests/e2e/**/*.spec.ts files and cross-references each test against the sentinel-bearing journey-map.md to attach priority, category, section, and purpose metadata. - Runtime-Derived Taxonomy: Groups scenarios by primary section (URL-prefix or file-name clusters) and page area derived from the journey map, with priority, type, and status chips per scenario — never hardcoded app sections. - PDF Rendering with Verification: Renders an A4-landscape dark-mode HTML catalogue to PDF via per-slide Chromium rendering merged with pdf-lib, with mandatory page-count verification and exhaustive visual inspection of every page. - Use Case: Before a client review, ask the agent to produce a test catalogue; it outputs a cover page with headline totals, per-section scenario tables, an adversarial-regression section, and a transparent skipped-with-reason section. ## Quick Start Ask the agent to produce a test catalogue for the client from the existing Playwright suite and journey map.
