Hire an AI mobile app release planner

Everything it can hand back

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

• A signing check that lists each key or certificate, who holds it and when it expires
• A go or no-go list marked Pass, Fail or Not supplied
• A list of likely store rejection risks, each with a fix
• A staged rollout plan with the share of users at each stage and when to pause
• A recovery plan for shipping a fix fast

How it does the job well

• Store rules change. Say "check this against the store's current guidelines" for review rules, privacy form fields, rollout schedules and crash-rate limits. Never present a number from memory as the store's limit.
• Never write "safe to ship" without evidence. Mark each check Pass (seen in the user's material), Fail (seen and wrong) or Not supplied.
• Pause numbers are proposals. Use the user's own numbers when given. When you propose numbers, label them "proposed, confirm with your team".
• Do not log in, submit, publish, change a live system or spend money. Prepare the plan and ask first.
• A rollout can be paused but a shipped build cannot be pulled back. Say so in the plan: recovery means shipping a fix.
• Signing identity is infrastructure, not a laptop file. Certificates and keystores live in a shared, encrypted, access-controlled store (fastlane match, a secrets manager, or Play App Signing) — never emailed, never in git, never on one person's machine. A lost keystore can mean you can never update the app again.
• You cannot un-ship a binary. There is no rollback, only roll-forward. So: phased rollouts always, halt-on-crash-spike thresholds defined in advance, and the ability to pause a rollout at the first bad signal.

Mistakes it avoids

• Planning a release straight to 100% of users.
• Treating a debug build as proof the release build works.
• Copying the profile's sample fastlane code or thresholds as the user's facts.
• Advising anyone to store keys in git, email or one person's laptop.
• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.

What a good result looks like

An example, not your task: You are about to send your first app version to the App Store or Google Play and want the steps in the right order.

• Release scope. The app, platforms, version and date the plan covers.
• Signing check. Each certificate or key, who holds it, when it ends and the risk.
• Go or no-go list. Version numbers, privacy forms, crash files, store text and test build, each marked Pass, Fail or Not supplied.
• Store review risks. The likely reasons for rejection that fit your app, each with a fix.
• Rollout plan. Stages from test users to everyone, what to watch and when to pause.
• Recovery plan. How to ship a fix, who is on call and what to tell users.

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.

Capabilities

• Fix the scope. It confirms the app, the platforms, the version and the date. Anything missing is asked once, then marked MISSING.
• Check signing. It lists each certificate, profile and key, who holds it and when it ends. It flags any key that lives on one laptop.
• Run the go or no-go list. It checks version and build numbers, privacy forms, crash-report files, store text and the test build. Each line is marked Pass, Fail or Not supplied.
• Look for review trouble. It matches your app and any rejection text to the common reasons stores say no, and suggests a fix for each.
• Plan the rollout. It sets stages from test users to everyone, what to watch at each stage and the signs that mean pause.
• Plan the recovery. It writes how you would ship a fix, who is on call and what to tell users.

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-mobile-release-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-mobile-release-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

• The app name, whether it is iOS, Android or both, and what changed in this version
• How you sign and ship today, and who holds the keys (never paste passwords or key files)
• Your target release date and who can approve it
• A store rejection message, if you have one (optional)
• Your version history and the tool that collects crash reports (optional)

Helpful context (optional)

• The name of your crash-report tool, such as Crashlytics, if you use one.
• Your last three version and build numbers.
• The full text of any store rejection.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It can read your build settings, release notes and a pasted rejection email next to your description.

Functions and deliverables

• Mobile app release planner: Plan your iOS or Android app release. Get a signing check, a go or no-go list, a staged rollout and a recovery plan before you submit to the store.
  • A signing check that lists each key or certificate, who holds it and when it expires
  • A go or no-go list marked Pass, Fail or Not supplied
  • A list of likely store rejection risks, each with a fix
  • A staged rollout plan with the share of users at each stage and when to pause
  • A recovery plan for shipping a fix fast
  Source: Michael Sitarzewski and Agency Agents contributors.
• Version and release notes planner: Use Git history and release rules to draft version changes, changelogs, and release tool settings.
  • The rule for your next version number, with the bump it gives
  • A release config file for semantic-release or standard-version
  • A GitHub Actions release workflow, if you pick semantic-release
  • A CHANGELOG.md entry format
  • A one-page commit message guide for your team
  Source: sickn33.
• App Store release notes writer: Share your app’s code history. Get plain “What’s New” notes users can read, based on real changes.
  • Five to ten user-friendly bullets
  • Changes grouped by theme
  • Internal work left out
  • Each bullet checked against a real change in your history
  Source: sickn33.
• Release day rollback planner: Plan a safe release before you ship. Paste what you are releasing and where it runs. Get checks, steps, a rollback plan and a way to confirm it worked.
  • A risk rating with the reason
  • A pre-release checklist
  • Steps with pause points
  • Undo signs and steps, and a post-release check
• 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.

Tasks you can use it for

• You are about to send your first app version to the App Store or Google Play and want the steps in the right order.
• The store rejected your last build and you need a fix plan before you try again.
• A signing certificate is close to expiring, or one person holds all the keys.
• You ship each update by hand and want a plan that makes every release the same.

Limits to check before starting

• You release a website or a back-end service, not an app. Use the Release safety planner, or the Deployment pipeline designer for a build and deploy pipeline.
• A bad version is live right now. Use the Incident response coordinator, and ask someone with store access to pause the rollout first.
• You build with Expo and want builds made and sent for you. Use the Expo app deployment 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, paste SKILL.md into a new chat, then paste references/source-agent.md.
• Describe the release in plain words. Say the app, the platforms, what changed and the date you want.
• Add how you sign and ship now, and any rejection message. Do not paste passwords, private keys or key files. Say who holds them instead. No code running or web access is needed.
• Type "Plan this release. Mark anything you cannot check as MISSING, and do not call it safe without proof."
• Read the go or no-go list first. Fix every Fail or Not supplied line, then ask for the plan again.
• Give the rollout and recovery plans to the person who has store access. The AI cannot submit or log in for you.

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-mobile-release-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.