mobile-agent

Generate and maintain cross-linked mobile screen specs from UC and SRS documents.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill mobile-agent-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-agent
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/mobile-agent
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill mobile-agent-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a mobile app's screen inventory complete and consistent with evolving use cases and SRS requirements is tedious and error-prone. This Skill automates the discovery, generation, and synchronization of screen specification files so no required screen is missed and no navigation link is broken. ## Core Features & Use Cases - Screen Discovery & Gap Analysis: Scans UC/SRS documents to identify every required screen (including hidden dialogs and error states) and reports which specs are missing. - Spec Generation & Editing: Creates standardized screen spec files from templates with navigation links, UI states, data requirements, and accessibility constraints. - Cross-Link Integrity Sync: Validates orphan screens, broken links, one-way links, and stale API endpoints, then updates the Screen Index README on every run. - Use Case: After a UC change in the HealthGuard mobile app, run TASK sync to detect affected screens, update their specs with bidirectional links, and regenerate the Screen Index automatically. ## Quick Start Ask the AI to run mobile-agent TASK full to scan the SRS, generate missing screen specs, fix cross-links, and update the Screen Index.

Frequently Asked Questions about mobile-agent

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

FAQPage Schema
How do I generate screen specs from use case documents?▼

Run the TASK generate sub-command with a module name to scan UC/SRS files and create missing screen spec files using the provided template. Each spec includes navigation links, user flows, four UI states, data requirements, and accessibility constraints.

How to keep mobile screen documentation in sync with SRS changes?▼

Use TASK sync after any UC change to validate cross-link integrity across all screen files. It detects orphan screens, missing screens, broken links, one-way links, and stale API endpoints, then updates the Screen Index README.

What sub-commands does the mobile screen management workflow support?▼

Five sub-commands exist: TASK scan discovers screens from SRS, TASK generate creates specs for a module, TASK update edits a specific screen, TASK sync validates cross-links, and TASK full runs the complete pipeline.

Can this workflow delete obsolete screen spec files?▼

No, screen files are never deleted. Obsolete screens are marked with a Status: Obsolete section instead, and any modification affecting five or more lines requires a diff preview before overwriting.

What accessibility requirements apply to medical app screen specs?▼

Every screen spec must enforce minimum 16sp body font, 48dp touch targets (56dp for emergency UI), 4.5:1 contrast ratio per WCAG AA, and TalkBack/VoiceOver semantic labels for all interactive elements.