Playwright Plain-Text Documentation
Use this skill for low-overhead scenario documentation.
Output Contract
For each scenario, capture:
- the goal,
- the relevant setup or preconditions,
- the main execution flow,
- the expected outcome,
- any requirement reference or open question that matters.
Output can be a short paragraph or a flat bullet list, whichever is clearer for the material.
Writing Rules
- Keep the sequence easy to follow.
- Prefer user intent and expected behavior over implementation detail.
- Make assumptions visible instead of hiding them in prose.
- Do not add formal structure unless the user specifically wants TDD or BDD.