{"schema":"ai-blocks-role/1","id":"standardize-repair-work-order-intake","name":"Repair work-order intake and follow-up planner","summary":"Share work-order samples, required fields and approval rules. Get an intake procedure, missing-field checks and a tracker for open work.","area":"operations","family":{"id":"document-work","name":"Write down how work gets done"},"lead":"standardize-repair-work-order-intake","featured":false,"contextKind":"personal","deliverables":["An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician","A missing-field check for each sample work order","A register of open jobs with every unresolved authorization or customer decision","Questions for anyone who must confirm a rule","A list of facts still MISSING"],"inputs":["A few real work orders, with customer names and contact details removed","Your required intake fields, if you have a list (optional)","Your rules on what the customer must agree to before diagnosis, quote and repair","What front desk staff may and may not judge about a fault, and who decides","Your current intake steps, written or described","Open jobs waiting on something, for the register (optional)"],"opening":{"give":["A few real work orders, with customer names and contact details removed","Your required intake fields, if you have a list (optional)","What front desk staff may and may not judge about a fault, and who decides"],"get":["A missing-field check for each sample work order","Questions for anyone who must confirm a rule","A list of facts still MISSING"]},"helpfulInputs":["Your blank work order form.","Your terms of service or repair authorization wording."],"fit":["Work orders come in with missing serial numbers, contact details or authorization.","Different staff take in the same kind of job in different ways.","A customer disputes what they agreed to, and your records are thin.","You are adding a second counter or new staff and need the intake steps written down."],"limits":["You need a fault diagnosed or a repair judged safe: that stays with your qualified technicians.","You want to decide whether a customer agreed to a repair: only their own authorization counts. This lists where it is missing.","You want a procedure for some other process: use the Process and SOP writer.","You already have an intake procedure and want it checked: use the SOP and runbook checker."],"tools":["A chat AI that reads files and images: It can read work order photos or exports. In plain chat, paste the text of each sample."],"method":["Download the workflow pack and add it to Claude, ChatGPT or Gemini, in a chat that accepts files.","Attach your sample work orders with personal details removed, and paste your required fields, authorization rules and current steps.","Tell your AI to follow the pack and save each step's file.","After step 1, check the procedure against how your shop works. Fix any step that sounds like a diagnosis or a repair decision.","After step 2, work through the unresolved list. Do not start a repair that still shows missing authorization."],"capabilities":[{"name":"Process and SOP writer","description":"Writes the intake procedure from your existing process, covering item identification, authorization evidence, quote acceptance and escalation. Then checks each sample work order against your required fields. Hands step 2 the field list and the gaps found. Check before moving on, no step diagnoses a fault or assumes consent."},{"name":"Executive action register keeper","description":"Builds the register of open work orders from your records and explicit commitments. Missing authorization and customer decisions stay unresolved, each with an owner and a source. Check before you act, every open item names what is missing and who can supply it."}],"expertise":{"principles":["Turn every request into owned actions: who, what and by when.","Work from the real calendar, notes and lists. Never invent meetings, people or dates.","Put the most important decision or deadline first, then the details.","Prepare drafts and proposals. Sending, booking and changing records waits for approval."],"pitfalls":["Losing commitments buried in long notes.","Mixing confirmed facts with guesses about other people's plans.","Adding process when a short checklist would do."],"quality":["No step or note diagnoses a fault, promises a repair result or infers consent.","Every field, rule, date and owner traces to a source, or is marked as a proposal or MISSING:.","No customer name, contact detail or address appears.","End with CHECKS MISSED: and each check that failed or could not run, or none. Never call this tested.","Every action has an owner and a date, or is marked as missing one.","Each item points to the note or message it came from.","The output fits where it will be used, such as one screen or one page."],"sources":{"learned":0,"curated":false,"method":4,"source":0,"area":"operations"}},"workedExample":{"situation":"Work orders come in with missing serial numbers, contact details or authorization.","task":"Share work-order samples, required fields and approval rules. Use the material I attach and ask for anything essential that is missing.","given":["A few sample work orders with personal details removed","Your required fields, authorization rules and current intake steps","Open jobs waiting on a customer decision (optional)"],"outputs":[{"name":"outputs/step-01-process-and-sop-writer.md","contains":"The intake procedure, plus a field-by-field check of each sample work order."},{"name":"outputs/step-02-executive-action-register.md","contains":"The register of open jobs, with each unresolved authorization or customer decision, owner and source."},{"name":"Questions","contains":"Each rule that needs confirming, and who can answer it."},{"name":"HAND-BACK SUMMARY","contains":"Files saved, sources used, MISSING lines, checks missed and one suggested next step."}]},"example":"Share work-order samples, required fields and approval rules. Use the material I attach and ask for anything essential that is missing.","functions":[{"name":"Repair work-order intake and follow-up planner","description":"Share work-order samples, required fields and approval rules. Get an intake procedure, missing-field checks and a tracker for open work.","method":"standardize-repair-work-order-intake","when":["Work orders come in with missing serial numbers, contact details or authorization.","Different staff take in the same kind of job in different ways.","A customer disputes what they agreed to, and your records are thin.","You are adding a second counter or new staff and need the intake steps written down."],"inputs":["A few real work orders, with customer names and contact details removed","Your required intake fields, if you have a list (optional)","Your rules on what the customer must agree to before diagnosis, quote and repair","What front desk staff may and may not judge about a fault, and who decides","Your current intake steps, written or described","Open jobs waiting on something, for the register (optional)"],"deliverables":["An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician","A missing-field check for each sample work order","A register of open jobs with every unresolved authorization or customer decision","Questions for anyone who must confirm a rule","A list of facts still MISSING"]},{"name":"Process and SOP writer","description":"Turn how your team works into a clear SOP. Give it a process name or old notes. You get a RACI table, a flow, steps and exceptions.","method":"process-and-sop-writer","when":["A process lives in one person's head and you need it written down before they leave.","You are handing work to a new hire and need clear steps and owners.","An audit asks for a documented procedure.","People argue about who owns a step and you need a RACI."],"inputs":["Process name or a short description","Existing notes or documents (optional)","Names of the people or teams involved (optional)","Known exceptions or problem cases (optional)"],"deliverables":["A step-by-step written procedure","A RACI table","A process flow","An exceptions and edge cases table","Metrics to track the process"]},{"name":"Action item tracker","description":"Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.","method":"executive-action-register","when":["You want the result described above from the files and facts you already have.","You need a repeatable process and a clear next action."],"inputs":["The source files, notes or product facts for this job","Your goal, deadline and limits","Relevant earlier work, if available"],"deliverables":["action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id","clarifications.md","proposed-task-changes.md"]},{"name":"Recurring task procedure writer","description":"Turn a task you repeat into a step-by-step guide anyone can follow, with fixes, rollback and who to call. Built for on-call staff.","method":"repeat-task-step-guide-writer","when":["Only one person knows how to do a weekly task and they are going on leave.","A new hire must run a monthly process alone.","On-call staff keep asking the same questions during incidents.","An old process document is out of date."],"inputs":["Name of the task","How you do it today, notes or commands","Owner and how often it runs (optional)","Known failure cases (optional)"],"deliverables":["Step-by-step guide with expected results","Fix steps for each failure","Rollback and check steps","Escalation contacts section"]},{"name":"me.md builder","description":"Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.","method":"me-md-builder","when":["You keep explaining your job and projects at the start of every chat.","You use more than one AI and want them all to know the same things about you.","Your AI gives you answers that don't sound like you or don't fit your work."],"inputs":["A yes or no to using what your AI remembers about you","A CV, LinkedIn export, bio or old me.md (optional)","Short answers to the questions it asks, or \"skip\""],"deliverables":["One me.md file with up to ten dated sections","A list of facts taken from memory, for you to check","A short note of what it removed for privacy","The two next steps, to save it and set it up"]}],"resources":[{"slug":"standardize-repair-work-order-intake","name":"Repair work-order intake and follow-up planner","summary":"Share work-order samples, required fields and approval rules. Get an intake procedure, missing-field checks and a tracker for open work.","task":"document-work","kind":"workflow","path":"/workflows/standardize-repair-work-order-intake","revision":"e950fbc3d95298b47e0285f756f45869af7b033bced5a501b3dd1dd4e8296177","skillPath":"/skills/standardize-repair-work-order-intake/SKILL.md","bundled":false,"onboarding":false},{"slug":"process-and-sop-writer","name":"Process and SOP writer","summary":"Turn how your team works into a clear SOP. Give it a process name or old notes. You get a RACI table, a flow, steps and exceptions.","task":"document-work","kind":"skill","path":"/skills/process-and-sop-writer","revision":"4e3050c1750ff7d6cbd6f512bf121490cac162ab0f29ff1c50cfa90246d2b24c","skillPath":"/skills/process-and-sop-writer/SKILL.md","bundled":true,"onboarding":false,"by":"Anthropic"},{"slug":"executive-action-register","name":"Action item tracker","summary":"Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.","task":"organise-work","kind":"skill","path":"/skills/executive-action-register","revision":"7a2659d6aecd083473b08c0e8fe5026bca3922bdeb2585f14684c648b41d81c6","skillPath":"/skills/executive-action-register/SKILL.md","bundled":true,"onboarding":false},{"slug":"repeat-task-step-guide-writer","name":"Recurring task procedure writer","summary":"Turn a task you repeat into a step-by-step guide anyone can follow, with fixes, rollback and who to call. Built for on-call staff.","task":"document-work","kind":"skill","path":"/skills/repeat-task-step-guide-writer","revision":"e06dda10c5ae31a0adc5276e7bea8734a6d4212b617ceb1fee9e6abbb2adebb0","skillPath":"/skills/repeat-task-step-guide-writer/SKILL.md","bundled":false,"onboarding":false,"support":true,"by":"Anthropic"},{"slug":"me-md-builder","name":"me.md builder","summary":"Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.","task":"set-up-ai","kind":"skill","path":"/skills/me-md-builder","revision":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53","skillPath":"/skills/me-md-builder/SKILL.md","bundled":false,"onboarding":true}],"resourceCount":5,"sourceChecks":{"completeMethods":5,"referenceValidation":"PASS"},"catalogueHash":"3c3567ac2dbda7b2ac0cfaa8c93d8da3818f66bdadd51f18d8ff9051d77fc8f3","evaluation":{"status":"NOT_RUN","rubric":[{"id":"c1","criterion":"Delivers: An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician"},{"id":"c2","criterion":"Delivers: A missing-field check for each sample work order"},{"id":"c3","criterion":"Delivers: A register of open jobs with every unresolved authorization or customer decision"},{"id":"c4","criterion":"Delivers: Questions for anyone who must confirm a rule"},{"id":"c5","criterion":"No step or note diagnoses a fault, promises a repair result or infers consent."},{"id":"c6","criterion":"Every field, rule, date and owner traces to a source, or is marked as a proposal or MISSING:."},{"id":"c7","criterion":"No customer name, contact detail or address appears."},{"id":"c8","criterion":"End with CHECKS MISSED: and each check that failed or could not run, or none. Never call this tested."},{"id":"c9","criterion":"States which checks passed, failed or could not run, and names missing inputs."}],"goldenTasks":[{"id":"g1","kind":"core","situation":"Work orders come in with missing serial numbers, contact details or authorization.","expect":["An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician","A missing-field check for each sample work order","A register of open jobs with every unresolved authorization or customer decision"]},{"id":"g2","kind":"core","situation":"Different staff take in the same kind of job in different ways.","expect":["An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician","A missing-field check for each sample work order","A register of open jobs with every unresolved authorization or customer decision"]},{"id":"g-missing","kind":"missing-input","situation":"The request leaves out: A few real work orders, with customer names and contact details removed","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":2,"since":"2026-11-03","changes":[{"version":2,"date":"2026-11-03","what":"Source methods updated to new revisions."},{"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":"standardize-repair-work-order-intake","name":"Repair work-order intake and follow-up 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":"Share work-order samples, required fields and approval rules. Get an intake procedure, missing-field checks and a tracker for open work.","capabilities":[{"name":"Process and SOP writer","description":"Writes the intake procedure from your existing process, covering item identification, authorization evidence, quote acceptance and escalation. Then checks each sample work order against your required fields. Hands step 2 the field list and the gaps found. Check before moving on, no step diagnoses a fault or assumes consent."},{"name":"Executive action register keeper","description":"Builds the register of open work orders from your records and explicit commitments. Missing authorization and customer decisions stay unresolved, each with an owner and a source. Check before you act, every open item names what is missing and who can supply it."}],"limits":["You need a fault diagnosed or a repair judged safe: that stays with your qualified technicians.","You want to decide whether a customer agreed to a repair: only their own authorization counts. This lists where it is missing.","You want a procedure for some other process: use the Process and SOP writer.","You already have an intake procedure and want it checked: use the SOP and runbook checker."]},"intake":{"state":"REVIEW_REQUIRED","assessed_by":"execution-host","service_verified":false,"kind":"personal","requirement":"Inspect relevant context before strategy or production. This role's work depends on its me.md, not on brand research.","method":"me-md-builder","files":["me.md","work/context-check.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: your role and goals, working preferences, current constraints and the files or records relevant to this job. 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":"standardize-repair-work-order-intake","name":"Repair work-order intake and follow-up planner","kind":"workflow","primary":true,"purpose":"primary","when":["Work orders come in with missing serial numbers, contact details or authorization.","Different staff take in the same kind of job in different ways.","A customer disputes what they agreed to, and your records are thin.","You are adding a second counter or new staff and need the intake steps written down."],"inputs":["A few real work orders, with customer names and contact details removed","Your required intake fields, if you have a list (optional)","Your rules on what the customer must agree to before diagnosis, quote and repair","What front desk staff may and may not judge about a fault, and who decides","Your current intake steps, written or described","Open jobs waiting on something, for the register (optional)"],"deliverables":["An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician","A missing-field check for each sample work order","A register of open jobs with every unresolved authorization or customer decision","Questions for anyone who must confirm a rule","A list of facts still MISSING"],"instruction":"skills/standardize-repair-work-order-intake/SKILL.md","revision":"e950fbc3d95298b47e0285f756f45869af7b033bced5a501b3dd1dd4e8296177","invocation":"Read the complete procedure, required inputs, real step order and stop gates. Use it only when it covers the job."},{"method":"process-and-sop-writer","name":"Process and SOP writer","kind":"skill","primary":false,"purpose":"bundled","when":["A process lives in one person's head and you need it written down before they leave.","You are handing work to a new hire and need clear steps and owners.","An audit asks for a documented procedure.","People argue about who owns a step and you need a RACI."],"inputs":["Process name or a short description","Existing notes or documents (optional)","Names of the people or teams involved (optional)","Known exceptions or problem cases (optional)"],"deliverables":["A step-by-step written procedure","A RACI table","A process flow","An exceptions and edge cases table","Metrics to track the process"],"instruction":"skills/process-and-sop-writer/SKILL.md","revision":"4e3050c1750ff7d6cbd6f512bf121490cac162ab0f29ff1c50cfa90246d2b24c","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"executive-action-register","name":"Action item tracker","kind":"skill","primary":false,"purpose":"bundled","when":["You want the result described above from the files and facts you already have.","You need a repeatable process and a clear next action."],"inputs":["The source files, notes or product facts for this job","Your goal, deadline and limits","Relevant earlier work, if available"],"deliverables":["action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id","clarifications.md","proposed-task-changes.md"],"instruction":"skills/executive-action-register/SKILL.md","revision":"7a2659d6aecd083473b08c0e8fe5026bca3922bdeb2585f14684c648b41d81c6","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"repeat-task-step-guide-writer","name":"Recurring task procedure writer","kind":"skill","primary":false,"purpose":"support","when":["Only one person knows how to do a weekly task and they are going on leave.","A new hire must run a monthly process alone.","On-call staff keep asking the same questions during incidents.","An old process document is out of date."],"inputs":["Name of the task","How you do it today, notes or commands","Owner and how often it runs (optional)","Known failure cases (optional)"],"deliverables":["Step-by-step guide with expected results","Fix steps for each failure","Rollback and check steps","Escalation contacts section"],"instruction":"skills/repeat-task-step-guide-writer/SKILL.md","revision":"e06dda10c5ae31a0adc5276e7bea8734a6d4212b617ceb1fee9e6abbb2adebb0","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"me-md-builder","name":"me.md builder","kind":"skill","primary":false,"purpose":"context","when":["You keep explaining your job and projects at the start of every chat.","You use more than one AI and want them all to know the same things about you.","Your AI gives you answers that don't sound like you or don't fit your work."],"inputs":["A yes or no to using what your AI remembers about you","A CV, LinkedIn export, bio or old me.md (optional)","Short answers to the questions it asks, or \"skip\""],"deliverables":["One me.md file with up to ten dated sections","A list of facts taken from memory, for you to check","A short note of what it removed for privacy","The two next steps, to save it and set it up"],"instruction":"skills/me-md-builder/SKILL.md","revision":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."}],"connections":[{"name":"A chat AI that reads files and images: It can read work order photos or exports. In plain chat, paste the text of each sample.","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-standardize-repair-work-order-intake\ndescription: \"Carry out a scoped repair work-order intake and follow-up planner task with the selected library methods and checked deliverables.\"\n---\n\n# Repair work-order intake and follow-up planner\n\nAI Blocks role setup: https://useaiblocks.com/roles/standardize-repair-work-order-intake · version 2\n\n## Remit\nShare work-order samples, required fields and approval rules. Get an intake procedure, missing-field checks and a tracker for open work.\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- An intake procedure covering item identification, reported problem, authorization, quote acceptance and handoff to a technician\n- A missing-field check for each sample work order\n- A register of open jobs with every unresolved authorization or customer decision\n- Questions for anyone who must confirm a rule\n- A list of facts still MISSING\n\n## How an expert works\n1. Process and SOP writer: Writes the intake procedure from your existing process, covering item identification, authorization evidence, quote acceptance and escalation. Then checks each sample work order against your required fields. Hands step 2 the field list and the gaps found. Check before moving on, no step diagnoses a fault or assumes consent.\n2. Executive action register keeper: Builds the register of open work orders from your records and explicit commitments. Missing authorization and customer decisions stay unresolved, each with an owner and a source. Check before you act, every open item names what is missing and who can supply it.\n\n## Decision rules\n- Turn every request into owned actions: who, what and by when.\n- Work from the real calendar, notes and lists. Never invent meetings, people or dates.\n- Put the most important decision or deadline first, then the details.\n- Prepare drafts and proposals. Sending, booking and changing records waits for approval.\n\n## Mistakes to avoid\n- Losing commitments buried in long notes.\n- Mixing confirmed facts with guesses about other people's plans.\n- Adding process when a short checklist would do.\n\n## Worked example (not the user's task)\nSituation: Work orders come in with missing serial numbers, contact details or authorization.\nGiven: A few sample work orders with personal details removed; Your required fields, authorization rules and current intake steps; Open jobs waiting on a customer decision (optional)\nA strong result contains:\n- outputs/step-01-process-and-sop-writer.md: The intake procedure, plus a field-by-field check of each sample work order.\n- outputs/step-02-executive-action-register.md: The register of open jobs, with each unresolved authorization or customer decision, owner and source.\n- Questions: Each rule that needs confirming, and who can answer it.\n- HAND-BACK SUMMARY: Files saved, sources used, MISSING lines, checks missed and one suggested next step.\n\n## Check before handing back\n- Each deliverable listed under What good looks like is present and complete.\n- No step or note diagnoses a fault, promises a repair result or infers consent.\n- Every field, rule, date and owner traces to a source, or is marked as a proposal or MISSING:.\n- No customer name, contact detail or address appears.\n- End with CHECKS MISSED: and each check that failed or could not run, or none. Never call this tested.\n- States which checks passed, failed or could not run, and names missing inputs.\n\n## Limits\n- You need a fault diagnosed or a repair judged safe: that stays with your qualified technicians.\n- You want to decide whether a customer agreed to a repair: only their own authorization counts. This lists where it is missing.\n- You want a procedure for some other process: use the Process and SOP writer.\n- You already have an intake procedure and want it checked: use the SOP and runbook checker.\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 me.md, 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: your role and goals, working preferences, current constraints and the files or records relevant to this job. Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If me.md is needed, reuse the relevant slice of an existing me.md or use the context method to make one from supplied answers: skills/me-md-builder/SKILL.md. Files: me.md, work/context-check.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\nUse only the parts of me.md that matter for this job. Keep personal and business records private and minimal. Check dates, names and figures against the supplied records. 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/standardize-repair-work-order-intake/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- Repair work-order intake and follow-up planner (primary): [complete method](../standardize-repair-work-order-intake/SKILL.md), revision e950fbc3d952\n- Process and SOP writer: [complete method](../process-and-sop-writer/SKILL.md), revision 4e3050c1750f\n- Action item tracker: [complete method](../executive-action-register/SKILL.md), revision 7a2659d6aecd\n- Recurring task procedure writer (support method): [complete method](../repeat-task-step-guide-writer/SKILL.md), revision e06dda10c5ae\n- me.md builder (context setup): [complete method](../me-md-builder/SKILL.md), revision 3d3708ece93a\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":"document-a-clinic-appointment-intake-process","name":"Clinic booking procedure writer"},{"id":"process-doc-freshness-keeper","name":"Process guide revision reviewer"},{"id":"set-up-a-documentation-system-and-write-sops-that-pass-a-check","name":"Team documentation, procedure and runbook planner"},{"id":"write-a-procedure-test-it-and-build-a-training-deck","name":"Procedure draft, newcomer test and training-deck builder"}],"sourceHash":"02028331e7a5bdafc90f86ae13699d45b1dcd7e49a2c697ad55a35587364ce98"}