{"id":77027,"plugin_id":"plugins_6ab4123730588191bc9267b9458b2670","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:19.895Z","digest":"531a37105a31266bb6e5b973f605101daee13d077a1da631b4522965886579f0","against":null,"payload":{"description":"Audit existing product experiences or workflows with evidence-backed, prioritized improvements.","included_files":[],"name":"audit-existing-product","skill_md_contents":"---\nname: audit-existing-product\ndescription: Audit existing product experiences or workflows with evidence-backed, prioritized improvements.\n---\n\n# Audit Existing Product\n\n## When to use\nAudit existing product experiences or workflows with evidence-backed, prioritized improvements.\n\n## Workflow\nInspect screenshots, user journey, site, notes, analytics or repository before assessing. Declare which surfaces were actually observed. Walk the core user outcome and mark strengths, friction, states and recoverability. Separate UX defects, broken behavior, unclear product value and technical debt. Give each issue impact, confidence, evidence and smallest feasible fix.\n\nPreserve working behavior. Identify the first three highest-leverage improvements and their verification. Don't claim usage statistics or missing backend behavior from screenshots. Use `../../references/product-audit.md` and original UX guidance in `../../references/original/ux_flow_and_state_patterns.md`.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/product-audit.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}