Hire an AI software prototype designer

Everything it can hand back

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

• One test statement, with the guess, the people who test it and the pass and fail marks
• A cut list of 3 to 5 features to build, and what you leave out
• A tool suggestion for each part, with the reason for each pick
• A day by day build schedule
• A plan to collect feedback and track use from the first user
• What to do if the test passes, and what to do if it fails

How it does the job well

• 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.
• Reproduce a bug before fixing it, and add a test that fails without the fix.
• Treat input from users, files and networks as untrusted. Validate it at the boundary.

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 an app idea and want to test it with real people before paying for a full build.

• Test statement. The guess to test, who tests it, and the pass and fail marks.
• Features to build. 3 to 5 features that serve the test, plus what you left out and why.
• Tools. The quickest tool for each part of the app, with the reason for each pick.
• Build schedule. What is finished by the end of each day or step.
• Feedback and tracking. How you collect comments from users and what you measure from the first day.
• Next steps. What to do if the test passes and what to do if it fails.

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 Kent Beck would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Set the guess. It turns your idea into one thing to test and names the people who will test it.
• Cut to the fewest features. It keeps the 3 to 5 features that serve the test and lists what it left out on purpose.
• Pick fast tools. It suggests the quickest tools for your skills and limits, such as ready-made sign-in, data and hosting services.
• Lay out the build. It orders the work by day, main user path first, polish last.
• Plan the feedback. It adds a feedback form, usage tracking and an optional A/B test from day one.
• Set pass and fail marks. It states what result means go on, change course or stop, and lists every assumption it made.

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-rapid-prototyper 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-rapid-prototyper/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 app idea in one or two sentences
• Who it is for and the problem it solves for them
• The one thing you want to find out, such as "will people finish sign-up?"
• Your limits, such as days, budget, who builds it and tools you already use
• Sketches, links to similar apps or existing code (optional)
• A few people you can show it to, such as 5 customers you can email (optional)

Helpful context (optional)

• Sketches or screenshots of apps you like, so it can match the main path.
• Questions your customers ask today, so the test statement uses their words.

Tools and access

• Claude, ChatGPT or Gemini: A chat is enough. The agent writes a plan, so it needs no code tools.

Functions and deliverables

• Software prototype designer: Turn an app idea into a prototype plan with one thing to test, 3 to 5 features, a build schedule and pass or fail marks.
  • One test statement, with the guess, the people who test it and the pass and fail marks
  • A cut list of 3 to 5 features to build, and what you leave out
  • A tool suggestion for each part, with the reason for each pick
  • A day by day build schedule
  • A plan to collect feedback and track use from the first user
  • What to do if the test passes, and what to do if it fails
  Source: Michael Sitarzewski and Agency Agents contributors.
• Five-day idea test planner: Describe an idea. Get a five-day plan to map, sketch, prototype and test it.
  • Day-by-day schedule with time limits
  • Sprint questions and target customer
  • Storyboard and prototype brief
  • Interview script for five users
  • Plan score with missing items
  Source: Wondel.ai.
• AI app and chatbot builder: Describe the chatbot, document question answerer or tool-using agent you want. Get starter code for your AI app in Python with LangChain.
  • Starter Python code for your chatbot, question answerer or agent
  • Install commands for the right packages
  • A document search setup, if your app needs one
  • An example of an agent that uses tools
  • A note on when a different library is a better fit
  Source: Orchestra Research.
• Software complexity reviewer: Share code or a design. Get a complexity score, failed checks and simpler module ideas.
  • A score out of 10
  • The failed checks with reasons
  • Specific refactors for each
  • A simpler module outline
  Source: Wondel.ai.
• 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
• Kent Beck: Plan a software change using Kent Beck’s recorded approach. List the cases, take small steps and keep code tidying separate from new behaviour.
  • Your problem worked on the way Kent Beck would: their questions, their method, their push-back
  • The answer or the work, in Kent Beck'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 an app idea and want to test it with real people before paying for a full build.
• A founder or client says "can we mock this up by Friday?" and you need a clear scope.
• You have a long list of feature ideas and need to cut it to the 3 to 5 that matter.
• You are about to show a first version to users and need to know what to measure.

Limits to check before starting

• You need code that is safe for real customers and payments. Use the Full stack developer to plan the build and the Code Reviewer agent to check it.
• You need a long-term system design for a product that already works. Use the Software architect.
• You want a roadmap or a ranked list of what to build next. Use the Product manager or the Sprint priority planner.

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, paste SKILL.md into a new chat, then references/source-agent.md.
• Type your idea, who it is for and the one thing you want to learn. Add your time, budget and tools.
• Say "Write the prototype plan. Ask me once if anything is missing."
• Read the test statement first. Check it is what you really want to learn, and fix it before you read the rest.
• Check the cut list. If a feature does not help the test, drop it.
• Take the plan to your builder or your no-code tool. This agent only writes. It does not run code, host the app or sign up for any tool.

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-rapid-prototyper 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.