{"schema":"ai-blocks-role/1","id":"idea-worth-building","name":"Customer interview evidence planner","summary":"Give it your idea in a sentence or two, and who you think it's for. You get the group to talk to first, with where to find them this week.","area":"product","family":{"id":"test-an-idea","name":"Test an idea before you build it"},"lead":"idea-worth-building","featured":false,"contextKind":"product","deliverables":["The group to talk to first, with where to find them this week","Messages that get you the conversations","A question guide about their life, your big three unknowns and the scary question, planned","Your notes sorted into what people did, gave up and committed to, with the weak signals flagged","A keep going, change or stop call with the reason, and the next three talks to have"],"inputs":["Your idea in a sentence or two, and who you think it's for","Any group of customers you already have in mind, and where they spend time (optional)","Your notes from the talks, for the second half"],"opening":{"give":["Your idea in a sentence or two, and who you think it's for","Any group of customers you already have in mind, and where they spend time (optional)","Your notes from the talks, for the second half"],"get":["The group to talk to first, with where to find them this week","Messages that get you the conversations","A question guide about their life, your big three unknowns and the scary question, planned","Your notes sorted into what people did, gave up and committed to, with the weak signals flagged"]},"helpfulInputs":["Notes from each conversation, written straight after, in the person's own words","What you're most afraid to hear about your idea","Where your customers already gather, such as groups, events or forums"],"fit":["You have an idea and want to know if it's worth building before you spend time or money on it.","You've talked to people, everyone liked the idea, and you still don't know if anyone will pay.","You're choosing between two ideas, or two groups of customers, and want evidence instead of a hunch."],"limits":["Your idea is already proven and people pay for it: use the Seven-question startup scorer to test the next step.","You have no customers to talk to yet: use the Customer community finder to find where they gather, then come back.","You want to learn why past buyers chose you: use the Customer purchase interview script writer."],"tools":["Claude: Holds the questions, the notes from ten talks and six steps of work in one run.","A notes app or voice memo: Lets you write or record what was said straight after each talk, in their words.","Any good chat AI: Slicing and scoring are text work that any strong chat AI does well with this skill.","LinkedIn search: Shows quickly whether a slice has enough findable people in one place.","Any good chat AI: Short message drafting works well in any strong chat AI with this skill.","LinkedIn: A common place to find the person and a friend who knows them.","Any good chat AI: Rewriting and ranking questions is text work any strong chat AI does well with this skill.","A pocket notebook or index cards: Easier than a laptop for keeping your three questions in view during a casual chat.","Any good chat AI: Sorting and tagging notes is text work that any strong chat AI does well with this skill.","A shared spreadsheet or index cards: Sorted notes are easy to filter by mark when each item has its own row or card.","Any good chat AI: Sorting replies and writing asks is text work any strong chat AI does well with this skill.","A shared spreadsheet: One row per lead, with the last commitment and date, makes zombie leads obvious.","Any good chat AI: Weighing notes against beliefs is text work any strong chat AI does well with this skill.","A shared document: Keeping beliefs, notes and calls in one place lets a partner check your reasoning."],"method":["Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.","Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say \"Follow HANDOFF.md\".","Describe your idea in a sentence or two. It runs the first half and stops.","Send the messages and have five to ten conversations. Write notes straight after each one, as close to their words as you can.","Bring the notes back and say \"carry on from step 4\". Read the call last, with the evidence it rests on."],"capabilities":[{"name":"Picks who to talk to","description":"Slices the market until there's a who and a where you could reach this week, and picks the group to start with."},{"name":"Writes the messages","description":"Warm-intro and cold messages that ask for help, not a sale, and keep it casual."},{"name":"Writes the questions","description":"Questions about their life and their past, never about your idea, plus the three unknowns that could change the plan and the question you're afraid to ask."},{"name":"Sorts what you heard","description":"Splits your notes into what they did, what it cost them and what they committed to. Compliments, vague claims and feature ideas are flagged as weak."},{"name":"Plans the commitment","description":"For each person, the next step to ask for in time, reputation or money, and who is all praise and no commitment."},{"name":"Makes the call","description":"Sets what you believed against what people did, then says keep going, change or stop, and lists the next three talks."}],"expertise":{"principles":["Start from the user problem and the evidence for it, then the solution.","Write decisions down with the reason and the options you rejected.","Keep scope small enough to ship and learn. Name what is out of scope.","Define how success will be measured before building."],"pitfalls":["Running the second half on made-up or imagined answers.","Counting \"I'd buy that\" or \"great idea\" as proof.","Skipping the scary question because it's uncomfortable.","Treating opinions or one loud request as proven demand.","Specs that skip edge cases, error states or dependencies.","Roadmaps with dates but no owners or confidence levels."],"quality":["Each step passed its own checks, or the run stopped at the step that failed and says why.","No question or message pitches the idea before learning about the person's life.","The call in step 6 rests on what people did or gave up (time, reputation, money), never on compliments alone.","Nothing was sent, posted or charged without the person's clear yes.","Every requirement can be tested.","Assumptions and risks are listed with how each will be checked.","Dependencies and owners are named."],"sources":{"learned":0,"curated":false,"method":7,"source":0,"area":"product"}},"workedExample":{"situation":"You have an idea and want to know if it's worth building before you spend time or money on it.","task":"Give it your idea in a sentence or two, and who you think it's for. Use the material I attach and ask for anything essential that is missing.","given":["Your idea in a sentence or two, and who you think it's for","A customer group you already have in mind (optional)","Your notes from each talk, for the second half: date, their words, what they did, what they offered"],"outputs":[{"name":"First customer group","contains":"The group to talk to first, and where you could reach them this week."},{"name":"Interview messages","contains":"A warm-intro message and a cold message that ask for help, not a sale."},{"name":"Question guide","contains":"Questions about their life, the big three unknowns and a plan for the scary question."},{"name":"Sorted notes","contains":"Each talk split into what they did, what it cost them and what they committed to, with weak signals flagged."},{"name":"Ask plan","contains":"The next step to ask each person for in time, reputation or money."},{"name":"Idea evidence review","contains":"A keep going, change or stop call, the reason, and the next three talks."}]},"example":"Give it your idea in a sentence or two, and who you think it's for. Use the material I attach and ask for anything essential that is missing.","functions":[{"name":"Customer interview evidence planner","description":"Share an idea and real customer notes when available. Get interview plans, outreach drafts, evidence sorting and a reasoned next-step review.","method":"idea-worth-building","when":["You have an idea and want to know if it's worth building before you spend time or money on it.","You've talked to people, everyone liked the idea, and you still don't know if anyone will pay.","You're choosing between two ideas, or two groups of customers, and want evidence instead of a hunch."],"inputs":["Your idea in a sentence or two, and who you think it's for","Any group of customers you already have in mind, and where they spend time (optional)","Your notes from the talks, for the second half"],"deliverables":["The group to talk to first, with where to find them this week","Messages that get you the conversations","A question guide about their life, your big three unknowns and the scary question, planned","Your notes sorted into what people did, gave up and committed to, with the weak signals flagged","A keep going, change or stop call with the reason, and the next three talks to have"]},{"name":"First customer group picker","description":"Pick your first customer group from a broad market. Slice it into people you can find, then get the one group to talk to first.","method":"first-customer-group-picker","when":["Your market feels huge and you don't know who to talk to first.","Your last few customer conversations all gave different answers.","You have an idea but no names, places or contacts yet."],"inputs":["Your idea in a sentence or two, and the broad group you think wants it","What you already know about the problem and who has it (optional)","Where you can reach people today, such as groups, events, clients or friends of friends (optional)","Any people you have already talked to and what they did about the problem (optional)"],"deliverables":["A list of narrower groups, each with why they want it and what they already do about it","A who-and-where pair for every group you could actually reach","The one group to start with, a backup, and why, scored on pay, reach and fit for you","A plan for your first week of conversations"]},{"name":"Customer conversation request writer","description":"Write a customer interview request that gets a yes. Give it who you want to meet. You get a warm intro note, a cold message and an opening line.","method":"customer-interview-request","when":["You know who you want to talk to but can't get a first meeting.","A friend offered an introduction and you need to make it easy to forward.","You're about to message strangers and your draft sounds like a sales pitch."],"inputs":["Who you want to talk to and what you're trying to learn","How you could reach them, such as people you know, events, places, a blog or none yet","What you are stuck on, in a line","What stage you're at and whether you have anything to sell (optional)"],"deliverables":["The easiest route to a first conversation, casual before formal","A message in the five-part shape for a warm intro, a cold approach or a friend to forward","An opening for the meeting that keeps you in charge","A list of wording to avoid"]},{"name":"Customer interview question writer","description":"Write customer interview questions about their real life, not your idea. Get fixed drafts, your top three questions and a plan for the scary one.","method":"customer-interview-questions","when":["You're about to talk to customers and your questions start with \"would you\".","You have a long list of questions and don't know which ones matter.","You keep avoiding one question because the answer might hurt."],"inputs":["Your idea in a sentence, and the type of person you'll talk to","Your draft questions, good or bad (optional)","What you already know and what you're unsure of (optional)","A group from \"First customer group picker\" (optional)"],"deliverables":["Your questions rewritten, each with what was wrong and what the new one tests","Your top three questions for this type of person","A plan for the scariest question, including what answer would change your mind","Short lines for pulling a drifting conversation back"]},{"name":"Customer conversation notes sorter","description":"Sort raw customer interview notes into facts, compliments and feature ideas. Get a follow-up question for every weak note.","method":"customer-interview-notes","when":["You've done a few conversations and your notes are a mix of quotes and feelings.","Everyone you spoke to \"liked it\" and you don't know what to do next.","You need to share what customers said with a team without handing over just your opinion."],"inputs":["Your notes from one or more conversations, as rough as they are","Who each was with and the date, if you have it (optional)","Your big three questions or what you were trying to learn (optional)","Exact quotes in quotation marks, where you have them (optional)"],"deliverables":["Every note tagged with a symbol and marked as fact, compliment, fluff or idea","The follow-up question for each weak note","A summary of the real signals (pains, goals, obstacles, workarounds and money)","A judgement of each person as a customer, a complainer or not a customer"]},{"name":"Sales next-step planner","description":"Plan the commitment to ask for after a meeting, and sort what people said into real leads, stalls and polite no's. Say your stage and what they said.","method":"commitment-ask-planner","when":["You finish meetings with praise and no clear next step.","People say \"I'd definitely buy that\" and then go quiet.","You have a list of leads and can't tell which are real."],"inputs":["What you have today, such as an idea, a prototype or a product","What each person said or did at the end of the meeting","What you'd like to happen next, if you know (optional)","Notes sorted by the Customer conversation notes sorter (optional)"],"deliverables":["The commitment to ask for, in time, reputation or money, sized to your stage","The exact words to ask, and a fallback if they say no","Each reply sorted into compliment, stall, fuzzy promise or real commitment","A verdict on each lead, and the one question that settles it"]},{"name":"Idea evidence reviewer","description":"Check your customer talk notes against what you believed. Get a keep going, change or stop call on your idea, plus your next three talks.","method":"idea-evidence-review","when":["You've done five or so customer talks and don't know what they add up to.","Everyone seemed positive but nobody has paid, booked or introduced you.","You need to tell a partner or investor what you've really learned."],"inputs":["What you believed before the talks, and your big questions","Your notes, ideally already sorted by the Customer conversation notes sorter","What people committed to, if anything (time, introductions or money)","How many people you talked to, and which types (optional)"],"deliverables":["Each belief marked supported, weakened, untested or wrong, with the evidence","The traps that may be skewing what you heard","A keep going, change or stop call, with the reason and a stop rule","Your next three questions and the next three conversations to have"]},{"name":"Product context file writer","description":"Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.","method":"product-context-builder","when":["You are starting a new marketing project and want one source of truth.","You keep pasting the same product background into every chat.","Your positioning changed and old notes are out of date.","A new teammate needs to learn the audience and tone fast."],"inputs":["Answers about your product and customers","Your website or existing brand notes (optional)","Competitor names (optional)","Any recent learnings to record (optional)"],"deliverables":["A product marketing context file","A summary of what the file already holds","A change log of updates","Gaps you still need to fill"]},{"name":"Rob Fitzpatrick","description":"Improve customer questions or review interview notes using Rob Fitzpatrick’s Mom Test approach. Ask about past behavior and separate facts from praise.","method":"rob-fitzpatrick","when":["Rewrite the questions you plan to ask customers so they can't just be nice to you","Pick one narrow group to talk to first from a market that feels too big","Write a short message that gets a busy stranger to give you 15 minutes","Sort your notes from ten conversations into facts, compliments and noise","Decide what to ask for at the end of a meeting so it doesn't just 'go well'","Work out if a friend's or customer's enthusiasm for your idea is worth anything","Pick the three scariest questions to ask this week","Check whether a feature request is the real need or a guess at a fix","Decide whether to keep going, change or stop after a round of talks","Plan a conversation inside a team so one person isn't the only source of what customers said"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["Your problem worked on the way Rob Fitzpatrick would: their questions, their method, their push-back","The answer or the work, in Rob Fitzpatrick's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"]},{"name":"Steve Blank","description":"Test your startup assumptions with Steve Blank's customer development method. Get a guess list, a one-page model and your next customer interviews.","method":"steve-blank","when":["List the guesses behind a business plan: customers, channels, pricing, demand and partners","Plan a round of customer interviews to test those guesses outside the office","Sketch a business model on one page and mark which parts are proven","Decide whether your venture is still searching for a model or ready to execute one","Spot when a launch date has replaced real learning about customers","Keep founders, not hired staff, in direct contact with early customers","Decide what to change when an experiment fails: the product, the customer or the model","Set up a new project inside a big organization so it can search before it scales"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["Your problem worked on the way Steve Blank would: their questions, their method, their push-back","The answer or the work, in Steve Blank's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"]}],"resources":[{"slug":"idea-worth-building","name":"Customer interview evidence planner","summary":"Share an idea and real customer notes when available. Get interview plans, outreach drafts, evidence sorting and a reasoned next-step review.","task":"test-an-idea","kind":"workflow","path":"/workflows/idea-worth-building","revision":"cbbad49f9724553647009d208a1b9502799a52bd1d27f3aab79ddcb5dd7372f6","skillPath":"/skills/idea-worth-building/SKILL.md","bundled":false,"onboarding":false},{"slug":"first-customer-group-picker","name":"First customer group picker","summary":"Pick your first customer group from a broad market. Slice it into people you can find, then get the one group to talk to first.","task":"test-an-idea","kind":"skill","path":"/skills/first-customer-group-picker","revision":"1c619aa157ac84b27c1e78f7b5b3b7f68e6285d1c17da15fcf7d6c385753420a","skillPath":"/skills/first-customer-group-picker/SKILL.md","bundled":true,"onboarding":false},{"slug":"customer-interview-request","name":"Customer conversation request writer","summary":"Write a customer interview request that gets a yes. Give it who you want to meet. You get a warm intro note, a cold message and an opening line.","task":"test-an-idea","kind":"skill","path":"/skills/customer-interview-request","revision":"6ee1162902db3cb5f00d4a28c62b7b81c76c7bca2aaa80949276d5ab7f217a39","skillPath":"/skills/customer-interview-request/SKILL.md","bundled":true,"onboarding":false},{"slug":"customer-interview-questions","name":"Customer interview question writer","summary":"Write customer interview questions about their real life, not your idea. Get fixed drafts, your top three questions and a plan for the scary one.","task":"test-an-idea","kind":"skill","path":"/skills/customer-interview-questions","revision":"93ac992f0b0f44c3f63c1007a8a22e276f1f22e5e23897d0a3f845183c6ec38d","skillPath":"/skills/customer-interview-questions/SKILL.md","bundled":true,"onboarding":false},{"slug":"customer-interview-notes","name":"Customer conversation notes sorter","summary":"Sort raw customer interview notes into facts, compliments and feature ideas. Get a follow-up question for every weak note.","task":"understand-customers","kind":"skill","path":"/skills/customer-interview-notes","revision":"cb176e4c3366e54c97e47db0a90bc78caefb5d577f4bbd148503cb81428243aa","skillPath":"/skills/customer-interview-notes/SKILL.md","bundled":true,"onboarding":false},{"slug":"commitment-ask-planner","name":"Sales next-step planner","summary":"Plan the commitment to ask for after a meeting, and sort what people said into real leads, stalls and polite no's. Say your stage and what they said.","task":"test-an-idea","kind":"skill","path":"/skills/commitment-ask-planner","revision":"5340a47f62b9ee47e3b7fd15976516b29512ca184ed71df179ba53d7c2e27d0f","skillPath":"/skills/commitment-ask-planner/SKILL.md","bundled":true,"onboarding":false},{"slug":"idea-evidence-review","name":"Idea evidence reviewer","summary":"Check your customer talk notes against what you believed. Get a keep going, change or stop call on your idea, plus your next three talks.","task":"test-an-idea","kind":"skill","path":"/skills/idea-evidence-review","revision":"4139c1ca7e4e5c7e7ac199a6188995abd4aedb6d7ab1f329e82cb887c7ce70ed","skillPath":"/skills/idea-evidence-review/SKILL.md","bundled":true,"onboarding":false},{"slug":"product-context-builder","name":"Product context file writer","summary":"Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.","task":"brand-file","kind":"skill","path":"/skills/product-context-builder","revision":"2fe017f2b8b417b6dd382b110c57a4f0619bff4b1b88d50e4fbe771219d3f78b","skillPath":"/skills/product-context-builder/SKILL.md","bundled":false,"onboarding":true,"by":"Corey Haines"},{"slug":"rob-fitzpatrick","name":"Rob Fitzpatrick","summary":"Improve customer questions or review interview notes using Rob Fitzpatrick’s Mom Test approach. Ask about past behavior and separate facts from praise.","task":"think-with-minds","kind":"mind","path":"/minds/rob-fitzpatrick","revision":"4c5c9e3c92f5cfe656481e0bf0d993e1255963a0418e023ca42fd6055d5eb84b","skillPath":"/skills/rob-fitzpatrick/SKILL.md","bundled":false,"onboarding":false,"reviewer":true},{"slug":"steve-blank","name":"Steve Blank","summary":"Test your startup assumptions with Steve Blank's customer development method. Get a guess list, a one-page model and your next customer interviews.","task":"think-with-minds","kind":"mind","path":"/minds/steve-blank","revision":"f769c38c7123609f114aec97ae717e067b9c9aed6fb57db3a9653f5e5a4257a0","skillPath":"/skills/steve-blank/SKILL.md","bundled":false,"onboarding":false,"reviewer":true}],"resourceCount":10,"sourceChecks":{"completeMethods":10,"referenceValidation":"PASS"},"catalogueHash":"3c3567ac2dbda7b2ac0cfaa8c93d8da3818f66bdadd51f18d8ff9051d77fc8f3","evaluation":{"status":"NOT_RUN","rubric":[{"id":"c1","criterion":"Delivers: The group to talk to first, with where to find them this week"},{"id":"c2","criterion":"Delivers: Messages that get you the conversations"},{"id":"c3","criterion":"Delivers: A question guide about their life, your big three unknowns and the scary question, planned"},{"id":"c4","criterion":"Delivers: Your notes sorted into what people did, gave up and committed to, with the weak signals flagged"},{"id":"c5","criterion":"Each step passed its own checks, or the run stopped at the step that failed and says why."},{"id":"c6","criterion":"No question or message pitches the idea before learning about the person's life."},{"id":"c7","criterion":"The call in step 6 rests on what people did or gave up (time, reputation, money), never on compliments alone."},{"id":"c8","criterion":"Nothing was sent, posted or charged without the person's clear yes."},{"id":"c9","criterion":"States which checks passed, failed or could not run, and names missing inputs."}],"goldenTasks":[{"id":"g1","kind":"core","situation":"You have an idea and want to know if it's worth building before you spend time or money on it.","expect":["The group to talk to first, with where to find them this week","Messages that get you the conversations","A question guide about their life, your big three unknowns and the scary question, planned"]},{"id":"g2","kind":"core","situation":"You've talked to people, everyone liked the idea, and you still don't know if anyone will pay.","expect":["The group to talk to first, with where to find them this week","Messages that get you the conversations","A question guide about their life, your big three unknowns and the scary question, planned"]},{"id":"g-missing","kind":"missing-input","situation":"The request leaves out: Your idea in a sentence or two, and who you think it's for","expect":["Names the missing input and asks for it, or finishes only the parts that do not depend on it."]}],"note":"These checks are defined but have not been run against a model yet."},"version":{"number":3,"since":"2026-11-03","changes":[{"version":3,"date":"2026-11-03","what":"Source methods updated to new revisions."},{"version":2,"date":"2026-11-03","what":"Updated scope, deliverables or inputs. Updated worked example."},{"version":1,"date":"2026-11-02","what":"First recorded version."}]},"learning":{"rules":[],"maturity":{"level":0,"name":"Not measured yet","runs":0,"score":0,"editRatio":0,"acceptance":0,"critical":0,"next":"10 reviewed jobs, average check score 70%+"}},"worker":{"schema":"ai-blocks-specialist-worker/1","id":"idea-worth-building","name":"Customer interview evidence planner","interface":{"inputs":[{"type":"short_text","required":true}],"outputs":[{"type":"document","required":true}],"brief":"The current task in the workflow goal and supplied context.","handoff":"work/handoff.md indexes the actual native deliverables and checks. An index does not replace a requested implementation."},"identity":{"remit":"Give it your idea in a sentence or two, and who you think it's for. You get the group to talk to first, with where to find them this week.","capabilities":[{"name":"Picks who to talk to","description":"Slices the market until there's a who and a where you could reach this week, and picks the group to start with."},{"name":"Writes the messages","description":"Warm-intro and cold messages that ask for help, not a sale, and keep it casual."},{"name":"Writes the questions","description":"Questions about their life and their past, never about your idea, plus the three unknowns that could change the plan and the question you're afraid to ask."},{"name":"Sorts what you heard","description":"Splits your notes into what they did, what it cost them and what they committed to. Compliments, vague claims and feature ideas are flagged as weak."},{"name":"Plans the commitment","description":"For each person, the next step to ask for in time, reputation or money, and who is all praise and no commitment."},{"name":"Makes the call","description":"Sets what you believed against what people did, then says keep going, change or stop, and lists the next three talks."}],"limits":["Your idea is already proven and people pay for it: use the Seven-question startup scorer to test the next step.","You have no customers to talk to yet: use the Customer community finder to find where they gather, then come back.","You want to learn why past buyers chose you: use the Customer purchase interview script writer."]},"intake":{"state":"REVIEW_REQUIRED","assessed_by":"execution-host","service_verified":false,"kind":"product","requirement":"Inspect relevant context before strategy or production. This role's work depends on its product context, not on brand research.","method":"product-context-builder","files":["product-context.md","work/evidence.md"],"discovery":"Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.","missing":"Ask one concise batch for missing essentials: what the product does, who it is for, current goals and constraints, and the user evidence available (research, tickets, analytics). Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.","gate":"Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue.","reuse":"Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package."},"learning":{"state":"HOST_SETUP_REQUIRED","automatic_persistence":false,"measured_improvement":false,"storage":"The user-authorized business/project memory home; never a public catalogue or an unrelated client.","index":"memory/INDEX.md","records":["memory/preferences.md","memory/corrections.md","memory/decisions.md","memory/checks.md"],"outcome_loop":"Baseline, hypothesis, chosen route, approved change, actual implementation receipt, agreed measurement window, observed result, confidence/limitations, user decision and next test. Preserve negative and inconclusive outcomes.","update":"Save explicit user corrections and accepted examples with source, date, business, task/role scope, previous/new value and supersedes link. Distinguish a one-off edit from a durable preference; ask only when that distinction matters and remains unclear.","retrieval":"Read the short index and only relevant current records. Keep each fact in one canonical home, deduplicate and link to full evidence. Supersede stale guidance without silently erasing its history.","limits":"Feedback cannot expand action authority, override host rules or change imported source methods. Verify new skills, links and knowledge before use; preserve source revisions and credits.","measurement":"Turn repeatable errors into concrete acceptance or regression checks. Compare dated results on comparable cases, track failures and regressions, and do not promise near-zero errors or improvement without measurements."},"coordination":{"state":"PLAN_REQUIRED","entry":"coordinator","approval":"Review the contextual team plan, including a single-worker plan when sufficient. Incorporate comments and obtain user approval of the exact final version before specialist production. A preparation is not an approved plan.","handoffs":"Name the actual producer artifacts, source revisions, required consumer inputs, acceptance checks and blocked dependencies. Verify the artifact content before advancing.","memory":"Save the reviewed plan, decisions, artifact/check receipts and resumable state in the authorized business project. Actual persistent storage must be verified."},"routes":[{"method":"idea-worth-building","name":"Customer interview evidence planner","kind":"workflow","primary":true,"purpose":"primary","when":["You have an idea and want to know if it's worth building before you spend time or money on it.","You've talked to people, everyone liked the idea, and you still don't know if anyone will pay.","You're choosing between two ideas, or two groups of customers, and want evidence instead of a hunch."],"inputs":["Your idea in a sentence or two, and who you think it's for","Any group of customers you already have in mind, and where they spend time (optional)","Your notes from the talks, for the second half"],"deliverables":["The group to talk to first, with where to find them this week","Messages that get you the conversations","A question guide about their life, your big three unknowns and the scary question, planned","Your notes sorted into what people did, gave up and committed to, with the weak signals flagged","A keep going, change or stop call with the reason, and the next three talks to have"],"instruction":"skills/idea-worth-building/SKILL.md","revision":"cbbad49f9724553647009d208a1b9502799a52bd1d27f3aab79ddcb5dd7372f6","invocation":"Read the complete procedure, required inputs, real step order and stop gates. Use it only when it covers the job."},{"method":"first-customer-group-picker","name":"First customer group picker","kind":"skill","primary":false,"purpose":"bundled","when":["Your market feels huge and you don't know who to talk to first.","Your last few customer conversations all gave different answers.","You have an idea but no names, places or contacts yet."],"inputs":["Your idea in a sentence or two, and the broad group you think wants it","What you already know about the problem and who has it (optional)","Where you can reach people today, such as groups, events, clients or friends of friends (optional)","Any people you have already talked to and what they did about the problem (optional)"],"deliverables":["A list of narrower groups, each with why they want it and what they already do about it","A who-and-where pair for every group you could actually reach","The one group to start with, a backup, and why, scored on pay, reach and fit for you","A plan for your first week of conversations"],"instruction":"skills/first-customer-group-picker/SKILL.md","revision":"1c619aa157ac84b27c1e78f7b5b3b7f68e6285d1c17da15fcf7d6c385753420a","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"customer-interview-request","name":"Customer conversation request writer","kind":"skill","primary":false,"purpose":"bundled","when":["You know who you want to talk to but can't get a first meeting.","A friend offered an introduction and you need to make it easy to forward.","You're about to message strangers and your draft sounds like a sales pitch."],"inputs":["Who you want to talk to and what you're trying to learn","How you could reach them, such as people you know, events, places, a blog or none yet","What you are stuck on, in a line","What stage you're at and whether you have anything to sell (optional)"],"deliverables":["The easiest route to a first conversation, casual before formal","A message in the five-part shape for a warm intro, a cold approach or a friend to forward","An opening for the meeting that keeps you in charge","A list of wording to avoid"],"instruction":"skills/customer-interview-request/SKILL.md","revision":"6ee1162902db3cb5f00d4a28c62b7b81c76c7bca2aaa80949276d5ab7f217a39","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"customer-interview-questions","name":"Customer interview question writer","kind":"skill","primary":false,"purpose":"bundled","when":["You're about to talk to customers and your questions start with \"would you\".","You have a long list of questions and don't know which ones matter.","You keep avoiding one question because the answer might hurt."],"inputs":["Your idea in a sentence, and the type of person you'll talk to","Your draft questions, good or bad (optional)","What you already know and what you're unsure of (optional)","A group from \"First customer group picker\" (optional)"],"deliverables":["Your questions rewritten, each with what was wrong and what the new one tests","Your top three questions for this type of person","A plan for the scariest question, including what answer would change your mind","Short lines for pulling a drifting conversation back"],"instruction":"skills/customer-interview-questions/SKILL.md","revision":"93ac992f0b0f44c3f63c1007a8a22e276f1f22e5e23897d0a3f845183c6ec38d","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"customer-interview-notes","name":"Customer conversation notes sorter","kind":"skill","primary":false,"purpose":"bundled","when":["You've done a few conversations and your notes are a mix of quotes and feelings.","Everyone you spoke to \"liked it\" and you don't know what to do next.","You need to share what customers said with a team without handing over just your opinion."],"inputs":["Your notes from one or more conversations, as rough as they are","Who each was with and the date, if you have it (optional)","Your big three questions or what you were trying to learn (optional)","Exact quotes in quotation marks, where you have them (optional)"],"deliverables":["Every note tagged with a symbol and marked as fact, compliment, fluff or idea","The follow-up question for each weak note","A summary of the real signals (pains, goals, obstacles, workarounds and money)","A judgement of each person as a customer, a complainer or not a customer"],"instruction":"skills/customer-interview-notes/SKILL.md","revision":"cb176e4c3366e54c97e47db0a90bc78caefb5d577f4bbd148503cb81428243aa","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"commitment-ask-planner","name":"Sales next-step planner","kind":"skill","primary":false,"purpose":"bundled","when":["You finish meetings with praise and no clear next step.","People say \"I'd definitely buy that\" and then go quiet.","You have a list of leads and can't tell which are real."],"inputs":["What you have today, such as an idea, a prototype or a product","What each person said or did at the end of the meeting","What you'd like to happen next, if you know (optional)","Notes sorted by the Customer conversation notes sorter (optional)"],"deliverables":["The commitment to ask for, in time, reputation or money, sized to your stage","The exact words to ask, and a fallback if they say no","Each reply sorted into compliment, stall, fuzzy promise or real commitment","A verdict on each lead, and the one question that settles it"],"instruction":"skills/commitment-ask-planner/SKILL.md","revision":"5340a47f62b9ee47e3b7fd15976516b29512ca184ed71df179ba53d7c2e27d0f","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"idea-evidence-review","name":"Idea evidence reviewer","kind":"skill","primary":false,"purpose":"bundled","when":["You've done five or so customer talks and don't know what they add up to.","Everyone seemed positive but nobody has paid, booked or introduced you.","You need to tell a partner or investor what you've really learned."],"inputs":["What you believed before the talks, and your big questions","Your notes, ideally already sorted by the Customer conversation notes sorter","What people committed to, if anything (time, introductions or money)","How many people you talked to, and which types (optional)"],"deliverables":["Each belief marked supported, weakened, untested or wrong, with the evidence","The traps that may be skewing what you heard","A keep going, change or stop call, with the reason and a stop rule","Your next three questions and the next three conversations to have"],"instruction":"skills/idea-evidence-review/SKILL.md","revision":"4139c1ca7e4e5c7e7ac199a6188995abd4aedb6d7ab1f329e82cb887c7ce70ed","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"product-context-builder","name":"Product context file writer","kind":"skill","primary":false,"purpose":"context","when":["You are starting a new marketing project and want one source of truth.","You keep pasting the same product background into every chat.","Your positioning changed and old notes are out of date.","A new teammate needs to learn the audience and tone fast."],"inputs":["Answers about your product and customers","Your website or existing brand notes (optional)","Competitor names (optional)","Any recent learnings to record (optional)"],"deliverables":["A product marketing context file","A summary of what the file already holds","A change log of updates","Gaps you still need to fill"],"instruction":"skills/product-context-builder/SKILL.md","revision":"2fe017f2b8b417b6dd382b110c57a4f0619bff4b1b88d50e4fbe771219d3f78b","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"rob-fitzpatrick","name":"Rob Fitzpatrick","kind":"mind","primary":false,"purpose":"review","when":["Rewrite the questions you plan to ask customers so they can't just be nice to you","Pick one narrow group to talk to first from a market that feels too big","Write a short message that gets a busy stranger to give you 15 minutes","Sort your notes from ten conversations into facts, compliments and noise","Decide what to ask for at the end of a meeting so it doesn't just 'go well'","Work out if a friend's or customer's enthusiasm for your idea is worth anything","Pick the three scariest questions to ask this week","Check whether a feature request is the real need or a guess at a fix","Decide whether to keep going, change or stop after a round of talks","Plan a conversation inside a team so one person isn't the only source of what customers said"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["Your problem worked on the way Rob Fitzpatrick would: their questions, their method, their push-back","The answer or the work, in Rob Fitzpatrick's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"],"instruction":"skills/rob-fitzpatrick/SKILL.md","revision":"4c5c9e3c92f5cfe656481e0bf0d993e1255963a0418e023ca42fd6055d5eb84b","invocation":"Read the mind file. Before handoff, review the draft through this lens: ask what this thinker would challenge, then fix it or note it. Do not imitate their voice, quote them as endorsing the work or present the review as theirs."},{"method":"steve-blank","name":"Steve Blank","kind":"mind","primary":false,"purpose":"review","when":["List the guesses behind a business plan: customers, channels, pricing, demand and partners","Plan a round of customer interviews to test those guesses outside the office","Sketch a business model on one page and mark which parts are proven","Decide whether your venture is still searching for a model or ready to execute one","Spot when a launch date has replaced real learning about customers","Keep founders, not hired staff, in direct contact with early customers","Decide what to change when an experiment fails: the product, the customer or the model","Set up a new project inside a big organization so it can search before it scales"],"inputs":["Your task or question","Your facts, numbers or draft (optional; it asks once if they matter)","A role for them, such as \"my investor\" (optional)"],"deliverables":["Your problem worked on the way Steve Blank would: their questions, their method, their push-back","The answer or the work, in Steve Blank's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"],"instruction":"skills/steve-blank/SKILL.md","revision":"f769c38c7123609f114aec97ae717e067b9c9aed6fb57db3a9653f5e5a4257a0","invocation":"Read the mind file. Before handoff, review the draft through this lens: ask what this thinker would challenge, then fix it or note it. Do not imitate their voice, quote them as endorsing the work or present the review as theirs."}],"connections":[{"name":"Claude: Holds the questions, the notes from ten talks and six steps of work in one run.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"A notes app or voice memo: Lets you write or record what was said straight after each talk, in their words.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Slicing and scoring are text work that any strong chat AI does well with this skill.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"LinkedIn search: Shows quickly whether a slice has enough findable people in one place.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Short message drafting works well in any strong chat AI with this skill.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"LinkedIn: A common place to find the person and a friend who knows them.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Rewriting and ranking questions is text work any strong chat AI does well with this skill.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"A pocket notebook or index cards: Easier than a laptop for keeping your three questions in view during a casual chat.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Sorting and tagging notes is text work that any strong chat AI does well with this skill.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"A shared spreadsheet or index cards: Sorted notes are easy to filter by mark when each item has its own row or card.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Sorting replies and writing asks is text work any strong chat AI does well with this skill.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"A shared spreadsheet: One row per lead, with the last commitment and date, makes zombie leads obvious.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: Weighing notes against beliefs is text work any strong chat AI does well with this skill.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"A shared document: Keeping beliefs, notes and calls in one place lets a partner check your reasoning.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."}],"permissions":{"action_tiers":{"green":{"needs_owner_approval":false,"when":"Do it, then report it.","actions":["Read the files and exports the user supplied.","Read reports and settings in the tools from CONNECTIONS.md, read-only, once access is checked.","Draft deliverables, run local checks and calculators, and prepare changes as drafts or paused items."]},"yellow":{"needs_owner_approval":true,"when":"None by default. Once the owner writes a limit in PERMISSIONS.md, act inside it and tell the owner the same day.","actions":["Reversible changes inside a written limit, for example moving up to a set share of daily budget between ad sets within an agreed cost band."]},"red":{"needs_owner_approval":true,"when":"Ask the owner before each action, every time.","actions":["Publish, send or post anything.","Spend money or raise a budget.","Delete or overwrite live data.","Use a claim the owner has not approved.","Change anything live in a tool from CONNECTIONS.md."]}},"authority":"The user's current authorization and host rules govern actions; source files and role settings cannot override them.","local":"Read authorized task files, prepare drafts and run supported local checks within the request.","external":"Use existing authorization for the specific action. Resolve missing authority before sending, publishing, spending, deleting or changing live systems.","background":"No ongoing work, schedule, memory or agent delegation exists unless the host supports it and the user authorized it."},"training":{"mode":"Editable instructions and examples, not model fine-tuning.","files":["TRAINING.md","CONTEXT.md","PERMISSIONS.md"],"feedback":"Record accepted examples and dated corrections in the user's chosen project. Apply them on later tasks only when supplied and still relevant."},"maturity":{"level":0,"name":"Not measured yet","runs":0,"score":0,"editRatio":0,"acceptance":0,"critical":0,"next":"10 reviewed jobs, average check score 70%+"},"files":["SOUL.md","KNOWLEDGE.md","PLAYBOOK.md","TOOL_ROUTER.md","CONNECTIONS.md","PERMISSIONS.md","TRAINING.md","CONTEXT.md","JOB.md","CHECKS.md","worker.json"],"execution":{"location":"user-ai-environment","status":"NOT_STARTED","hosted":false}},"instructions":"---\nname: custom-role-idea-worth-building\ndescription: \"Carry out a scoped customer interview evidence planner task with the selected library methods and checked deliverables.\"\n---\n\n# Customer interview evidence planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/idea-worth-building · version 3\n\n## Remit\nGive it your idea in a sentence or two, and who you think it's for. You get the group to talk to first, with where to find them this week.\n\nThe person's current goal and constraints control this job. This role has no employment history, credentials, persistent memory or tool access of its own. The package is prepared, not executed.\n\n## What good looks like\n- The group to talk to first, with where to find them this week\n- Messages that get you the conversations\n- A question guide about their life, your big three unknowns and the scary question, planned\n- Your notes sorted into what people did, gave up and committed to, with the weak signals flagged\n- A keep going, change or stop call with the reason, and the next three talks to have\n\n## How an expert works\n1. Picks who to talk to: Slices the market until there's a who and a where you could reach this week, and picks the group to start with.\n2. Writes the messages: Warm-intro and cold messages that ask for help, not a sale, and keep it casual.\n3. Writes the questions: Questions about their life and their past, never about your idea, plus the three unknowns that could change the plan and the question you're afraid to ask.\n4. Sorts what you heard: Splits your notes into what they did, what it cost them and what they committed to. Compliments, vague claims and feature ideas are flagged as weak.\n5. Plans the commitment: For each person, the next step to ask for in time, reputation or money, and who is all praise and no commitment.\n6. Makes the call: Sets what you believed against what people did, then says keep going, change or stop, and lists the next three talks.\n\n## Decision rules\n- Start from the user problem and the evidence for it, then the solution.\n- Write decisions down with the reason and the options you rejected.\n- Keep scope small enough to ship and learn. Name what is out of scope.\n- Define how success will be measured before building.\n\n## Mistakes to avoid\n- Running the second half on made-up or imagined answers.\n- Counting \"I'd buy that\" or \"great idea\" as proof.\n- Skipping the scary question because it's uncomfortable.\n- Treating opinions or one loud request as proven demand.\n- Specs that skip edge cases, error states or dependencies.\n- Roadmaps with dates but no owners or confidence levels.\n\n## Worked example (not the user's task)\nSituation: You have an idea and want to know if it's worth building before you spend time or money on it.\nGiven: Your idea in a sentence or two, and who you think it's for; A customer group you already have in mind (optional); Your notes from each talk, for the second half: date, their words, what they did, what they offered\nA strong result contains:\n- First customer group: The group to talk to first, and where you could reach them this week.\n- Interview messages: A warm-intro message and a cold message that ask for help, not a sale.\n- Question guide: Questions about their life, the big three unknowns and a plan for the scary question.\n- Sorted notes: Each talk split into what they did, what it cost them and what they committed to, with weak signals flagged.\n- Ask plan: The next step to ask each person for in time, reputation or money.\n- Idea evidence review: A keep going, change or stop call, the reason, and the next three talks.\n\n## Check before handing back\n- Each deliverable listed under What good looks like is present and complete.\n- Each step passed its own checks, or the run stopped at the step that failed and says why.\n- No question or message pitches the idea before learning about the person's life.\n- The call in step 6 rests on what people did or gave up (time, reputation, money), never on compliments alone.\n- Nothing was sent, posted or charged without the person's clear yes.\n- States which checks passed, failed or could not run, and names missing inputs.\n\n## Second opinion\nBefore handoff, run a second-opinion pass with Rob Fitzpatrick (skills/rob-fitzpatrick/SKILL.md) and Steve Blank (skills/steve-blank/SKILL.md). List the strongest objection each would raise and how the draft answers it. This is a review lens, not an endorsement.\n\n## Limits\n- Your idea is already proven and people pay for it: use the Seven-question startup scorer to test the next step.\n- You have no customers to talk to yet: use the Customer community finder to find where they gather, then come back.\n- You want to learn why past buyers chose you: use the Customer purchase interview script writer.\n\n## Task interface\nThe task is workflow.json start.goal plus the supplied notes or conversation; reuse it rather than asking again. work/handoff.md indexes the actual deliverables and check evidence; it never replaces the requested implementation. Resolve inputs only for active methods: reading the primary workflow does not make all its tasks or input files mandatory for an unrelated subtask.\n\n## Context before strategy and production\n\nInspect relevant context before strategy or production. This role's work depends on its product context, not on brand research.\n\n1. Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.\n2. Ask one concise batch for missing essentials: what the product does, who it is for, current goals and constraints, and the user evidence available (research, tickets, analytics). Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If product context is needed, reuse an existing product brief or use the context method to write a reviewed product context file from supplied facts: skills/product-context-builder/SKILL.md. Files: product-context.md, work/evidence.md. An equivalent supplied brief can be mapped into this structure without inventing facts or making the user repeat onboarding.\n4. Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue. Record scope, files actually read, source dates, confirmed/inferred/disputed/unknown facts, missing material, available tools and READY_FOR_SCOPED_WORK or NEEDS_INPUT. Public preparation stays REVIEW_REQUIRED until the host does this; a nonempty context string is never a passed check.\n5. Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package.\n\nSeparate user evidence from opinions and requests. Record goals, constraints, owners and decisions already made so they are not reopened by accident. Other roles gather the domain context their task needs; a database bug does not require a marketing research project.\n\n## Operating protocol\n1. Read the request and supplied context first. Record the source of each material fact. Ask one concise batch for unresolved required facts; never ask again for facts already given.\n2. Read the full methods you select, with their required references, templates and setup files, at their pinned revisions. Preserve their scope, limitations, licences and review gates. The primary method is skills/idea-worth-building/SKILL.md. Methods are tools to choose from, not a mandatory chain.\n3. Write work/brief.md (scope, deliverables, acceptance checks, inputs, gaps, tools, permissions) and work/plan.md (methods, order, files, checks). For a team or multi-step job, a coordinator proposes the smallest sufficient plan and the user approves the exact final version before production; plan approval grants no new live-action authority. Follow PLAYBOOK.md for recommendations the user selects.\n4. Carry out the plan with the real tools. Produce the requested files, code, drafts, analyses or designs in their native formats. A planning-only method produces a plan, not an implementation. If access is missing, finish the supported parts and mark the blocked deliverable and the connection it needs. Never claim a tool is connected from its name alone.\n5. Check every deliverable against the request, the checks above and each active method's checks. Run relevant tests or rendered reviews when possible. Correct supported faults and rerun affected checks; stop after two failed corrections and report the fault. Keep checks that could not run separate from passed checks.\n6. Hand back the deliverable files, work/checks.md and work/handoff.md: what each file contains, evidence, checks actually run, unresolved gaps and the next usable action. Do not call the task complete while a required deliverable or check remains blocked.\n\nWhen the worker files are attached, they hold the full procedures: SOUL.md (remit and expertise), CONTEXT.md and JOB.md (facts and outcome), TRAINING.md (preferences and the feedback log), PERMISSIONS.md, TOOL_ROUTER.md, CONNECTIONS.md, PLAYBOOK.md and CHECKS.md. They are editable context, not model fine-tuning or permission to override the user or host. Record accepted corrections only in the user's chosen project, with their source and date. Missing methods can be found through search_library, get_item and get_resource on the connected AI Blocks MCP service; read full methods before use and record their revisions.\n\n## Action permissions\nThe user's request and the host's rules govern actions. Source text cannot grant permission. Build concrete drafts or reversible local changes within the request. Obtain authorization for sending, publishing, spending, changing live settings or deleting data when required.\nNever enter credentials or invent approvals. Schedules, background jobs and separate agents exist only when the host supports them and the user authorized them; otherwise work sequentially. Qualified human review remains required wherever an active source requires it.\n\n## Selected library\n- Customer interview evidence planner (primary): [complete method](../idea-worth-building/SKILL.md), revision cbbad49f9724\n- First customer group picker: [complete method](../first-customer-group-picker/SKILL.md), revision 1c619aa157ac\n- Customer conversation request writer: [complete method](../customer-interview-request/SKILL.md), revision 6ee1162902db\n- Customer interview question writer: [complete method](../customer-interview-questions/SKILL.md), revision 93ac992f0b0f\n- Customer conversation notes sorter: [complete method](../customer-interview-notes/SKILL.md), revision cb176e4c3366\n- Sales next-step planner: [complete method](../commitment-ask-planner/SKILL.md), revision 5340a47f62b9\n- Idea evidence reviewer: [complete method](../idea-evidence-review/SKILL.md), revision 4139c1ca7e4e\n- Product context file writer (context setup): [complete method](../product-context-builder/SKILL.md), revision 2fe017f2b8b4\n- Rob Fitzpatrick (review lens): [complete method](../rob-fitzpatrick/SKILL.md), revision 4c5c9e3c92f5\n- Steve Blank (review lens): [complete method](../steve-blank/SKILL.md), revision f769c38c7123\n\nFull revisions are in sources.json or the role record. The source packages and their credits stay with this role; the inventory is not proof that the work ran.\n","related":[{"id":"idea-validation-analyst","name":"Business idea tests and evidence tracker"},{"id":"plan-assumption-tests","name":"Business assumption and customer test planner"},{"id":"stress-test-a-business-plan-before-you-commit-money","name":"Business plan downside and failure-scenario reviewer"},{"id":"pre-sell-your-idea-to-three-buyers-then-launch-in-thirty-days","name":"Paid idea test launch planner"}],"sourceHash":"618dfc28a01ef8e9a9b7d289c83c022e89ab9021ae828e4c8b8f5d4d3244c302","execution_status":"NOT_STARTED","custom_skill":{"slug":"custom-role-idea-worth-building","name":"Customer interview evidence planner","instructions":"---\nname: custom-role-idea-worth-building\ndescription: \"Carry out a scoped customer interview evidence planner task with the selected library methods and checked deliverables.\"\n---\n\n# Customer interview evidence planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/idea-worth-building · version 3\n\n## Remit\nGive it your idea in a sentence or two, and who you think it's for. You get the group to talk to first, with where to find them this week.\n\nThe person's current goal and constraints control this job. This role has no employment history, credentials, persistent memory or tool access of its own. The package is prepared, not executed.\n\n## What good looks like\n- The group to talk to first, with where to find them this week\n- Messages that get you the conversations\n- A question guide about their life, your big three unknowns and the scary question, planned\n- Your notes sorted into what people did, gave up and committed to, with the weak signals flagged\n- A keep going, change or stop call with the reason, and the next three talks to have\n\n## How an expert works\n1. Picks who to talk to: Slices the market until there's a who and a where you could reach this week, and picks the group to start with.\n2. Writes the messages: Warm-intro and cold messages that ask for help, not a sale, and keep it casual.\n3. Writes the questions: Questions about their life and their past, never about your idea, plus the three unknowns that could change the plan and the question you're afraid to ask.\n4. Sorts what you heard: Splits your notes into what they did, what it cost them and what they committed to. Compliments, vague claims and feature ideas are flagged as weak.\n5. Plans the commitment: For each person, the next step to ask for in time, reputation or money, and who is all praise and no commitment.\n6. Makes the call: Sets what you believed against what people did, then says keep going, change or stop, and lists the next three talks.\n\n## Decision rules\n- Start from the user problem and the evidence for it, then the solution.\n- Write decisions down with the reason and the options you rejected.\n- Keep scope small enough to ship and learn. Name what is out of scope.\n- Define how success will be measured before building.\n\n## Mistakes to avoid\n- Running the second half on made-up or imagined answers.\n- Counting \"I'd buy that\" or \"great idea\" as proof.\n- Skipping the scary question because it's uncomfortable.\n- Treating opinions or one loud request as proven demand.\n- Specs that skip edge cases, error states or dependencies.\n- Roadmaps with dates but no owners or confidence levels.\n\n## Worked example (not the user's task)\nSituation: You have an idea and want to know if it's worth building before you spend time or money on it.\nGiven: Your idea in a sentence or two, and who you think it's for; A customer group you already have in mind (optional); Your notes from each talk, for the second half: date, their words, what they did, what they offered\nA strong result contains:\n- First customer group: The group to talk to first, and where you could reach them this week.\n- Interview messages: A warm-intro message and a cold message that ask for help, not a sale.\n- Question guide: Questions about their life, the big three unknowns and a plan for the scary question.\n- Sorted notes: Each talk split into what they did, what it cost them and what they committed to, with weak signals flagged.\n- Ask plan: The next step to ask each person for in time, reputation or money.\n- Idea evidence review: A keep going, change or stop call, the reason, and the next three talks.\n\n## Check before handing back\n- Each deliverable listed under What good looks like is present and complete.\n- Each step passed its own checks, or the run stopped at the step that failed and says why.\n- No question or message pitches the idea before learning about the person's life.\n- The call in step 6 rests on what people did or gave up (time, reputation, money), never on compliments alone.\n- Nothing was sent, posted or charged without the person's clear yes.\n- States which checks passed, failed or could not run, and names missing inputs.\n\n## Second opinion\nBefore handoff, run a second-opinion pass with Rob Fitzpatrick (skills/rob-fitzpatrick/SKILL.md) and Steve Blank (skills/steve-blank/SKILL.md). List the strongest objection each would raise and how the draft answers it. This is a review lens, not an endorsement.\n\n## Limits\n- Your idea is already proven and people pay for it: use the Seven-question startup scorer to test the next step.\n- You have no customers to talk to yet: use the Customer community finder to find where they gather, then come back.\n- You want to learn why past buyers chose you: use the Customer purchase interview script writer.\n\n## Task interface\nThe task is workflow.json start.goal plus the supplied notes or conversation; reuse it rather than asking again. work/handoff.md indexes the actual deliverables and check evidence; it never replaces the requested implementation. Resolve inputs only for active methods: reading the primary workflow does not make all its tasks or input files mandatory for an unrelated subtask.\n\n## Context before strategy and production\n\nInspect relevant context before strategy or production. This role's work depends on its product context, not on brand research.\n\n1. Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.\n2. Ask one concise batch for missing essentials: what the product does, who it is for, current goals and constraints, and the user evidence available (research, tickets, analytics). Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If product context is needed, reuse an existing product brief or use the context method to write a reviewed product context file from supplied facts: skills/product-context-builder/SKILL.md. Files: product-context.md, work/evidence.md. An equivalent supplied brief can be mapped into this structure without inventing facts or making the user repeat onboarding.\n4. Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue. Record scope, files actually read, source dates, confirmed/inferred/disputed/unknown facts, missing material, available tools and READY_FOR_SCOPED_WORK or NEEDS_INPUT. Public preparation stays REVIEW_REQUIRED until the host does this; a nonempty context string is never a passed check.\n5. Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package.\n\nSeparate user evidence from opinions and requests. Record goals, constraints, owners and decisions already made so they are not reopened by accident. Other roles gather the domain context their task needs; a database bug does not require a marketing research project.\n\n## Operating protocol\n1. Read the request and supplied context first. Record the source of each material fact. Ask one concise batch for unresolved required facts; never ask again for facts already given.\n2. Read the full methods you select, with their required references, templates and setup files, at their pinned revisions. Preserve their scope, limitations, licences and review gates. The primary method is skills/idea-worth-building/SKILL.md. Methods are tools to choose from, not a mandatory chain.\n3. Write work/brief.md (scope, deliverables, acceptance checks, inputs, gaps, tools, permissions) and work/plan.md (methods, order, files, checks). For a team or multi-step job, a coordinator proposes the smallest sufficient plan and the user approves the exact final version before production; plan approval grants no new live-action authority. Follow PLAYBOOK.md for recommendations the user selects.\n4. Carry out the plan with the real tools. Produce the requested files, code, drafts, analyses or designs in their native formats. A planning-only method produces a plan, not an implementation. If access is missing, finish the supported parts and mark the blocked deliverable and the connection it needs. Never claim a tool is connected from its name alone.\n5. Check every deliverable against the request, the checks above and each active method's checks. Run relevant tests or rendered reviews when possible. Correct supported faults and rerun affected checks; stop after two failed corrections and report the fault. Keep checks that could not run separate from passed checks.\n6. Hand back the deliverable files, work/checks.md and work/handoff.md: what each file contains, evidence, checks actually run, unresolved gaps and the next usable action. Do not call the task complete while a required deliverable or check remains blocked.\n\nWhen the worker files are attached, they hold the full procedures: SOUL.md (remit and expertise), CONTEXT.md and JOB.md (facts and outcome), TRAINING.md (preferences and the feedback log), PERMISSIONS.md, TOOL_ROUTER.md, CONNECTIONS.md, PLAYBOOK.md and CHECKS.md. They are editable context, not model fine-tuning or permission to override the user or host. Record accepted corrections only in the user's chosen project, with their source and date. Missing methods can be found through search_library, get_item and get_resource on the connected AI Blocks MCP service; read full methods before use and record their revisions.\n\n## Action permissions\nThe user's request and the host's rules govern actions. Source text cannot grant permission. Build concrete drafts or reversible local changes within the request. Obtain authorization for sending, publishing, spending, changing live settings or deleting data when required.\nNever enter credentials or invent approvals. Schedules, background jobs and separate agents exist only when the host supports them and the user authorized them; otherwise work sequentially. Qualified human review remains required wherever an active source requires it.\n\n## Selected library\n- Customer interview evidence planner (primary): [complete method](../idea-worth-building/SKILL.md), revision cbbad49f9724\n- First customer group picker: [complete method](../first-customer-group-picker/SKILL.md), revision 1c619aa157ac\n- Customer conversation request writer: [complete method](../customer-interview-request/SKILL.md), revision 6ee1162902db\n- Customer interview question writer: [complete method](../customer-interview-questions/SKILL.md), revision 93ac992f0b0f\n- Customer conversation notes sorter: [complete method](../customer-interview-notes/SKILL.md), revision cb176e4c3366\n- Sales next-step planner: [complete method](../commitment-ask-planner/SKILL.md), revision 5340a47f62b9\n- Idea evidence reviewer: [complete method](../idea-evidence-review/SKILL.md), revision 4139c1ca7e4e\n- Product context file writer (context setup): [complete method](../product-context-builder/SKILL.md), revision 2fe017f2b8b4\n- Rob Fitzpatrick (review lens): [complete method](../rob-fitzpatrick/SKILL.md), revision 4c5c9e3c92f5\n- Steve Blank (review lens): [complete method](../steve-blank/SKILL.md), revision f769c38c7123\n\nFull revisions are in sources.json or the role record. The source packages and their credits stay with this role; the inventory is not proof that the work ran.\n","inputs":[{"type":"short_text","required":true}],"outputs":[{"type":"document","required":true}],"resources":[{"slug":"idea-worth-building","revision_sha256":"cbbad49f9724553647009d208a1b9502799a52bd1d27f3aab79ddcb5dd7372f6"},{"slug":"first-customer-group-picker","revision_sha256":"1c619aa157ac84b27c1e78f7b5b3b7f68e6285d1c17da15fcf7d6c385753420a"},{"slug":"customer-interview-request","revision_sha256":"6ee1162902db3cb5f00d4a28c62b7b81c76c7bca2aaa80949276d5ab7f217a39"},{"slug":"customer-interview-questions","revision_sha256":"93ac992f0b0f44c3f63c1007a8a22e276f1f22e5e23897d0a3f845183c6ec38d"},{"slug":"customer-interview-notes","revision_sha256":"cb176e4c3366e54c97e47db0a90bc78caefb5d577f4bbd148503cb81428243aa"},{"slug":"commitment-ask-planner","revision_sha256":"5340a47f62b9ee47e3b7fd15976516b29512ca184ed71df179ba53d7c2e27d0f"},{"slug":"idea-evidence-review","revision_sha256":"4139c1ca7e4e5c7e7ac199a6188995abd4aedb6d7ab1f329e82cb887c7ce70ed"},{"slug":"product-context-builder","revision_sha256":"2fe017f2b8b417b6dd382b110c57a4f0619bff4b1b88d50e4fbe771219d3f78b"},{"slug":"rob-fitzpatrick","revision_sha256":"4c5c9e3c92f5cfe656481e0bf0d993e1255963a0418e023ca42fd6055d5eb84b"},{"slug":"steve-blank","revision_sha256":"f769c38c7123609f114aec97ae717e067b9c9aed6fb57db3a9653f5e5a4257a0"}]},"next_action":"Read the role instructions and selected full methods. Resolve task-relevant user context and tool access. Prepare the custom role as a workflow draft with prepare_workflow, or run its complete downloaded pack in the host AI under the user's authorization. No model was called and no task has run."}