android-workflow

Orchestrates Android development workflows for Kotlin/Compose projects.Routes tasks to appropriate workflow: feature, quick-fix, refactor, investigate, hotfix.Use when user requests: implementation (구현, 추가, 새 기능, 만들어, 개발, 적용),bug fixes (버그, 수정, 오류, 고쳐), refactoring (리팩토링, 개선, 정리),debugging (분석, 원인, 왜, 디버깅, 안돼), or hotfix (긴급, 프로덕션, 핫픽스).Provides Self-Check Protocol and Quality Gates for implementation tasks.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

The Android Workflow Orchestrator is a professional-grade Claude skill designed to automate and streamline the Android development lifecycle for Kotlin and Jetpack Compose projects. It acts as an intelligent task router that directs development requests—such as feature implementation, refactoring, debugging, and emergency hotfixes—into standardized, multi-step workflows. By enforcing a 'Self-Check Protocol' and rigorous 'Quality Gates,' it ensures that every code change meets high-quality standards, passes build checks, and follows architectural best practices, significantly reducing manual overhead for Android engineers.

Use Cases

  • New Feature Implementation: Orchestrates a complete development pipeline from requirement planning and UX/UI design to code generation and final critique.
  • Automated Bug Investigation: Analyzes complex error logs and mysterious crashes to identify root causes and automatically route them to the appropriate fix workflow.
  • Production Hotfixes: Executes a high-priority, streamlined workflow for critical production issues, ensuring rapid deployment with essential smoke testing.
  • Codebase Refactoring: Manages large-scale structural improvements while preserving functional behavior through automated testing and quality assurance gates.
  • Quality Control & Build Automation: Enforces strict criteria where tasks are only marked complete if the build succeeds and the code meets predefined quality metrics.
nameandroid-workflow
description|
Routes tasks to appropriate workflowfeature, quick-fix, refactor, investigate, hotfix.
Use when user requestsimplementation (구현, 추가, 새 기능, 만들어, 개발, 적용),

Android Workflow Orchestrator

Routes Android development tasks to appropriate workflows and manages quality gates.

Self-Check Protocol (MUST DO)

Before starting implementation tasks, verify:

# Question Action if No
1 Is this an implementation task? Handle directly
2 Has the workflow been classified? Call task-router first
3 Following the correct sequence? Re-check workflow
4 Trying to skip an agent? Never allowed, follow sequence

Quick Classification

Classification Criteria

Condition Workflow
Files ≤2, single layer, no UI/API/DB quick-fix
New feature, new screen feature
Structure change, behavior preserved refactor
Unknown bug cause, error analysis investigate
Production emergency hotfix

Auto-Upgrade Rules

Trigger From To
UI changes detected quick-fix feature
Files 3+ quick-fix feature
API/DB changes quick-fix feature
Build fails 2x any investigate

Workflow Sequences

Agent execution order for each workflow:

Workflow Sequence
quick-fix code-writer → code-critic
feature planner → [ux-engineer] → [ui-builder] → code-writer → test-engineer → code-critic
refactor planner → code-writer → test-engineer → code-critic
investigate investigator → (route based on findings)
hotfix code-writer → test-engineer(smoke) → code-critic

Detailed Guides:

Quality Gates

Gate Checkpoint Criteria
Gate 0 task-router Classification complete
Gate 1 planner Requirements clear, tasks defined
Gate 2 code-writer Build succeeds
Gate 3 code-critic 0 critical, ≤2 major issues

Detailed Criteria: gates/quality-gates.md

MCP Tool Requirements

Workflow sequential-thinking context7 codex-cli
quick-fix Skip Optional 1 round
feature 3+ steps Required 2+ rounds
refactor 3+ steps Optional 2+ rounds
investigate 5+ steps Optional Optional
hotfix Skip Optional 1 round

Build Commands

# Full build
./gradlew build

# Module build
./gradlew :feature:home:build

# Run tests
./gradlew test
./gradlew :feature:home:testDebugUnitTest

# Clean build
./gradlew clean build

Failure Recovery

On build or gate failure:

  1. Record: Log error messages and environment info
  2. Retry: Auto-retry once
  3. Escalate: If still failing, present options
    • A: Manual fix then retry
    • B: Call investigator
    • C: Abort task