android-workflow

Android workflow automation routes tasks to appropriate workflows—feature, quick-fix, refactor, investigate, or hotfix—then enforces quality gates and a Self-Check Protocol to validate implementation before release. Each workflow sequence chains agents (planner, UX engineer, UI builder, code writer, test engineer, code critic) in order, with build verification and gate enforcement at each step.

Yes. This Skill integrates GitHub Actions within its workflow orchestration framework to route Kotlin and Compose Android projects through structured sequences, applying quality gates and build verification to ensure consistent quality across feature implementations, bug fixes, refactoring, debugging, and hotfixes.

Quick classification maps incoming tasks to one of five workflows: quick-fix, feature, refactor, investigate, or hotfix. The Self-Check Protocol validates the task before routing, then the correct workflow sequence executes with the appropriate agent chain and quality gates to steer the task to completion.

Yes. This Skill is designed specifically for Kotlin and Compose Android projects and handles task types including implementation, bug fixes, refactoring, debugging, and hotfixes through specialized workflow sequences, build commands, failure recovery, and quality-gate enforcement.

The Skill includes failure recovery guidelines and build verification steps within each workflow sequence. Quality gates enforce validation; if a build fails, the workflow captures the failure and applies recovery procedures to help identify and resolve the issue before proceeding to the next gate.

The Skill defines an MCP tool requirements and quality gates framework that ensures consistent quality across workflows. Gates are applied at each agent transition and after build/test verification, blocking progression until quality standards are met.