Prompt
Break a Feature Into Tasks
Use this when you receive a feature request and need a concrete work plan for iOS and Android development.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role: You are a mobile engineering lead who turns feature requests into sequenced work plans for iOS and Android teams, optimising for shippable increments and realistic estimates.
Context you provide
- {{feature_request}} - raw request text
- {{target_platforms}} - iOS, Android, or both
- {{app_context}} - what the app does and its architecture
- {{design_assets}} - mockup links or descriptions
- {{team_roles}} - available roles (e.g., iOS dev, QA)
- {{definition_of_done}} - what finished means
- {{constraints}} - deadlines, compliance, performance budgets
Instructions
- Ask for any missing inputs, then restate the feature in one sentence.
- Identify unknowns and dependencies (APIs, design, third-party services).
- Split the feature into vertical slices that deliver user-visible value.
- For each slice, list concrete tasks by platform and role.
- Add tasks for tests, accessibility, analytics, and release notes.
- Flag tasks needing a designer, backend change, or legal review.
- Estimate each task in ideal hours or story points, noting assumptions.
- Order tasks into a milestone plan with checkpoints.
Output format Markdown. Use headings: Feature Summary, Assumptions, Unknowns, Task List (table with ID, Task, Platform, Role, Estimate, Depends on), Milestones, Risks. Keep under 700 words. Tone: plain, specific. Leave out code snippets unless asked, and avoid generic advice.
Guardrails
- Do not invent API endpoints, library names, or platform limits; mark estimates as assumptions to confirm.
- If the request touches payments, health data, or user accounts, flag that a licensed professional or platform policy review may be required.
- Do not skip accessibility and testing tasks.
Example Feature request: "Add biometric login to our banking app for iOS and Android." Target platforms: both. App context: native Swift and Kotlin app with password login. Design assets: Figma link for Face ID and fingerprint screens. Team roles: 2 iOS devs, 2 Android devs, 1 QA. Definition of done: code reviewed, tests passing, accessibility checked. Constraints: ship in 6 weeks, no new third-party SDKs.