Key takeaways
- Kiro only writes the requirements you ask for – Apple's rules are not in your specs until you add them.
- A release steering file that loads when Kiro touches Info.plist, entitlements or the privacy manifest keeps those files from drifting.
- Agent hooks are useful reminders, not proof: back them with a real build and test run on a Mac with Xcode 26.
- Your requirements.md is the best raw material for review notes – it already lists every feature and where it lives.
Why a spec-driven app has a head start in App Review
Kiro is AWS's agentic IDE. Instead of steering one long chat, you work through specs: each feature gets a folder under .kiro/specs/ with a requirements.md (user stories and acceptance criteria in EARS notation), a design.md and a tasks.md that the agent works through in order.
That structure suits an App Store release better than most people expect. An App Review session is a behaviour test: the reviewer installs the build, signs up, taps through the main flows, looks for the paywall and checks whether an account can be deleted. If the intended behaviour is written down as acceptance criteria, you can verify it before Apple does.
The catch is simple. Kiro turns your prompt into requirements – it does not add Apple's rules on its own. In the iOS projects we see, the same gaps come up again and again:
- a sign-up spec with no matching "delete my account" requirement,
- Google sign-in specified, Sign in with Apple missing,
- a premium feature designed around a web checkout,
- no requirement for the first-launch state, so new users see empty lists or sample data,
- permission prompts with generic purpose strings.
Each of these is a typical rejection reason, and each is a missing line in a spec.
Steering files: tell Kiro the release facts once
Steering files live in .kiro/steering/. Kiro can generate three foundation files – product.md, tech.md and structure.md – that are included in every interaction. Use tech.md for the build facts the agent would otherwise guess: the Xcode scheme, the simulator destination for tests, the minimum iOS version and the signing approach.
Then add a separate release file with the fileMatch inclusion mode, so it loads whenever Kiro works on the files App Review cares about: Info.plist, the .entitlements file, PrivacyInfo.xcprivacy and the project file. Its body can be short:
# iOS release rules - Bundle ID and team are fixed. Never change them. - Do not add capabilities or entitlements without asking. - Every permission needs a purpose string that names the feature using it. - New SDKs: check for a privacy manifest and list the SDK in docs/release-log.md. - Digital content is sold with StoreKit only. No external payment links.
Kiro's steering documentation describes the inclusion modes. If your team also uses other agents, Kiro reads AGENTS.md as well; our guide to CLAUDE.md and AGENTS.md for mobile projects shows how to keep one source of truth.
Talk to an AI Code Engineer about shipping your app to the App Store.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
Write Apple's rules into requirements.md
The most effective change is also the least technical: give the App Store rules their own requirements, with acceptance criteria a tester can tick off. A table like this one, turned into user stories, covers most first-submission problems:
| Guideline | Requirement to add | Acceptance criterion |
|---|---|---|
| 5.1.1(v) | Users who can create an account can delete it in the app | Settings shows "Delete account"; after confirmation the account and its data are gone and the user is signed out |
| 4.8 | Third-party sign-in comes with an equivalent privacy-friendly option | Wherever Google sign-in appears, Sign in with Apple appears too |
| 3.1.1 | Digital upgrades use In-App Purchase | The paywall shows StoreKit products; restore purchases works |
| 2.1 | No unfinished features ship | Every visible button leads somewhere; no placeholder text or sample data |
| 4.2 | The app offers value beyond a website | The core task uses native features such as offline storage, notifications or the camera |
In EARS style, one of these reads like this – plain enough for the agent and for the person checking the TestFlight build:
WHEN a signed-in user confirms "Delete account" THEN the system SHALL delete the account and all personal data on the server AND the system SHALL sign the user out and show the welcome screen.
Our App Store review checklist for AI-built apps lists more candidates, and Sign in with Apple for AI-built apps covers the login requirement in detail.
Agent hooks as release guards
Kiro's agent hooks run an instruction when something happens in the workspace, for example when a file is saved. For an iOS release, three hooks earn their place:
- Dependencies changed. When
Package.resolvedorPodfile.lockchanges, the agent lists new SDKs, checks whether each ships a privacy manifest and notes whether your App Privacy answers need an update. - Info.plist changed. The agent checks every usage description: does it name the feature and the reason, in the app's language?
- Paywall code changed. The agent confirms that no link or button leads to an external purchase of digital content.
Treat hook output as a reminder, not as proof. A hook is an instruction to a language model, so it can miss things. The hard checks belong in a build: an archive with Xcode 26 and the iOS 26 SDK, unit and UI tests, and an upload that would fail on missing required-reason declarations. An upload that was already flagged with ITMS-91053 is covered in our ITMS-91053 rejection guide.
Building, signing and TestFlight: where Kiro stops
Kiro runs on your machine, so on a Mac with Xcode it can call xcodebuild, run tests on a simulator and execute fastlane lanes. On Windows or Linux, the archive has to happen on a macOS CI runner instead.
Put the pipeline into tasks.md like any other feature – a lane for tests, one for the archive, one for the TestFlight upload – and let Kiro implement it. The parts that require your Apple identity stay with you: enrolling in the Apple Developer Program (organizations need a D-U-N-S Number), accepting agreements, creating the app record, generating the App Store Connect API key and choosing who manages certificates. Our fastlane setup with coding agents covers the details.
Then test with people. Internal TestFlight testers get builds immediately; external testers after the beta app review. When feedback arrives, add it to the spec as a new task or a corrected acceptance criterion instead of fixing it in a side chat. That keeps the spec true – which matters for the next step.
From specs to review notes – and who sends them
Review notes fail when they are vague. Your specs are not. Ask Kiro to draft the notes from the requirements: one line per feature, where to find it, whether it needs a login or a purchase, plus the demo account. Edit the draft yourself – remove internal wording and check that every feature listed really is in the build you submit.
The fields around it are yours to answer: App Privacy details, age rating, export compliance, screenshots and the reply when App Review comes back with a question. If you would rather hand that part off, our AI Code Engineers take over signing, CI/CD, the listing and the review conversation in your own Apple Developer account through our iOS submission service. Teams that want to get better at the spec-first way of working can join a spec-driven development workshop.
Planning an Android version as well? Kiro app to Google Play shows which Play requirements belong in the same specs.
Kiro iOS release checklist
- Account deletion, Sign in with Apple and In-App Purchase have their own requirements and acceptance criteria.
- A release steering file loads whenever Kiro touches Info.plist, entitlements or the privacy manifest.
- tech.md names the scheme, test destination, deployment target and signing approach.
- Hooks flag new SDKs and changed permission texts, and a real build verifies them.
- A Mac or macOS runner with Xcode 26 produces the archive, not a developer laptop nobody else can reach.
- TestFlight feedback went back into the specs as tasks, not ad-hoc fixes.
- Review notes are drafted from requirements.md and checked against the submitted build.
- The App Privacy questionnaire reflects every SDK and data flow in the release log.
Frequently asked questions
Can Kiro build and upload an iOS app?
On a Mac with Xcode installed, Kiro can run the commands that build, test and upload – for example a fastlane lane. For that it needs certificates, profiles and an API key you generated. Enrolling, setting up the app record and pressing Submit for Review are things only the account holder can do.
Do Kiro specs replace an App Store checklist?
They can hold one. Specs only contain what you put into them, so add Apple's requirements as user stories with acceptance criteria. Then the checklist is part of the app's definition instead of a document nobody opens before submission.
Does Apple treat apps built with Kiro differently?
No. App Review judges the submitted app against the guidelines, whatever tool produced the code. Kiro-built apps are rejected for the same reasons as others – missing account deletion, login or payment issues, incomplete features or thin native value.
Who should own signing for a Kiro project?
The account holder. Let Kiro implement the pipeline, but keep certificates, profiles and the API key under the control of a person on your team – stored as CI secrets, never in the repository or a steering file.
Can someone help us finish the release?
Yes. In a free call, an AI Code Engineer goes through your specs and the current build with you and tells you what is missing. We can also run the whole release – signing, pipeline, listing and review replies – inside your own Apple account.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.