From flutter-craft
Dispatches parallel agents for 2+ independent Flutter tasks like separate features, test files, or Clean Architecture layers without shared state or dependencies.
npx claudepluginhub vp-k/flutter-craftThis skill uses the workspace's default tool permissions.
When you have multiple unrelated tasks (different features, different test files, different bugs), working on them sequentially wastes time. Each investigation is independent and can happen in parallel.
Provides expert Flutter/Dart patterns for cross-platform mobile apps including feature-first project structure, const widget best practices, and Riverpod/Bloc state management.
Guides expert Flutter 3.x and Dart 3.x development for multi-platform apps, including advanced widgets, state management with Riverpod/Bloc/GetX, performance optimization, and architecture patterns.
Provides expert guidance on Flutter 3.x and Dart 3.x for multi-platform apps, including advanced widgets, state management (Riverpod, Bloc), animations, testing, architecture, and performance optimization.
Share bugs, ideas, or general feedback.
When you have multiple unrelated tasks (different features, different test files, different bugs), working on them sequentially wastes time. Each investigation is independent and can happen in parallel.
Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.
Announce at start: "I'm using the flutter-parallel-agents skill to handle these tasks."
Multiple tasks/failures?
├─ NO → Single agent handles it
└─ YES → Are they independent?
├─ NO (related) → Single agent investigates all
└─ YES → Can they work in parallel?
├─ NO (shared state/files) → Sequential agents
└─ YES → Parallel dispatch (this skill)
Use when:
Don't use when:
lib/features/auth/
├── domain/ ← Agent 1: Implement entities & interfaces
├── data/ ← Agent 2: Implement models & datasources
└── presentation/ ← Wait for Agents 1 & 2 (has dependencies)
Can parallelize: Domain + Data layers (different files) Cannot parallelize: Presentation depends on Domain
lib/features/
├── auth/ ← Agent 1: Auth feature
├── profile/ ← Agent 2: Profile feature
└── settings/ ← Agent 3: Settings feature
Can parallelize: All three (different feature folders)
test/features/
├── auth/data/repositories/auth_repo_test.dart ← Agent 1
├── profile/presentation/bloc/profile_bloc_test.dart ← Agent 2
└── settings/data/datasources/settings_ds_test.dart ← Agent 3
Can parallelize: Different test files, different features
Group tasks by what's affected:
Each domain is independent - fixing auth doesn't affect settings.
Each agent gets:
Task("Implement auth domain layer - entities and repository interface")
Task("Implement profile domain layer - entities and repository interface")
Task("Implement settings domain layer - entities and repository interface")
// All three run concurrently
When agents return:
flutter analyzeflutter testImplement the [Layer] layer for [Feature] feature.
## Scope
lib/features/[feature]/[layer]/
## Files to Create
- entities/[entity].dart
- repositories/[repository].dart (interface)
## Requirements
[Paste specific requirements from plan]
## Constraints
- ONLY modify files in lib/features/[feature]/[layer]/
- Do NOT touch other features
- Follow Clean Architecture principles
- Run flutter analyze before committing
## Expected Output
- Summary of what you created
- flutter analyze result
- Commit message used
Scenario: Need to implement domain layers for 3 features
Decision: Each domain layer is independent
Dispatch:
Agent 1 → Implement auth/domain/ (User entity, AuthRepository interface)
Agent 2 → Implement profile/domain/ (Profile entity, ProfileRepository interface)
Agent 3 → Implement settings/domain/ (Settings entity, SettingsRepository interface)
Results:
Integration:
flutter analyze # All clean
flutter test # All pass
git log --oneline -3 # See all three commits
❌ Too broad: "Implement all features" - agent gets lost ✅ Specific: "Implement auth/domain layer" - focused scope
❌ Dependent tasks in parallel: Data layer before Domain ✅ Correct order: Domain first, then Data in parallel
❌ Same files: Two agents editing pubspec.yaml ✅ No conflicts: Each agent has isolated file scope
After agents return:
flutter analyze
flutter test
git diff --stat # See all changes