Plain text
Skill jovd83/Cypress-skill/documentation/test_cases/plain_text
End-to-end Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/Cypress-skill --skill plain_textAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Legacy Cypress-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 Cypress-local conventions must be preserved explicitly.
SKILL.md
1.8 KB, as published. Nobody here has run it
Telemetry & Logging
[!IMPORTANT] All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate:
./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason>(or./log-dispatch.shon Linux)
Documenting Test Cases: Plain Text format
Use this skill when the goal is fast, lightweight documentation rather than a formal template.
Structure
Produce a concise paragraph list or bullet list that covers:
- the goal of the test,
- the setup or preconditions,
- the main execution flow,
- the expected outcome,
- any requirement or risk reference that matters.
Keep the structure simple, but make sure the document is still actionable.
Usage
Use .md or .txt output as requested by the user.
This format is best for rapid capture, early planning, low-ceremony reviews, or transitional documentation that may later be promoted into TDD or BDD artifacts.