arness

This skill should be used when the user says "competitive analysis", "gap analysis", "competitive gap", "stress competitive", "compare competitors", "feature comparison", "competitive stress test", "market comparison", "competitor analysis", or wants to stress-test a product concept by conducting deep competitive gap analysis with feature comparison, gap identification, and positioning assessment. Produces a competitive report with a feature matrix, per-competitor analysis, and recommended concept updates.

This skill should be used when the user says "stress interview", "synthetic interview", "user interview stress test", "interview my personas", "test with synthetic users", "persona interview", "simulate user interviews", "run user interviews", or wants to stress-test a product concept by conducting structured interviews with synthetic personas through three adversarial lenses (Pragmatist, Skeptic, Power User). Produces an interview report with per-persona findings, synthesized themes, and recommended concept updates.

This skill should be used when the user says "pre-mortem", "premortem", "risk analysis", "stress premortem", "failure analysis", "what could go wrong", "pre mortem", "investigate failure", "failure modes", or wants to stress-test a product concept by applying Gary Klein's pre-mortem methodology to identify hypothetical failure root causes, early warning signals, and mitigation strategies. Produces a pre-mortem report with 3 root causes across distinct failure dimensions and recommended concept updates.

This skill should be used when the user says "prfaq", "pr faq", "pr/faq", "press release stress test", "stress prfaq", "amazon pr faq method", "test the pitch with a pr/faq", "validate concept through pr/faq", "critique press release", "pr faq stress test", "will this marketing story hold up", or wants to stress-test a product concept by drafting a compelling press release and FAQ, then adversarially critiquing it to find where the concept cracks under scrutiny. Produces a PR/FAQ report with the full draft, adversarial questions, crack point analysis, and recommended concept updates.

This skill should be used when the user says "style explore", "arn style", "visual style", "explore styles", "UI style", "look and feel", "design direction", "pick a style", "choose colors", "theme the app", "visual direction", "style guide", or wants to explore and define the visual design direction for their project through guided conversation, producing a style brief document with implementable toolkit configuration.

This skill should be used when the user says "use cases", "arn use cases", "write use cases", "define use cases", "Cockburn use cases", "actor goals", "behavioral requirements", "system behavior", "what does the app do", "describe the behavior", "use case document", "document the behavior", "define system behavior", or wants to create structured use case documents that describe the application's behavior from actor perspectives, producing a use-cases/ directory with individual Cockburn fully-dressed use case files and a README index.

This skill should be used when the user says "use cases teams", "arn use cases teams", "team use cases", "debate use cases", "collaborative use cases", "use cases with debate", "team-based use case review", "use case debate", "review use cases as a team", or wants to create structured use case documents through expert debate where product strategist and UX specialist review and discuss each other's findings before revising, producing a use-cases/ directory with individual Cockburn fully-dressed use case files and a README index.

This skill should be used when the user says "visual readiness", "check visual layers", "activate visual layer", "visual checkpoint", "promote visual testing", "enable layer 2", "visual test health", "check deferred layers", "activate deferred layers", "layer promotion", or wants to validate and activate deferred visual testing layers after project milestones.

This skill should be used when the user says "visual sketch", "arn visual sketch", "sketch directions", "explore visuals", "visual proposals", "try different looks", "design directions", "sketch the UI", "visual exploration", "compare styles", "show me options", "what could this look like", or wants to generate multiple visual direction proposals as real HTML/CSS running on the scaffolded project's dev server, iteratively selecting and refining until a final visual direction is chosen.

This skill should be used when the user says "visual strategy", "arn visual strategy", "visual testing", "visual regression", "screenshot testing", "compare to prototype", "visual validation", "how do I test visuals", "set up visual tests", "baseline images", "screenshot comparison", "pixel diff", "visual diff", "does it match the prototype", or wants to set up visual regression testing for development — creating capture scripts, comparison scripts, and baseline images so that feature implementations are automatically compared against prototype screenshots to catch visual regressions during development.