Hire an AI electrical design reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A list of every input with its unit and source, and what is MISSING or ASSUMED
• Sizing sums for the parts you asked about, each with inputs, formula, standard and result
• A table of differences between your documents, such as a drawing that says 100 A where the parts list says 63 A
• Pass, fail or not checked for each clause it used
• A list of open risks, and a closing line that a licensed electrical engineer must sign off

How it does the job well

• Never state that a design complies, and never stamp or certify. State which clauses were checked, what passed, what failed and what was not checked.
• Do not quote a standard clause from memory as fact. Say that the user must check each clause against the edition they hold.
• Write no step that implies live work. Isolation, lock-out and test-before-touch are required steps.
• Local authority, utility and operator rules override generic standards. If they were not supplied, say so.
• Offer an inspection checklist, a draft parts list or software check rules only after the review, and only if asked.
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You have a site survey, a single-line drawing and a parts list, and you suspect they disagree.

• Basis. The standards and editions used, backup hours, spare capacity and redundancy level.
• Inputs. Every value with its unit and source, plus the MISSING and ASSUMED lists.
• Sizing sums. One block per part, showing inputs, formula, clause, result and pass or fail.
• Document differences. Each place your drawing, survey record and parts list disagree, with a proposed fix.
• Findings. Pass, fail or not checked for each clause used.
• Open risks. What is still unknown and what would settle it.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Margaret Hamilton and Andrew Chen would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Check the inputs. It converts values to SI units, keeps a unit on every number, never adds kW to kVA, and lists what is MISSING.
• Set the basis. It names the standards and editions, the spare capacity, the backup level and the pass rule for each sum, with every assumption and its reason.
• Do the sums in order. It works from load to DC plant, then cables and protection, then backup power, then earthing, because each step feeds the next.
• Compare the documents. It cross-checks the drawing, survey record and parts list, and logs each difference with the two sources.
• Judge each result. It marks each clause pass, fail or not checked, and compares answers with rules of thumb to spot outliers.
• Package the review. It lists open items, and adds the line that a licensed engineer must review and sign before building, switch-on or submission.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-electrical-engineer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-electrical-engineer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your design basis: site type, voltages, backup hours needed, how often the grid fails, and the standards your project or operator uses
• Your load list, with a unit on every number (W, kW or kVA) and the power factor for AC loads
• Documents to check, such as the single-line drawing, cable list, parts list and survey record (optional)
• The battery data sheet, showing capacity, discharge rate and end voltage per cell, if batteries are in scope
• Site facts such as lowest air temperature, height above sea level and soil resistance (optional)

Helpful context (optional)

• The manufacturer data sheet for each battery, rectifier and generator.
• Your operator's own limits, such as low-voltage disconnect level and earth resistance target.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It reads several documents at once and compares them line by line.

Functions and deliverables

• Electrical design reviewer: Get an electrical design review with checked units, sizing sums, standards and open risks. A licensed engineer must sign off before building.
  • A list of every input with its unit and source, and what is MISSING or ASSUMED
  • Sizing sums for the parts you asked about, each with inputs, formula, standard and result
  • A table of differences between your documents, such as a drawing that says 100 A where the parts list says 63 A
  • Pass, fail or not checked for each clause it used
  • A list of open risks, and a closing line that a licensed electrical engineer must sign off
  Source: Michael Sitarzewski and Agency Agents contributors.
• Oracle migration risk reviewer: Check Oracle to PostgreSQL migration work against 14 known behavior gaps and get a risk table, test coverage check and pass or fail verdict.
  • A table with one row per risk that applies to your code
  • For each risk, the affected file and the fix to apply
  • A note on any risk that needs a design decision from you
  • A check of whether your tests cover each risk
  • A pass or fail checklist
  Source: GitHub Copilot community.
• New user drop-off finder: Find where new users drop off between visit, sign-up and day 30. Get the biggest leak, the missing first-visit step and one fix to measure.
  • Your funnel, with the count and share at each step
  • The biggest drop, ranked, written before any feature idea
  • An estimate of how many sign-ups the feature would reach
  • The step or message missing from the first visit
  • One change for new users, with a measure, a target and a date
• Backwards unit planner: Give it your standards. Get a unit planned from the end result, then the proof of learning, then the activities.
  • Lasting understandings and key questions
  • A final assessment plan
  • A lesson-by-lesson learning plan
  • An alignment check
  Source: Gareth Manning.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.
• Margaret Hamilton: Review a system failure plan using Margaret Hamilton’s recorded approach. Check handoffs, priorities, warnings and what happens when people make mistakes.
  • Your problem worked on the way Margaret Hamilton would: their questions, their method, their push-back
  • The answer or the work, in Margaret Hamilton's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Andrew Chen: Review product growth, returning users or a two-sided market using Andrew Chen’s public work. Start with the funnel and the smallest useful network.
  • Your problem worked on the way Andrew Chen would: their questions, their method, their push-back
  • The answer or the work, in Andrew Chen's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You have a site survey, a single-line drawing and a parts list, and you suspect they disagree.
• You need a first sizing for batteries, rectifiers, a generator or a cable run before an engineer reviews it.
• You want the design basis written down before detailed calculation starts.
• You manage many sites and want clear pass or fail rules that your software can check on each record.

Limits to check before starting

• You plan to build, connect or switch on anything from this output. A licensed electrical engineer must review and sign it first.
• You need wiring advice for a home or a small job. Ask a licensed electrician in your area.
• You want a plan for the software inside a device. Use the Embedded firmware engineer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, open a new chat and paste SKILL.md, then references/source-agent.md.
• Paste your design basis and load list. Attach drawings, parts lists and survey records if you have them. Keep the unit on every number.
• Say what you want reviewed: sizing, a document check or both. Name your standards and editions if you know them.
• Your AI asks once for what is missing. Anything still missing is marked MISSING, and the sums that need it stop there.
• Read the MISSING list and the differences table first. Fix your inputs and run it again.
• Give the result to a licensed electrical engineer. Check each standard clause against the published edition before anyone relies on it.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-electrical-engineer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.