{"schema":"ai-blocks-role/1","id":"set-your-position-and-turn-it-into-a-checked-roadmap","name":"Business positioning roadmap planner","summary":"Give it what you offer and who you serve. You get one position, a list of what you will not do and the activities that must fit.","area":"product","family":{"id":"plan-strategy","name":"Plan your strategy"},"lead":"set-your-position-and-turn-it-into-a-checked-roadmap","featured":false,"contextKind":"product","deliverables":["One position, a list of what you will not do and the activities that must fit","Three to five customer problems, each with a result you can measure and an owner","The plan rebuilt from the end date, with a score out of 100","A list of ways it could fail and one change for each gap"],"inputs":["What you offer and who you serve","Your main rivals (optional)","Your end date and the result you want by then","Your current feature or task list with dates (optional)"],"opening":{"give":["What you offer and who you serve","Your main rivals (optional)","Your end date and the result you want by then"],"get":["One position, a list of what you will not do and the activities that must fit","Three to five customer problems, each with a result you can measure and an owner","The plan rebuilt from the end date, with a score out of 100","A list of ways it could fail and one change for each gap"]},"helpfulInputs":[],"fit":["You list what you offer and keep adding to it.","You have a roadmap of features and cannot say what it should change.","You must show a board, partner or bank that the plan holds."],"limits":["You plan one campaign or one launch: use the Big problem splitter to break it into smaller parts.","You only want to know if your edge holds up against rivals: use the Competitive advantage tester.","You need a single yes or no on one choice: use the Plan objection writer, or ask a trusted adviser."],"tools":["Claude, ChatGPT or Gemini: Choosing a position and testing ideas against it is text work. No files, web access or paid tools needed.","Any good chat AI: Sorting and rewriting a list is text work that any strong chat AI does with this skill.","A spreadsheet: Holds the result numbers you track at each review point.","Any good chat AI: Backward planning and a second-method check are text and arithmetic work any strong chat AI can do.","A spreadsheet: Lets you rerun the small-changes table with your own numbers.","Any good chat AI: Listing and testing failure modes is text reasoning that any strong chat AI handles with this skill.","A spreadsheet: Handy for putting numbers on dependencies, cash and runway."],"method":["Download the handoff pack. It's a zip with HANDOFF.md and four skill files, in the order they run: Strategy trade-off planner, Product outcome roadmap planner, Backwards planning checker and Plan failure reviewer.","Give the folder to Claude (in Claude Code, or as files in a Claude Project, which can need a paid plan) and say \"Follow HANDOFF.md\".","State your end date and the result you want in plain numbers at the start. Step 3 needs both.","Tell it about any commitment you cannot drop, so the not-do list stays honest.","Read the failure list last and decide which changes to make before you share the roadmap."],"capabilities":[{"name":"Choose a position and what you will not do","description":"Separates doing better from doing different, picks one position that fits the facts, writes at least four things you will not do and lists the activities that carry it."},{"name":"Rewrite the activities as a roadmap of results","description":"Marks each item as a feature, a problem or a result, rewrites features as problems for named customers and gives each one a number and an owner, with review points in place of dates."},{"name":"Rebuild the roadmap from the end date","description":"Starts at the end date and works back to this week, checks the answer a second way, tests small input changes, adds backup routes and scores the plan out of 100."},{"name":"List the ways it could fail and fix them","description":"Lists what would guarantee failure, checks the plan against each item, marks risks that could end it and writes one change for each exposed gap."}],"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":["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.","The steps ran in order, and each one used the result of the one before.","Nothing was invented to fill a gap. Every gap is a MISSING: line.","Nothing was sent, published or paid for without a clear yes.","The position is one choice, and the not-do list has at least four real items.","Each roadmap result names a customer and a measure someone can pull from a system or a count.","Every requirement can be tested."],"sources":{"learned":0,"curated":false,"method":6,"source":0,"area":"product"}},"workedExample":{"situation":"You list what you offer and keep adding to it.","task":"Give it what you offer and who you serve. Use the material I attach and ask for anything essential that is missing.","given":["What you offer and who you serve","Your end date and the result you want by then","Your main rivals (optional)","Your current feature or task list with dates (optional)"],"outputs":[{"name":"Step 1 file: position","contains":"Better versus different, the chosen position, the price stance, the not-do list and the activities that must fit."},{"name":"Step 2 file: roadmap of results","contains":"Three to five customer problems, each with a result to measure, an owner and a review point."},{"name":"Step 3 file: backward check","contains":"The end goal, steps worked back from it, two cases, a second method, return paths and a score out of 100."},{"name":"Step 4 file: failure review","contains":"Ways the plan could fail, how well it covers each, risks that could end it, and one change per gap."},{"name":"HAND-BACK SUMMARY","contains":"Each step's file, any step not run and why, and every MISSING line in one list."}]},"example":"Give it what you offer and who you serve. Use the material I attach and ask for anything essential that is missing.","functions":[{"name":"Business positioning roadmap planner","description":"Share your offer, audience and planning limits. Get a position, trade-offs, measurable roadmap and a review of timing and failure risks.","method":"set-your-position-and-turn-it-into-a-checked-roadmap","when":["You list what you offer and keep adding to it.","You have a roadmap of features and cannot say what it should change.","You must show a board, partner or bank that the plan holds."],"inputs":["What you offer and who you serve","Your main rivals (optional)","Your end date and the result you want by then","Your current feature or task list with dates (optional)"],"deliverables":["One position, a list of what you will not do and the activities that must fit","Three to five customer problems, each with a result you can measure and an owner","The plan rebuilt from the end date, with a score out of 100","A list of ways it could fail and one change for each gap"]},{"name":"Strategy trade-off planner","description":"Choose a business position that rivals cannot copy. Get a one-line position, a not-do list and a yes or no on every new idea.","method":"strategy-trade-off-planner","when":["You compete on the same things as everyone else and cannot say why you are different.","Every new idea sounds good and your offer is getting blurry.","A bigger rival copies what you do within months.","You have a list of ideas for the next quarter and need a way to say no to some."],"inputs":["What you offer, who you serve and how you reach them","The main activities that make up your work, from sourcing to delivery","What your main rivals do (optional)","The new ideas you are thinking about adding (optional)","What you would never give up (optional)"],"deliverables":["A split of what makes you better from what makes you different","A position in one sentence, with who it is for","Whether it leads to a premium price or lower cost, and why","A not-do list, each line with what it gives up","A fit check of your activities and a yes or no on each new idea"]},{"name":"Product outcome roadmap planner","description":"Turn a feature roadmap into outcomes. Paste your features and dates. Get three to five customer problems, each with a result you can measure.","method":"outcome-based-roadmap","when":["Your plan is a long list of features ranked by a deadline.","Your team ships on time and nothing seems to improve.","A boss or client has handed you a list of requests and you need to find the goals behind them."],"inputs":["Your list of features, tasks or requests, with any dates","Who asked for each item, if you know (optional)","Findings from earlier checks on the ideas (optional)"],"deliverables":["Each item marked as a feature, a problem or a result","Three to five problems, each for a named customer","One measurable result per problem","Review points in place of dates, with the evidence each needs"]},{"name":"Backwards planning checker","description":"Check your plan from the end date back. Paste your goal and plan to get a second-method check, a backup route and a score out of 100.","method":"work-backwards-plan-checker","when":["You have a launch date, budget or forecast and nobody has checked it a second way.","Your plan starts with \"first we\" and never says what has to be true the week before the end.","You trust a tool's number and want to know if it holds up."],"inputs":["Your goal, and the date or limit you must meet","Your current plan, even rough","The numbers behind the plan, such as costs, hours or volumes (optional)"],"deliverables":["The plan rebuilt from the end point back to the first step","A second-method check with the gap between the two answers explained","A table of small input changes and how far each moves the result","A return path, a backup, and a score out of 100 with how it was worked out"]},{"name":"Plan failure reviewer","description":"Find the ways your plan could fail before you commit. Paste your plan and goal, and get ranked failure risks with a fix for each.","method":"failure-first-plan-check","when":["You have a plan written and want to find holes before you commit money or time.","A team is excited about a plan and nobody is arguing against it.","You are choosing between two paths and want to see what the other one would look like."],"inputs":["The plan, in as much detail as you have","The goal it serves, and the deadline","What the plan depends on (money, people, one big customer or tool) (optional)"],"deliverables":["The goal in one line","A list of failure modes specific to your plan, survival risks first","A change to the plan for each failure","The bet stated, and a set of attacks for the people you pick to argue against it"]},{"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":"Michael Porter","description":"Review a business strategy using Michael Porter’s recorded tools. Compare industry forces, choose a clear position and check which activities support it.","method":"michael-porter","when":["Map the five forces in your field to see why profits there are high or low","Decide whether to win on lower cost or on something customers will pay more for","List what you will stop doing so your position stays clear","Check whether a plan is real strategy or just doing the same things a bit better than rivals","Draw your value chain and find the activities where you are truly different","Test whether your activities support each other, so a rival can't copy one piece and catch up","Check whether a push to grow is blurring what made you different","Find a way to solve a social or local problem that also makes the business stronger"],"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 Michael Porter would: their questions, their method, their push-back","The answer or the work, in Michael Porter's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"]},{"name":"Charlie Munger","description":"Stress-test a plan using Charlie Munger’s recorded approach. Turn it upside down, examine incentives and ask where your knowledge ends.","method":"charlie-munger","when":["Invert a plan: list every way it could fail, then avoid each one","Find the incentive that's really driving a person, team or partner","Run a big decision past several thinking models from different fields","Spot the biases piling up behind a choice that feels too exciting","Build a checklist of mistakes to avoid before you sign a deal or hire someone","Decide whether to wait for a better chance or act now","Plan your own learning across many subjects, not just your job","Challenge an adviser whose advice also pays them","Check whether you know enough about a field before you act on it","Build a checklist for a decision you keep making"],"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 Charlie Munger would: their questions, their method, their push-back","The answer or the work, in Charlie Munger's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"]}],"resources":[{"slug":"set-your-position-and-turn-it-into-a-checked-roadmap","name":"Business positioning roadmap planner","summary":"Share your offer, audience and planning limits. Get a position, trade-offs, measurable roadmap and a review of timing and failure risks.","task":"plan-strategy","kind":"workflow","path":"/workflows/set-your-position-and-turn-it-into-a-checked-roadmap","revision":"c267f700e9f335e263c2c9b4acbe8c46ece68685b2f6fad757494c7c14ede85c","skillPath":"/skills/set-your-position-and-turn-it-into-a-checked-roadmap/SKILL.md","bundled":false,"onboarding":false},{"slug":"strategy-trade-off-planner","name":"Strategy trade-off planner","summary":"Choose a business position that rivals cannot copy. Get a one-line position, a not-do list and a yes or no on every new idea.","task":"plan-strategy","kind":"skill","path":"/skills/strategy-trade-off-planner","revision":"a2545d9c51009c6f73cd2762fd6ba51116a05cc001620e3feef12e3cabc07d13","skillPath":"/skills/strategy-trade-off-planner/SKILL.md","bundled":true,"onboarding":false},{"slug":"outcome-based-roadmap","name":"Product outcome roadmap planner","summary":"Turn a feature roadmap into outcomes. Paste your features and dates. Get three to five customer problems, each with a result you can measure.","task":"plan-strategy","kind":"skill","path":"/skills/outcome-based-roadmap","revision":"bfc332b10f2b175211b9ff400c4c61f4486924a5fe6310041f28034b205653df","skillPath":"/skills/outcome-based-roadmap/SKILL.md","bundled":true,"onboarding":false},{"slug":"work-backwards-plan-checker","name":"Backwards planning checker","summary":"Check your plan from the end date back. Paste your goal and plan to get a second-method check, a backup route and a score out of 100.","task":"plan-strategy","kind":"skill","path":"/skills/work-backwards-plan-checker","revision":"68c392b24d4149525a5f60d25c8781e4627e15d01e8ac895bc36280f3bbc3c6a","skillPath":"/skills/work-backwards-plan-checker/SKILL.md","bundled":true,"onboarding":false},{"slug":"failure-first-plan-check","name":"Plan failure reviewer","summary":"Find the ways your plan could fail before you commit. Paste your plan and goal, and get ranked failure risks with a fix for each.","task":"plan-strategy","kind":"skill","path":"/skills/failure-first-plan-check","revision":"2c3612f7365fc4c94d43958b6c9fff671dbf092ccad3c50deac0784a4cb585ab","skillPath":"/skills/failure-first-plan-check/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":"michael-porter","name":"Michael Porter","summary":"Review a business strategy using Michael Porter’s recorded tools. Compare industry forces, choose a clear position and check which activities support it.","task":"think-with-minds","kind":"mind","path":"/minds/michael-porter","revision":"f3ca34c4fd0c4f0a8d49ebc788a4d84d74a0baa3a5cbd7c8032d6f7795bce52d","skillPath":"/skills/michael-porter/SKILL.md","bundled":false,"onboarding":false,"reviewer":true},{"slug":"charlie-munger","name":"Charlie Munger","summary":"Stress-test a plan using Charlie Munger’s recorded approach. Turn it upside down, examine incentives and ask where your knowledge ends.","task":"think-with-minds","kind":"mind","path":"/minds/charlie-munger","revision":"a87cd5c2b761a64cb5a96db38ba9d7233e8603d2e8d5e8162c47ac88eaa75137","skillPath":"/skills/charlie-munger/SKILL.md","bundled":false,"onboarding":false,"reviewer":true}],"resourceCount":8,"sourceChecks":{"completeMethods":8,"referenceValidation":"PASS"},"catalogueHash":"3c3567ac2dbda7b2ac0cfaa8c93d8da3818f66bdadd51f18d8ff9051d77fc8f3","evaluation":{"status":"NOT_RUN","rubric":[{"id":"c1","criterion":"Delivers: One position, a list of what you will not do and the activities that must fit"},{"id":"c2","criterion":"Delivers: Three to five customer problems, each with a result you can measure and an owner"},{"id":"c3","criterion":"Delivers: The plan rebuilt from the end date, with a score out of 100"},{"id":"c4","criterion":"Delivers: A list of ways it could fail and one change for each gap"},{"id":"c5","criterion":"Each step passed its own checks, or the run stopped at the step that failed and says why."},{"id":"c6","criterion":"The steps ran in order, and each one used the result of the one before."},{"id":"c7","criterion":"Nothing was invented to fill a gap. Every gap is a MISSING: line."},{"id":"c8","criterion":"Nothing was sent, published or paid for without a 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 list what you offer and keep adding to it.","expect":["One position, a list of what you will not do and the activities that must fit","Three to five customer problems, each with a result you can measure and an owner","The plan rebuilt from the end date, with a score out of 100"]},{"id":"g2","kind":"core","situation":"You have a roadmap of features and cannot say what it should change.","expect":["One position, a list of what you will not do and the activities that must fit","Three to five customer problems, each with a result you can measure and an owner","The plan rebuilt from the end date, with a score out of 100"]},{"id":"g-missing","kind":"missing-input","situation":"The request leaves out: What you offer and who you serve","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":"Updated scope, deliverables or inputs. 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":"set-your-position-and-turn-it-into-a-checked-roadmap","name":"Business positioning roadmap 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 what you offer and who you serve. You get one position, a list of what you will not do and the activities that must fit.","capabilities":[{"name":"Choose a position and what you will not do","description":"Separates doing better from doing different, picks one position that fits the facts, writes at least four things you will not do and lists the activities that carry it."},{"name":"Rewrite the activities as a roadmap of results","description":"Marks each item as a feature, a problem or a result, rewrites features as problems for named customers and gives each one a number and an owner, with review points in place of dates."},{"name":"Rebuild the roadmap from the end date","description":"Starts at the end date and works back to this week, checks the answer a second way, tests small input changes, adds backup routes and scores the plan out of 100."},{"name":"List the ways it could fail and fix them","description":"Lists what would guarantee failure, checks the plan against each item, marks risks that could end it and writes one change for each exposed gap."}],"limits":["You plan one campaign or one launch: use the Big problem splitter to break it into smaller parts.","You only want to know if your edge holds up against rivals: use the Competitive advantage tester.","You need a single yes or no on one choice: use the Plan objection writer, or ask a trusted adviser."]},"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":"set-your-position-and-turn-it-into-a-checked-roadmap","name":"Business positioning roadmap planner","kind":"workflow","primary":true,"purpose":"primary","when":["You list what you offer and keep adding to it.","You have a roadmap of features and cannot say what it should change.","You must show a board, partner or bank that the plan holds."],"inputs":["What you offer and who you serve","Your main rivals (optional)","Your end date and the result you want by then","Your current feature or task list with dates (optional)"],"deliverables":["One position, a list of what you will not do and the activities that must fit","Three to five customer problems, each with a result you can measure and an owner","The plan rebuilt from the end date, with a score out of 100","A list of ways it could fail and one change for each gap"],"instruction":"skills/set-your-position-and-turn-it-into-a-checked-roadmap/SKILL.md","revision":"c267f700e9f335e263c2c9b4acbe8c46ece68685b2f6fad757494c7c14ede85c","invocation":"Read the complete procedure, required inputs, real step order and stop gates. Use it only when it covers the job."},{"method":"strategy-trade-off-planner","name":"Strategy trade-off planner","kind":"skill","primary":false,"purpose":"bundled","when":["You compete on the same things as everyone else and cannot say why you are different.","Every new idea sounds good and your offer is getting blurry.","A bigger rival copies what you do within months.","You have a list of ideas for the next quarter and need a way to say no to some."],"inputs":["What you offer, who you serve and how you reach them","The main activities that make up your work, from sourcing to delivery","What your main rivals do (optional)","The new ideas you are thinking about adding (optional)","What you would never give up (optional)"],"deliverables":["A split of what makes you better from what makes you different","A position in one sentence, with who it is for","Whether it leads to a premium price or lower cost, and why","A not-do list, each line with what it gives up","A fit check of your activities and a yes or no on each new idea"],"instruction":"skills/strategy-trade-off-planner/SKILL.md","revision":"a2545d9c51009c6f73cd2762fd6ba51116a05cc001620e3feef12e3cabc07d13","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"outcome-based-roadmap","name":"Product outcome roadmap planner","kind":"skill","primary":false,"purpose":"bundled","when":["Your plan is a long list of features ranked by a deadline.","Your team ships on time and nothing seems to improve.","A boss or client has handed you a list of requests and you need to find the goals behind them."],"inputs":["Your list of features, tasks or requests, with any dates","Who asked for each item, if you know (optional)","Findings from earlier checks on the ideas (optional)"],"deliverables":["Each item marked as a feature, a problem or a result","Three to five problems, each for a named customer","One measurable result per problem","Review points in place of dates, with the evidence each needs"],"instruction":"skills/outcome-based-roadmap/SKILL.md","revision":"bfc332b10f2b175211b9ff400c4c61f4486924a5fe6310041f28034b205653df","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"work-backwards-plan-checker","name":"Backwards planning checker","kind":"skill","primary":false,"purpose":"bundled","when":["You have a launch date, budget or forecast and nobody has checked it a second way.","Your plan starts with \"first we\" and never says what has to be true the week before the end.","You trust a tool's number and want to know if it holds up."],"inputs":["Your goal, and the date or limit you must meet","Your current plan, even rough","The numbers behind the plan, such as costs, hours or volumes (optional)"],"deliverables":["The plan rebuilt from the end point back to the first step","A second-method check with the gap between the two answers explained","A table of small input changes and how far each moves the result","A return path, a backup, and a score out of 100 with how it was worked out"],"instruction":"skills/work-backwards-plan-checker/SKILL.md","revision":"68c392b24d4149525a5f60d25c8781e4627e15d01e8ac895bc36280f3bbc3c6a","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"failure-first-plan-check","name":"Plan failure reviewer","kind":"skill","primary":false,"purpose":"bundled","when":["You have a plan written and want to find holes before you commit money or time.","A team is excited about a plan and nobody is arguing against it.","You are choosing between two paths and want to see what the other one would look like."],"inputs":["The plan, in as much detail as you have","The goal it serves, and the deadline","What the plan depends on (money, people, one big customer or tool) (optional)"],"deliverables":["The goal in one line","A list of failure modes specific to your plan, survival risks first","A change to the plan for each failure","The bet stated, and a set of attacks for the people you pick to argue against it"],"instruction":"skills/failure-first-plan-check/SKILL.md","revision":"2c3612f7365fc4c94d43958b6c9fff671dbf092ccad3c50deac0784a4cb585ab","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":"michael-porter","name":"Michael Porter","kind":"mind","primary":false,"purpose":"review","when":["Map the five forces in your field to see why profits there are high or low","Decide whether to win on lower cost or on something customers will pay more for","List what you will stop doing so your position stays clear","Check whether a plan is real strategy or just doing the same things a bit better than rivals","Draw your value chain and find the activities where you are truly different","Test whether your activities support each other, so a rival can't copy one piece and catch up","Check whether a push to grow is blurring what made you different","Find a way to solve a social or local problem that also makes the business stronger"],"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 Michael Porter would: their questions, their method, their push-back","The answer or the work, in Michael Porter's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"],"instruction":"skills/michael-porter/SKILL.md","revision":"f3ca34c4fd0c4f0a8d49ebc788a4d84d74a0baa3a5cbd7c8032d6f7795bce52d","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":"charlie-munger","name":"Charlie Munger","kind":"mind","primary":false,"purpose":"review","when":["Invert a plan: list every way it could fail, then avoid each one","Find the incentive that's really driving a person, team or partner","Run a big decision past several thinking models from different fields","Spot the biases piling up behind a choice that feels too exciting","Build a checklist of mistakes to avoid before you sign a deal or hire someone","Decide whether to wait for a better chance or act now","Plan your own learning across many subjects, not just your job","Challenge an adviser whose advice also pays them","Check whether you know enough about a field before you act on it","Build a checklist for a decision you keep making"],"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 Charlie Munger would: their questions, their method, their push-back","The answer or the work, in Charlie Munger's voice, using their ideas by name","Anything that goes beyond their public record, marked","One suggested next step"],"instruction":"skills/charlie-munger/SKILL.md","revision":"a87cd5c2b761a64cb5a96db38ba9d7233e8603d2e8d5e8162c47ac88eaa75137","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, ChatGPT or Gemini: Choosing a position and testing ideas against it is text work. No files, web access or paid tools needed.","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 rewriting a list is text work that any strong chat AI does 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 spreadsheet: Holds the result numbers you track at each review point.","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: Backward planning and a second-method check are text and arithmetic work any strong chat AI can do.","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 spreadsheet: Lets you rerun the small-changes table with your own numbers.","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: Listing and testing failure modes is text reasoning that any strong chat AI handles 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 spreadsheet: Handy for putting numbers on dependencies, cash and runway.","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-set-your-position-and-turn-it-into-a-checked-roadmap\ndescription: \"Carry out a scoped business positioning roadmap planner task with the selected library methods and checked deliverables.\"\n---\n\n# Business positioning roadmap planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/set-your-position-and-turn-it-into-a-checked-roadmap · version 3\n\n## Remit\nGive it what you offer and who you serve. You get one position, a list of what you will not do and the activities that must fit.\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- One position, a list of what you will not do and the activities that must fit\n- Three to five customer problems, each with a result you can measure and an owner\n- The plan rebuilt from the end date, with a score out of 100\n- A list of ways it could fail and one change for each gap\n\n## How an expert works\n1. Choose a position and what you will not do: Separates doing better from doing different, picks one position that fits the facts, writes at least four things you will not do and lists the activities that carry it.\n2. Rewrite the activities as a roadmap of results: Marks each item as a feature, a problem or a result, rewrites features as problems for named customers and gives each one a number and an owner, with review points in place of dates.\n3. Rebuild the roadmap from the end date: Starts at the end date and works back to this week, checks the answer a second way, tests small input changes, adds backup routes and scores the plan out of 100.\n4. List the ways it could fail and fix them: Lists what would guarantee failure, checks the plan against each item, marks risks that could end it and writes one change for each exposed gap.\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- 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 list what you offer and keep adding to it.\nGiven: What you offer and who you serve; Your end date and the result you want by then; Your main rivals (optional); Your current feature or task list with dates (optional)\nA strong result contains:\n- Step 1 file: position: Better versus different, the chosen position, the price stance, the not-do list and the activities that must fit.\n- Step 2 file: roadmap of results: Three to five customer problems, each with a result to measure, an owner and a review point.\n- Step 3 file: backward check: The end goal, steps worked back from it, two cases, a second method, return paths and a score out of 100.\n- Step 4 file: failure review: Ways the plan could fail, how well it covers each, risks that could end it, and one change per gap.\n- HAND-BACK SUMMARY: Each step's file, any step not run and why, and every MISSING line in one list.\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- The steps ran in order, and each one used the result of the one before.\n- Nothing was invented to fill a gap. Every gap is a MISSING: line.\n- Nothing was sent, published or paid for without a 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 Michael Porter (skills/michael-porter/SKILL.md) and Charlie Munger (skills/charlie-munger/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- You plan one campaign or one launch: use the Big problem splitter to break it into smaller parts.\n- You only want to know if your edge holds up against rivals: use the Competitive advantage tester.\n- You need a single yes or no on one choice: use the Plan objection writer, or ask a trusted adviser.\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/set-your-position-and-turn-it-into-a-checked-roadmap/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- Business positioning roadmap planner (primary): [complete method](../set-your-position-and-turn-it-into-a-checked-roadmap/SKILL.md), revision c267f700e9f3\n- Strategy trade-off planner: [complete method](../strategy-trade-off-planner/SKILL.md), revision a2545d9c5100\n- Product outcome roadmap planner: [complete method](../outcome-based-roadmap/SKILL.md), revision bfc332b10f2b\n- Backwards planning checker: [complete method](../work-backwards-plan-checker/SKILL.md), revision 68c392b24d41\n- Plan failure reviewer: [complete method](../failure-first-plan-check/SKILL.md), revision 2c3612f7365f\n- Product context file writer (context setup): [complete method](../product-context-builder/SKILL.md), revision 2fe017f2b8b4\n- Michael Porter (review lens): [complete method](../michael-porter/SKILL.md), revision f3ca34c4fd0c\n- Charlie Munger (review lens): [complete method](../charlie-munger/SKILL.md), revision a87cd5c2b761\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":"quarterly-strategy-reviewer","name":"Quarterly business plan reviewer"},{"id":"new-business-growth-needs","name":"Business growth target and risk planner"},{"id":"four-filter-decision","name":"Deal and hiring decision reviewer"},{"id":"brand-sales-budget-split","name":"Brand and sales budget planner"}],"sourceHash":"89fafecf2fc669676b4f9a855423ac901b8e9b510b0b1cbc0e0fdf1643ac3ec1","execution_status":"NOT_STARTED","custom_skill":{"slug":"custom-role-set-your-position-and-turn-it-into-a-checked-roadmap","name":"Business positioning roadmap planner","instructions":"---\nname: custom-role-set-your-position-and-turn-it-into-a-checked-roadmap\ndescription: \"Carry out a scoped business positioning roadmap planner task with the selected library methods and checked deliverables.\"\n---\n\n# Business positioning roadmap planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/set-your-position-and-turn-it-into-a-checked-roadmap · version 3\n\n## Remit\nGive it what you offer and who you serve. You get one position, a list of what you will not do and the activities that must fit.\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- One position, a list of what you will not do and the activities that must fit\n- Three to five customer problems, each with a result you can measure and an owner\n- The plan rebuilt from the end date, with a score out of 100\n- A list of ways it could fail and one change for each gap\n\n## How an expert works\n1. Choose a position and what you will not do: Separates doing better from doing different, picks one position that fits the facts, writes at least four things you will not do and lists the activities that carry it.\n2. Rewrite the activities as a roadmap of results: Marks each item as a feature, a problem or a result, rewrites features as problems for named customers and gives each one a number and an owner, with review points in place of dates.\n3. Rebuild the roadmap from the end date: Starts at the end date and works back to this week, checks the answer a second way, tests small input changes, adds backup routes and scores the plan out of 100.\n4. List the ways it could fail and fix them: Lists what would guarantee failure, checks the plan against each item, marks risks that could end it and writes one change for each exposed gap.\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- 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 list what you offer and keep adding to it.\nGiven: What you offer and who you serve; Your end date and the result you want by then; Your main rivals (optional); Your current feature or task list with dates (optional)\nA strong result contains:\n- Step 1 file: position: Better versus different, the chosen position, the price stance, the not-do list and the activities that must fit.\n- Step 2 file: roadmap of results: Three to five customer problems, each with a result to measure, an owner and a review point.\n- Step 3 file: backward check: The end goal, steps worked back from it, two cases, a second method, return paths and a score out of 100.\n- Step 4 file: failure review: Ways the plan could fail, how well it covers each, risks that could end it, and one change per gap.\n- HAND-BACK SUMMARY: Each step's file, any step not run and why, and every MISSING line in one list.\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- The steps ran in order, and each one used the result of the one before.\n- Nothing was invented to fill a gap. Every gap is a MISSING: line.\n- Nothing was sent, published or paid for without a 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 Michael Porter (skills/michael-porter/SKILL.md) and Charlie Munger (skills/charlie-munger/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- You plan one campaign or one launch: use the Big problem splitter to break it into smaller parts.\n- You only want to know if your edge holds up against rivals: use the Competitive advantage tester.\n- You need a single yes or no on one choice: use the Plan objection writer, or ask a trusted adviser.\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/set-your-position-and-turn-it-into-a-checked-roadmap/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- Business positioning roadmap planner (primary): [complete method](../set-your-position-and-turn-it-into-a-checked-roadmap/SKILL.md), revision c267f700e9f3\n- Strategy trade-off planner: [complete method](../strategy-trade-off-planner/SKILL.md), revision a2545d9c5100\n- Product outcome roadmap planner: [complete method](../outcome-based-roadmap/SKILL.md), revision bfc332b10f2b\n- Backwards planning checker: [complete method](../work-backwards-plan-checker/SKILL.md), revision 68c392b24d41\n- Plan failure reviewer: [complete method](../failure-first-plan-check/SKILL.md), revision 2c3612f7365f\n- Product context file writer (context setup): [complete method](../product-context-builder/SKILL.md), revision 2fe017f2b8b4\n- Michael Porter (review lens): [complete method](../michael-porter/SKILL.md), revision f3ca34c4fd0c\n- Charlie Munger (review lens): [complete method](../charlie-munger/SKILL.md), revision a87cd5c2b761\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":"set-your-position-and-turn-it-into-a-checked-roadmap","revision_sha256":"c267f700e9f335e263c2c9b4acbe8c46ece68685b2f6fad757494c7c14ede85c"},{"slug":"strategy-trade-off-planner","revision_sha256":"a2545d9c51009c6f73cd2762fd6ba51116a05cc001620e3feef12e3cabc07d13"},{"slug":"outcome-based-roadmap","revision_sha256":"bfc332b10f2b175211b9ff400c4c61f4486924a5fe6310041f28034b205653df"},{"slug":"work-backwards-plan-checker","revision_sha256":"68c392b24d4149525a5f60d25c8781e4627e15d01e8ac895bc36280f3bbc3c6a"},{"slug":"failure-first-plan-check","revision_sha256":"2c3612f7365fc4c94d43958b6c9fff671dbf092ccad3c50deac0784a4cb585ab"},{"slug":"product-context-builder","revision_sha256":"2fe017f2b8b417b6dd382b110c57a4f0619bff4b1b88d50e4fbe771219d3f78b"},{"slug":"michael-porter","revision_sha256":"f3ca34c4fd0c4f0a8d49ebc788a4d84d74a0baa3a5cbd7c8032d6f7795bce52d"},{"slug":"charlie-munger","revision_sha256":"a87cd5c2b761a64cb5a96db38ba9d7233e8603d2e8d5e8162c47ac88eaa75137"}]},"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."}