| name | playwright-documentation-plaintext |
| description | Legacy Playwright-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Playwright-local conventions must be preserved explicitly. |
| metadata | {"author":"jovd83","version":"2.0.0","dispatcher-category":"testing","dispatcher-capabilities":"test-artifact-formatting, playwright-legacy-test-case-formatting","dispatcher-accepted-intents":"render_test_artifact, export_test_cases","dispatcher-input-artifacts":"approved_test_cases, normalized_test_case_model, scenario_list","dispatcher-output-artifacts":"formatted_test_artifact, export_ready_case_set","dispatcher-stack-tags":"playwright, documentation, legacy-alias","dispatcher-risk":"low","dispatcher-writes-files":true} |
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.
