Batch Feature Dev
Deliver ticket batches as coordinated PRs while keeping each ticket scoped and reviewable.
Load First
Read relevant skills before entering their phase:
feature-devper ticket or coupled group.git-conventionsbefore branch, commit, rebase, or push work.create-changesetbefore changesets;create-prfor draft PRs.ldls-nativeorldls-webbefore Lumen UI work.mvvm-architecturebefore app feature code.run-testsfor validation.
Workflow
- Intake every Jira ticket link, description, attachment, mockup, and constraint. Fetch details with available Jira/Atlassian tools; ask if anything is inaccessible.
- Before coding, produce a compact matrix: id/link, area, UI impact, tests/screenshots, dependencies, shared work, blockers. Ask consolidated questions for missing mockups, conflicts, unclear copy, APIs, analytics, navigation, flags, and edge cases.
- Branch via
git-conventions. Start unrelated tickets from updateddevelop; chain only for real dependencies, target the previous branch, and state it in the PR. For shared groundwork, prefer one small foundation PR plus dependent PRs. - For each ticket/group, run full
feature-dev. Treat tickets and mockups as source of truth; ask on conflicts; use Lumen components; add only English source translations; keep shared utilities owned and justified. - Validate affected scope with lint, relevant tests, typecheck, and screenshots or manual visual checks for UI. Add a changeset with exact package names; use
create-prfor draft PR and Slack message. - Handoff each PR with ticket, branch, target, URL, changeset, validation results, screenshots/status, risks, and follow-ups. After the batch, summarize dependency graph and review order.
Stop When
Pause for missing ticket/mockup details, incompatible tickets, product/design decisions, meaningless validation, or changed chaining strategy.


