SKILL.md
Assess React Native Migration
Produce a read-only migration decision. Diagnose the product and delivery system; do not execute the migration.
Establish Product Scope
Run the assessment from a workspace that exposes as many production client codebases as possible. The current checkout is not evidence that it contains the whole product.
Before assessing readiness:
- Inspect the current repository and every workspace root available to the agent.
- Infer supported client platforms from product documentation, CI, release configuration, workspace manifests, submodules, and references to sibling repositories.
- Locate each production client codebase, including separate native iOS and Android repositories, app variants, and any web client relevant to staffing or proposed code sharing.
- Record a platform inventory with the client, repository or path, evidence of product membership, and access status.
When iOS and Android are both supported, inspect both native codebases before recommending a path. If a codebase remains unavailable, mark its evidence unknown, state that the assessment covers only the accessible platforms, and lower confidence accordingly. Do not infer that a platform is unsupported merely because its project is absent from the current repository.
Scope gate: every supported production client is listed, and each codebase is accessible, explicitly unavailable, or confirmed not to exist.