asb-carol-inciting-events

Maps customer purchase trigger events to keystones in an INCITING-EVENTS.md file.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-carol-inciting-events-evanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asb-carol-inciting-events
Source: https://github.com/evanish/reusable-PM-templates/tree/main/Templates%20to%20reuse/Work/asb-customer-discovery/asb-carol-inciting-events
Command: npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-carol-inciting-events-evanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customers can agree a product fits their needs yet still delay buying because nothing forces action now. This Skill identifies the specific inciting events — crises, seasonal cycles, strategic windows, life changes — that move an ideal-fit customer from could-buy-someday to buying-today, so positioning and targeting speak to real purchase moments. ## Core Features & Use Cases - Evidence-first harvesting: Pulls real trigger stories from customer interview findings, debrief files, and surveys, marking them OBSERVED with sources before any brainstorming begins. - Structured hypothesizing: Works backward through brainstorm lenses (crises, seasonal cycles, strategic windows, personal life-changes) for gaps, honestly marked HYPOTHESIZED with a validation path. - Keystone coupling and findability: Every event cites its keystone (K-number) and records how to detect or reach prospects in that condition, including likely search phrases. - Use Case: After defining keystones for your product, run this step to produce INCITING-EVENTS.md listing E1, E2, etc., each with evidence status and findability notes, ready to feed the final ideal-customer definition. ## Quick Start Run the inciting-events step on my KEYSTONES.md and customer interview findings to map what triggers our ideal customers to buy now.

Frequently Asked Questions about asb-carol-inciting-events

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify what triggers customers to buy my product?

Harvest real trigger stories from customer interviews, debriefs, and onboarding surveys first, marking them observed with sources. Then hypothesize remaining gaps through lenses like crises, seasonal cycles, strategic windows, and personal life-changes, marking those hypothesized until validated.

What is an inciting event in customer discovery?

An inciting event is the specific moment that raises a customer's problem to a top-three priority they must solve today, such as a site hack, a compliance deadline, or a crashed peak-traffic day. It couples to a keystone, which explains why they buy from you.

Do I need keystones before mapping inciting events?

Yes, every inciting event must cite a keystone, so a keystones file is required input. Without one, the skill offers to run the keystones step first or capture a minimal caveated list, since triggers mapped without targets describe everyone's bad week.

Can I brainstorm inciting events without customer interviews?

Yes, but all brainstormed events are marked hypothesized with a validation path, never presented as fact. The skill states plainly that everything is hypothesized until customers are asked what prompted them to start looking, ideally right after purchase.

What makes an inciting event usable for advertising?

The event must be vivid — the specific moment, emotion, and number — and include findability notes on how to detect prospects in that condition, including their likely search phrases. Generic triggers like 'realizes they need a better solution' are refused.