name: android-dev-workflow
description: End-to-end Android development workflow: Fetch Jira ticket -> Create Branch -> Implement with Best Practices -> Create MR.

Android Development Workflow

This skill combines the Jira Ticket Implementation workflow with the Android Development Assistant expertise. It guides the agent through the full lifecycle of a task while enforcing team coding standards and architectural patterns.

Prerequisites

• Access to Jira MCP tools.
• Access to GitLab MCP tools.
• git configured in the terminal.

Workflow Steps

1. Acquire Jira Information

1. Ask User: If the Jira ticket ID is not provided in the prompt, ask the user for it.
2. Fetch Details: Use the available Jira MCP tool to get the ticket details.
   • Key fields: Summary, Description, Acceptance Criteria.
   • Goal: Understand what needs to be implemented.

2. Setup Git Environment

1. Branch Naming:
   • Format: <Jira-Ticket-ID> (e.g., ANDROID-123).
   • Strict Rule: Do NOT use feature/ prefix. Use the uppercase Ticket ID directly.
2. Create Branch:
   • Run git checkout develop (or the project's base branch).
   • Run git pull.
   • Run git checkout -b <branch_name>.

3. Implementation Loop (with Android Dev Assistant)

Crucial: During implementation, strictly follow the team's engineering standards.

architectural Context

• Architecture: MVVM (No Clean Architecture domain layer).
• DI: Koin.
• UI: Jetpack Compose.
• Min API: 34+ (Android 14).

Reference Guides

Consult these guides for specific implementation details:
- Performance: references/performance-optimization.md (Recomposition, List performance, Memory)
- Architecture: references/mvvm-patterns.md (ViewModel, Repo, StateFlow)
- UI Patterns: references/compose-ui-patterns.md (Layouts, Theming, State)
- Testing: references/testing-patterns.md (Unit/Integration tests)
- CI/CD: references/ci-cd-android.md (Pipelines, Build variants)

Implementation Steps

1. Plan: Analyze requirements. Consult the References above to choose the right patterns.
2. Code: Implement changes.
   • Use Kotlin best practices.
   • Adhere to Material 3 design.
3. Verify:
   • Ensure code conceptually compiles.
   • Add/Update unit tests where appropriate (refer to Testing Patterns).

4. Create GitLab Merge Request

1. Commit & Push:
   • Run git add .
   • Run git commit -m "<Jira-Ticket-ID>: <Jira-Ticket-Summary>"
   • Run git push -u origin <branch_name>
2. Create MR:
   • Use the GitLab MCP tool.
   • Source Branch: <branch_name>
   • Target Branch: develop.
   • Title: <Jira-Ticket-ID>: <Jira-Ticket-Summary>

   • Description:
     ```markdown
     Closes

     Changes

     (Summary of technical changes)

     Jira Link

     (Link to Jira ticket)
     `` - **Draft**: Default tofalse` unless requested.

Notes

• If any MCP tool fails, report to the user.
• Always verify the base branch name.