atr

Convert sprint acceptance criteria into Playwright testbooks and run them.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill atr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atr
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/atr
Command: npx skills add https://github.com/russosalv/NONoise --skill atr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Acceptance testing is often manual, time-consuming, and hard to reproduce across environments. The ATR skill automates this by converting sprint acceptance criteria into a machine-readable testbook, executing tests via Playwright, and surfacing markdown reports with evidence.

Core Features & Use Cases

  • Reads sprint manifests to generate per-area testbooks, organized under docs/sprints/Sprint-N/acceptance.
  • Executes tests against the running application, produces markdown reports with screenshots, and maintains a backlog of failures for backlog grooming.
  • Optionally pushes failure items to external trackers once a MCP integration is wired, and supports generating stakeholder-friendly test plans.

Quick Start

Run /atr generate to create a testbook from your sprint manifest, then run /atr run to execute it against your app.

Frequently Asked Questions about atr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sprint acceptance testing with Playwright?

Automate sprint acceptance testing by converting manifest criteria into a machine-readable testbook and executing it with Playwright. This verifies app behavior against defined acceptance criteria and generates markdown reports with screenshots.

How do I generate and run a testbook from a sprint manifest?

Generate a testbook from a sprint manifest by running the generate command, which creates per-area testbooks organized under docs/sprints. Execute the testbook against your running application using the run command to verify behavior and capture results.

Can I use acceptance test automation for brownfield applications?

Acceptance test automation applies to both greenfield and brownfield scenarios. It generates per-area testbooks, executes tests via Playwright against the running application, and maintains a backlog of failures for follow-up regardless of project age.

What is the best way to maintain a backlog of failed acceptance tests?

Maintain a backlog of failed acceptance tests by executing the testbook against your application and capturing failures during the run. The automation produces markdown reports with screenshots and maintains the failure backlog for grooming and follow-up.

Does the acceptance test orchestrator support pushing failures to external trackers?

The acceptance test orchestrator optionally pushes failure items to external trackers once an MCP integration is wired. It reads the sprint manifest, generates testbooks, runs tests, and pushes failures when integrations are available.

Can I generate stakeholder-friendly test plans from sprint acceptance criteria?

Generate stakeholder-friendly test plans by reading sprint manifests and converting the acceptance criteria into a machine-readable testbook. The automation supports generating these plans alongside executing tests and producing markdown reports with evidence.