skills.rest
tranhieutt
tranhieuttCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

team-mobile

Orchestrate mobile team workstreams for planning, design, build, testing, accessibility, and release.

70|42|Updated Mar 27, 2026
Search Tags:#accessibility#cross-platform#ux-design#qa-testing#release-planning#feature-release#mobile-team
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill team-mobile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-mobile
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/team-mobile
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill team-mobile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivering a polished mobile feature requires orchestrating design, implementation, accessibility, QA, and release tasks across multiple specialists, and this skill prevents any handoff from being skipped or rushed. It enforces phase reviews, user approvals, and documentation so the pipeline stays aligned with technical, accessibility, and store requirements through every step.

Core Features & Use Cases

  • Guided pipeline: Phase 1 captures platform decisions with AskUserQuestion confirmations, Phase 2 produces UX specs and wireframes, Phase 3 enforces implementation rules, Phase 4 audits accessibility, Phase 5 drives device testing, and Phase 6 prepares signing, builds, and submissions.
  • Outputs for each team: Platform briefs, UX deliverables, implementation summary with tests, accessibility reports, QA device logs, and release submissions keep every specialist accountable.
  • Use Case: Run this Skill when shipping a new cross-platform onboarding workflow that must meet accessibility standards, survive offline conditions, and launch simultaneously to iOS and Android stores.

Quick Start

Orchestrate the mobile team to design, implement, test, and release the described mobile feature across both platforms.

Frequently Asked Questions about team-mobile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate cross-platform mobile feature releases across iOS and Android teams?▼

Cross-platform mobile feature releases require orchestrating UX design, implementation, accessibility audits, and QA testing across iOS and Android pipelines with phase reviews and user approvals to ensure aligned feature shipping. This skill enforces documented outputs and store submission readiness before advancing.

What's the best way to manage UX design and accessibility audits for a mobile app feature?▼

Managing UX design and accessibility audits involves producing UX specs and wireframes in early phases, then enforcing accessibility pass/fail checks and generating audit reports before device testing. This structured pipeline keeps UX designers and accessibility experts accountable through documented deliverables.

How do I plan a mobile feature release pipeline that meets store submission requirements?▼

Planning a mobile feature release pipeline requires sequential phases from platform strategy and UX design through implementation, accessibility auditing, device testing, and store submission preparation. It ensures signing, builds, and submissions are prepared only after QA device logs and accessibility checks pass.

Can I use this mobile team orchestration workflow for offline onboarding features?▼

Yes, this mobile team orchestration workflow supports cross-platform onboarding workflows that must meet accessibility standards and survive offline conditions. It aligns developers, accessibility experts, and QA engineers to launch features simultaneously to iOS and Android stores.

Why does mobile feature delivery require phase reviews and user approvals before advancing?▼

Mobile feature delivery requires phase reviews and user approvals to prevent handoffs between specialists from being skipped or rushed. This ensures the pipeline stays aligned with technical, accessibility, and store requirements through every step of the process.

Does this mobile release workflow enforce device testing coverage before store submission?▼

Yes, this mobile release workflow drives device testing coverage and generates QA device logs during phase five. Store submission readiness is only prepared in phase six after accessibility pass/fail checks and device testing confirm the feature meets required standards.

Related Skills

Explore More Product & Management Skills→
marablemarcelmarablemarcel

mobile-design

Guide platform-specific mobile UX decisions for iOS and Android projects.

Community
Advanced
expoexpo
2.4k

eas-app-stores

Deploy Expo apps to iOS and Android stores using EAS CLI.

Official
Advanced
cenconq25cenconq25
39

ux-review

Audit UX specs for completeness, accessibility, and platform conventions.

Community
Advanced
solace-illsolace-ill

team-polish

Orchestrate a cross-functional polish team through a phase-based pipeline.

Community
Advanced