← ClaudeAtlas

living-documentation-publisherlisted

Use when BDD scenarios pass in CI and stakeholders need an always-current, readable report of which acceptance criteria pass. Turns Cucumber JSON into HTML living documentation (multiple-cucumber-html-reporter or Serenity BDD) and publishes it to GitHub or GitLab Pages.
testland/qa · ★ 13 · Data & Documents · score 83
Install: claude install-skill testland/qa
# living-documentation-publisher ## Overview Per the Serenity BDD book ([serenity-bdd/the-serenity-book, living-documentation.adoc][ld]): > "Living documentation is generated by the automated test suite, and is > therefore by definition it is always up-to-date." The same source distinguishes living documentation from plain test reports: living documentation is authored before development starts, targets the whole team (BAs, product owners, stakeholders), and reads as a business-functionality narrative, not a pass/fail table. This skill covers the full workflow: produce Cucumber JSON from a passing suite, feed it into a report renderer, apply tag-based section routing, and publish the HTML artefact to a Pages endpoint so stakeholders get a URL, not a zip file. Two primary renderers are covered: - **multiple-cucumber-html-reporter** (Node, any Cucumber-JS project) - see [references/node-reporter.md](references/node-reporter.md). - **Serenity BDD aggregate report** (JVM, Maven/Gradle projects using `CucumberWithSerenity`) - see [references/serenity-reporter.md](references/serenity-reporter.md). ## When to use - The team already has Cucumber scenarios (see `cucumber-testing`) and stakeholders need to read acceptance-criteria status without opening a test runner. - The living-documentation page must track only *passing* scenarios (not every scenario authored, including pending or skipped ones). - CI should gate report publication so stakeholders never see a stal