Envy-7z

mobile-delivery-command-center

Top-level orchestration skill for Android/Flutter delivery from feature implementation to review, conflict resolution, merge, release, and CI/CD improvement. Use when you want one lead workflow that routes tasks safely, keeps responses token-efficient, and protects production stability.

Envy-7z 0 Updated 3mo ago

Resources

2
GitHub

Install

npx skillscat add envy-7z/mobile-agent-skillpack/mobile-delivery-command-center

Install via the SkillsCat registry.

SKILL.md

Mobile Delivery Command Center

Overview

Route each task to the minimal right workflow so output stays high quality, safe, and token-cheap.

Routing Matrix

  1. Feature implementation (UI)
  • Use: mobile-lead-soul + mobile-ui-slicing-playbook (+ mobile-context-compression).
  1. Feature implementation (deep Kotlin logic)
  • Use: mobile-lead-soul + kotlin-deep-logic-coroutines (+ mobile-context-compression).
  1. CI/CD and release process improvement
  • Use: mobile-ci-cd-evolution + mobile-modern-clean-architecture.
  1. PR review and merge decision
  • Use: mobile-pr-merge-gatekeeper + mobile-lead-soul.
  1. Merge conflict handling
  • Use: mobile-conflict-resolution-safe + safe-refactor-guard.
  1. Release/publish go-no-go
  • Use: mobile-release-publish-gate + mobile-lead-soul.

Default Rules

  • Always choose the smallest safe patch first.
  • If evidence is insufficient, block (BLOCK/NO-GO) instead of guessing.
  • Keep communication token-cheap: decision first, short evidence, next actions.

Response Format

## Decision
- GO-SAFE | BLOCK | NO-GO

## Active Workflow
- Skills used:

## Evidence
- ...

## Next Actions
1. ...
2. ...

Guardrails

  • No risky architecture rewrite by default.
  • No merge/release recommendation without verification evidence.
  • No verbose status updates unless requested.

Resources

  • references/delivery-routing-cheatsheet.md