Use when you have a written implementation plan to execute with review checkpoints
/plugin marketplace add vp-k/flutter-craft/plugin install vp-k-flutter-craft-plugins-flutter-craft@vp-k/flutter-craftThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Load plan, review critically, execute tasks in batches, run Flutter verifications, report for review between batches.
Core principle: Batch execution with checkpoints for review.
Announce at start: "I'm using the flutter-executing skill to implement this plan."
Read plan file
cat docs/plans/YYYY-MM-DD-<feature>-plan.md
Check dependencies first
cat pubspec.yaml
Install new dependencies if needed
flutter pub get
Review critically:
If concerns: Raise them before starting
If no concerns: Create TodoWrite and proceed
Default: First 3 tasks
For each task:
flutter analyze lib/features/<feature>/
git add <files>
git commit -m "<conventional commit message>"
After completing 3 tasks, run full verification:
# Static analysis
flutter analyze
# Expected: No issues found!
# Run tests (if test files exist)
flutter test test/features/<feature>/
# Expected: All tests passed!
# Quick build check (optional)
flutter build apk --debug --target-platform android-arm64
# Expected: Built successfully
When batch complete, report:
## Batch N Complete
**Tasks completed:**
1. ✅ Task 1: [description]
2. ✅ Task 2: [description]
3. ✅ Task 3: [description]
**Verification:**
- flutter analyze: No issues found
- flutter test: X/X passed
**Files created/modified:**
- lib/features/.../entity.dart
- lib/features/.../repository.dart
- ...
**Ready for feedback.**
Based on feedback:
After all tasks complete and verified:
Run final verification:
flutter analyze
flutter test
flutter build apk --debug # or ios
Announce: "I'm using the flutter-finishing skill to complete this work."
REQUIRED SUB-SKILL: Use flutter-craft:flutter-finishing
| Stage | Command | Expected Output |
|---|---|---|
| Per-file | flutter analyze lib/path/file.dart | No issues found |
| Per-batch | flutter analyze lib/features/<feature>/ | No issues found |
| Test | flutter test test/features/<feature>/ | All tests passed |
| Final | flutter build apk --debug | Built successfully |
STOP executing immediately when:
flutter analyze shows errors (not just warnings)Ask for clarification rather than guessing.
Before executing, verify plan follows this order:
1. Domain Layer tasks first
├── Entities
├── Repository interfaces
└── UseCases
2. Data Layer tasks second
├── Models
├── DataSources
└── Repository implementations
3. Presentation Layer tasks third
├── State Management
├── Widgets
└── Screens
4. Test tasks after implementation
├── Repository tests (priority 1)
├── State tests (priority 2)
└── Widget tests (priority 3)
If plan doesn't follow this order, raise concern before starting.
After EACH batch, you MUST invoke: → flutter-craft:flutter-verification (verify before continuing)
You MUST invoke: → flutter-craft:flutter-finishing (present completion options)
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.