screenshot-evidence-planner

What problem does it solve?

This Skill defines which screenshots are worth capturing, how to name and store them, and how to prevent evidence from leaking sensitive or cross-tenant data. It turns scattered, inconsistent screenshots into trustworthy release and test artifacts.

Core Features & Use Cases

• Risk-based checkpoint selection: Chooses evidence-worthy states such as requirement proofs, destructive-action before/after states, permission differences, error states, and defect evidence.
• Deterministic evidence conventions: Defines sortable naming patterns, required metadata, and linkage to case IDs, PRs, and closeout reports.
• Masking and retention policy: Mandates block-out masking before storage, sets access rules, and classifies retention by evidence type.
• Use case: A QA lead needs one shared screenshot policy for manual testing, clickthrough sessions, Playwright failures, and compliance review without exposing customer data.

Quick Start

Ask the skill to design a screenshot evidence policy for your release by providing the consumers, risk points, storage options, and masking requirements.