Jason Evanish
Community@evanish · Austin
Jason Evanish publishes structured customer-discovery, ideal-customer profiling, positioning, and startup-viability skills for founders and product strategists.
Agent Skills by Jason Evanish
Showing 18 vetted skills indexed across 1 GitHub repositories.
evanishasb-interview-questions
Converts customer hypotheses into unbiased open-ended interview questions mapped in QUESTIONS.md.
evanishasb-interview-report
Distills customer interview debriefs and hypotheses into a cited final findings report.
evanishasb-carol-dealbreakers
Maps product weaknesses into deal-breakers and hones keystone customer segments with disqualifying qualifiers.
evanishasb-positioning
Rewrites marketing copy into value-first, specific positioning statements recorded in POSITIONING.md.
evanishasb-who-me
Interviews users to map personal drives, hindrances, and strengths into a WHO-ME.md file.
evanishasb-problem
Scores business idea viability across seven multiplying market criteria using Fermi estimation.
evanishasb-carol-keystones
Refines classified product strengths into keystones that identify target market segments.
evanishasb-rude-qa
Interrogates plans, pitches, and decisions with adversarial questions to produce defensible strategic choices.
evanishasb-interview-debrief
Converts raw customer interview transcripts and notes into structured per-question debrief files.
evanishasb-voters
Distills personal or company strengths into one or two decisive strategic advantages recorded in VOTERS.md.
evanishasb-carol-observations
Facilitates structured gathering of raw company observations into a numbered OBSERVATIONS.md file.
evanishasb-interview-learning
Synthesizes customer interview debriefs into evidence-cited hypothesis updates and a stop-or-continue verdict.
evanishasb-carol-strengths
Distills raw company observations into classified strength and weakness attributes in a markdown chart.
evanishasb-interview-goals
Drafts numbered goal questions for customer discovery interviews and saves them to GOALS.md.
evanishasb-carol-inciting-events
Maps customer purchase trigger events to keystones in an INCITING-EVENTS.md file.
evanishasb-interview-hypotheses
Elicits and records falsifiable customer hypotheses mapped to interview goals in HYPOTHESES.md.
evanishasb-carol-define
Synthesizes customer research working files into a CAROL.md ideal customer profile definition.
evanishasb-needs-stack
Builds a customer Needs Stack mapping means-to-end levels into NEEDS-STACK.md.
Frequently Asked Questions About Jason Evanish
FAQPage SchemaWhat tasks can I accomplish with Jason Evanish's skills?▼
You can run a full customer-interview method (goals, hypotheses, questions, debriefs, synthesis, final report), build an ideal-customer profile from observations through keystones and deal-breakers, rewrite positioning copy, score startup idea viability, and stress-test plans with adversarial questioning.
Who are these skills designed for?▼
Founders, product managers, and marketers validating startup ideas, defining ideal customers, or sharpening positioning. They suit B2B and B2C teams doing customer discovery, pricing and messaging decisions, or seeking an honest devil's advocate for strategic plans.
How do the skills work in practice?▼
Each skill facilitates one numbered step of a method, interviewing the user and writing results to structured markdown artifacts (GOALS.md, HYPOTHESES.md, KEYSTONES.md, CAROL.md). Outputs of earlier steps feed later ones, with change logs and resumable numbered items.
What inputs or prerequisites do the skills require?▼
Later-step skills require upstream artifacts: hypotheses need a GOALS.md list, keystones need a classified strengths chart, and the final ICP definition needs strengths, honed keystones, deal-breakers, and inciting events. Entry-point skills like observations, goals, and self-discovery need no prior files.
Do these skills conduct interviews or write final marketing deliverables?▼
No. They prepare, record, and synthesize customer interviews but do not conduct them, and they produce the ICP definition and needs stack that positioning consumes rather than writing ads or feature plans. Each skill explicitly excludes adjacent steps to keep scope narrow.