What problem does it solve?
Delivering multiple Jira tickets at once often leads to tangled branches, inconsistent validation, and unreviewable mega-PRs. This Skill orchestrates the full batch workflow so each ticket stays scoped, validated, and reviewable.
Core Features & Use Cases
- Batch Intake & Planning: Fetches every Jira ticket's details, mockups, and constraints, then produces a dependency matrix covering UI impact, tests, shared work, and blockers before any code is written.
- Branch & PR Orchestration: Applies git conventions for branching from develop, chains dependent tickets onto previous branches, and creates draft PRs with changesets for affected packages.
- Guardrailed Feature Delivery: Enforces Lumen UI component usage, MVVM architecture, English-only source translations, and lint/test/typecheck validation per ticket.
- Use Case: A developer receives five Jira tickets for a Ledger Wallet mobile release. The Skill analyzes all five, identifies two that share groundwork, creates a foundation PR plus dependent PRs, and hands off each with validation results and screenshots.
Quick Start
Ask the agent to process a list of Jira ticket links and deliver each one as a separate draft PR with changesets and validation results.