القائمة
The drum sounds. Bear and Bloodhound gather for safe migration. Use when migrating anything that requires both careful movement and codebase understanding.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | gathering-migration |
| description | The drum sounds. Bear and Bloodhound gather for safe migration. Use when migrating anything that requires both careful movement and codebase understanding. |
The drum echoes through the valleys. The conductor stands at the pass, orchestrating two very different strengths. The Bloodhound arrives first with fresh eyes — no assumptions about what's connected, just a nose for dependencies. Then the Bear wakes, receiving a map it didn't draw — no shortcuts, no "I already know where things are." Together they move mountains safely, each with isolated context, each trusting only what it verified itself.
IMPORTANT: This gathering is a conductor. It never scouts or migrates directly. It dispatches subagents — one per animal — each with isolated context and an intentional model. The conductor only manages handoffs and gate checks.
SUMMON → DISPATCH → GATE → DISPATCH → GATE → VERIFY
↓ ↓ ↓ ↓ ↓ ↓
Spec Bloodhound Check Bear Check Final
(self) (haiku) ✓ (opus) ✓ Verify
| Order | Animal | Model | Role | Fresh Eyes? |
|---|---|---|---|---|
| 1 | 🐕 Bloodhound | haiku | Scout dependencies, map territory | Yes — sees only the migration spec |
| 2 | 🐻 Bear | opus | Execute migration safely | Yes — sees only territory map, not scouting process |
Reference: Load references/conductor-dispatch.md for exact subagent prompts and handoff formats
The drum sounds. The valley listens...
The conductor receives the migration request and prepares the dispatch plan:
Clarify the Migration:
Determine the Bear's domain guide:
| Migration Type | Domain Guide |
|---|---|
| Database schema, tables, D1/SQLite | domain-database.md |
| Component props, API upgrades, imports | domain-components.md |
| Icons, assets, documents, file formats | domain-content.md |
| Config, conventions, dependencies | domain-general.md |
Confirm with the human, then proceed.
Output: Migration specification, domain guide identified, dispatch plan confirmed.
The conductor signals. The Bloodhound puts its nose to the ground...
Agent(bloodhound, model: haiku)
Input: migration specification only
Reads: bloodhound-scout/SKILL.md (MANDATORY)
Output: territory map
Dispatch a haiku subagent to scout the codebase. The Bloodhound receives ONLY the migration specification — no pre-analysis, no assumptions. It reads its own skill file and executes its full SCENT → TRACK → HUNT → REPORT → RETURN workflow.
What the Bloodhound maps:
Handoff to conductor: Territory map (affected files, dependency graph, edge cases, current state counts, risk assessment).
Gate check: Territory map has: file lists, dependency relationships, item counts, edge cases identified. If incomplete, resume Bloodhound with specific questions.
The Bear wakes. It receives a map it didn't draw...
Agent(bear, model: opus)
Input: migration spec + territory map (from Bloodhound)
Reads: bear-migrate/SKILL.md + references/{domain-guide} (MANDATORY)
Output: migration results + file list
Dispatch an opus subagent to execute the migration. The Bear receives the spec and the Bloodhound's territory map — NOT the Bloodhound's scouting process, just its structured output.
What the Bear does:
Handoff to conductor: Migration results (items migrated, items skipped, validation reports), file list.
Gate check:
pnpm install
gw dev ci --affected --fail-fast --diagnose
Must compile and pass. If it fails, resume Bear with the error.
The journey ends. The conductor confirms safe arrival...
Validation Checklist:
gw dev ci --affected)Completion Report:
🌲 GATHERING MIGRATION COMPLETE
Migration: [Description]
DISPATCH LOG
🐕 Bloodhound (haiku) — [territory mapped, X files identified, Y dependencies found]
🐻 Bear (opus) — [Z items migrated, domain guide: {guide}]
GATE LOG
After Bloodhound: ✅ territory map complete
After Bear: ✅ compiles clean, migration verified
Final CI: ✅ gw dev ci --affected passes
MIGRATION RESULTS
Items migrated: [count]
Items skipped: [count, reason]
Item count match: ✅ [source] = [dest]
Integrity checks: ✅
Rollback: [branch/backup location]
Everything found its new home.
The conductor dispatches. It does not scout dependencies or execute migrations.
The Bear receives the territory map, not the Bloodhound's scouting process. It trusts the map but verifies what it finds during migration.
Territory map must be complete before Bear starts. CI must pass after Bear finishes.
If a gate check fails, resume the failing agent. The Bear especially benefits from resumption — it has the migration context and can fix issues faster than starting fresh.
The conductor does NOT:
| Migration Scope | Strategy |
|---|---|
| Simple rename (< 5 files) | Bear only (no Bloodhound needed) |
| Cross-cutting migration (5-50 files) | Standard: Bloodhound → Bear |
| Large migration (50+ files) | Bloodhound → Bear with chunked execution |
| Unknown scope ("migrate X") | Always start with Bloodhound |
When no single animal suffices, the gathering answers. 🌲🐾
Move mountains with patient strength. Wake from hibernation, gather what must move, carry it carefully, hibernate to verify, and wake again to confirm. Use when migrating anything — data, components, icons, documents, formats, or systems.
Gather scattered ideas into organized GitHub issues. The bee collects pollen from every flower, checks if the hive already has it, and carefully deposits new work in the comb for later. Never edits code—only organizes the work ahead. Use when creating issues from TODOs or planning work.
Better Auth framework reference — configuration, security, rate limiting, sessions, plugins, and production hardening. Use when configuring Better Auth, auditing auth security, adding plugins, or troubleshooting Heartwood.
Build multi-file features with unstoppable momentum. Trumpet the vision, gather materials, construct with strength, test thoroughly, and celebrate completion. Use when implementing features that span multiple files or systems.
Make your invisible work visible. The firefly drifts through your git history, gathers what you shipped into stories, glows them into human words, and helps you share them with the world. Use when you need patch notes, posts, or just want to see what you built.
The drum sounds. Hummingbird, Squirrel, Firefly, and Wren gather for a complete growth cycle — from finding opportunities to shipping findable content. Use when you want to plan and execute your content-to-discovery pipeline in one focused session.