メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Execute git and GitHub operations with Conventional Commits and agent-safe defaults. Use raw git/gh directly. Use gw only for worktree lifecycle (create/finish). Use when making commits, managing branches, working with PRs/issues, or performing any version control operations.
| name | gathering-growth |
| description | 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. |
The drum echoes across the meadow and into the wider world. Four creatures answer — each one a fresh subagent with its own context and focus. The Hummingbird darts out to find where your people are. The Squirrel takes what's found and builds a calendar. The Firefly drafts the posts in your voice. The Wren checks that everything is findable. The conductor orchestrates, pauses for human checkpoints between each animal, and ensures nothing gets lost in handoff. One session, one complete growth cycle.
/gathering-growthIMPORTANT: This gathering is a conductor with human checkpoints. It dispatches subagents but PAUSES between each animal to check in with you. Your input shapes every phase. This is collaborative, not automated.
SUMMON → SCOUT → ✋ CHECK → PLAN → ✋ CHECK → DRAFT → ✋ CHECK → POLISH → CHORUS
↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
Confirm Hummingbird Human Squirrel Human Firefly Human Wren Summary
scope finds opps review builds review drafts review SEO & next
& pick calendar & refine posts & approve checks steps
| Order | Animal | Model | Role | Handoff Receives |
|---|---|---|---|---|
| 1 | 🌺 Hummingbird | sonnet | Scout opportunities, find where people are | Feature spec + recent work |
| ✋ | Human checkpoint | — | Pick which opportunities to pursue | — |
| 2 | 🐿️ Squirrel | sonnet | Build content calendar from approved opportunities | Approved opportunities + recent firefly output |
| ✋ | Human checkpoint | — | Refine calendar, adjust rhythm, confirm dates | — |
| 3 | ✨ Firefly | sonnet | Draft posts for the highest-priority calendar items | Approved calendar + git log |
| ✋ | Human checkpoint | — | Refine voice, correct facts, approve posts | — |
| 4 | 🐦 Wren | sonnet | SEO-check any pages linked in posts | Approved posts + linked page list |
The drum sounds. The conductor steps into the clearing...
The conductor receives the growth request and prepares:
git log --oneline --since="14 days ago")Output: Scope confirmed, context gathered, ready to dispatch.
The conductor signals. The Hummingbird shoots out of the grove...
Agent(hummingbird, model: sonnet)
Input: Growth scope + recent shipping summary
Reads: hummingbird-pollinate/SKILL.md (MANDATORY)
Output: Opportunity report
Dispatch a sonnet subagent as the Hummingbird. It receives the scope and recent work summary, reads its skill file, and executes the full DART → HOVER → SIP → CARRY workflow.
Handoff to conductor: Opportunity report — communities found, conversations spotted, content ideas, growth experiments to try. Ranked by effort vs. impact.
Gate check: Opportunities identified with at least 3 actionable ideas.
The conductor pauses. Turns to you.
Present the Hummingbird's findings and ask:
Wait for human input. Do NOT proceed until the user has selected which opportunities to pursue. Use AskUserQuestion if helpful.
Output: User-approved opportunities, ready for calendar planning.
The Squirrel scurries into the clearing, nose twitching...
Agent(squirrel, model: sonnet)
Input: Approved opportunities + time horizon + any existing firefly output
Reads: squirrel-plan/SKILL.md (MANDATORY)
Output: Content calendar
Dispatch a sonnet subagent as the Squirrel. It receives the user-approved opportunities and builds a content calendar with specific topics, dates, formats, and effort levels.
Handoff to conductor: Content calendar with items placed in time, effort-tagged, platform-assigned.
Gate check: Calendar exists with at least one item per week in the time horizon.
The conductor pauses again.
Present the Squirrel's calendar and ask:
Wait for human input. The user picks which calendar items to draft in this session.
Optionally push to GitHub Projects:
gh issue create \
--title "Content: [topic]" \
--body "[calendar item details]" \
--label "content"
Output: User-approved calendar, items selected for drafting.
The clearing fills with warm light...
Agent(firefly, model: sonnet)
Input: Selected calendar items + git log for relevant period
Reads: firefly-journal/SKILL.md (MANDATORY)
Output: Draft posts
Dispatch a sonnet subagent as the Firefly. It receives the selected calendar items and reads the git log to understand what was actually built. Executes DRIFT → GATHER → GLOW to produce draft posts.
Note: The Firefly's REFLECT phase is handled by the next human checkpoint — the conductor manages the conversation, not the subagent.
Handoff to conductor: Draft posts for each selected calendar item, sized appropriately (Bluesky post, thread, dev log, etc.).
Gate check: Drafts exist for every selected calendar item.
The conductor holds up the drafts like lanterns...
Present each draft post and ask:
This is the REFLECT phase — the most important checkpoint. The user's corrections make the content authentic.
Iterate if needed: If the user provides corrections, revise the drafts right here. Usually 1-2 rounds.
Output: User-approved posts, ready for findability check.
The Wren hops onto the branch, tilting its head at the pages...
Agent(wren, model: sonnet)
Input: List of pages linked in approved posts + the posts themselves
Reads: wren-optimize/SKILL.md (MANDATORY)
Output: SEO report + fixes for linked pages
Dispatch a sonnet subagent as the Wren. It receives the pages that will be linked in posts and audits their findability — meta tags, OG images, descriptions. If someone clicks through from a Bluesky post, the landing page needs to deliver.
What the Wren checks:
Handoff to conductor: SEO report + any fixes applied.
Gate check: All linked pages have proper meta tags and OG images.
Dawn breaks over the clearing. The conductor surveys the work...
Present the complete growth cycle summary:
## 🌲 GATHERING GROWTH COMPLETE
### Dispatch Log
🌺 Hummingbird — [N opportunities found, M selected]
🐿️ Squirrel — [Calendar built: X items over Y weeks]
✨ Firefly — [N posts drafted, M approved]
🐦 Wren — [N pages audited, M fixes applied]
### Human Checkpoints
After Scout: ✅ [N] opportunities selected
After Plan: ✅ Calendar approved, [N] items for drafting
After Draft: ✅ [N] posts approved
After Polish: ✅ All linked pages findable
### Ready to Post
1. [Post title] — [platform] — [ready / needs screenshot / needs review]
2. [Post title] — ...
### Calendar (Next 2 Weeks)
| Date | Content | Platform | Status |
|------|---------|----------|--------|
### Growth Experiments to Track
- [Experiment from Hummingbird] — try by [date]
### Next Gathering
Suggested: [date] — run `/gathering-growth` again to check what bloomed
Output: Posts ready, calendar set, pages findable, growth experiments tracked.
NEVER skip a checkpoint. NEVER proceed without user input. The whole point is collaborative growth, not automated marketing. If in doubt, ask.
Each animal runs as an isolated subagent. The Hummingbird doesn't see the Wren's work. The Squirrel doesn't see the Firefly's drafts until they're ready. Isolation produces better results.
The conductor is the memory. It carries user decisions, approved items, and corrections from checkpoint to checkpoint. Each subagent gets ONLY what it needs — not the full history.
If the user says "this is enough for today" at any checkpoint, stop the gathering gracefully. Save what's done. The Squirrel can stash the remaining items for next time.
The conductor does NOT:
| Situation | Approach |
|---|---|
| Full monthly planning | All 4 animals, all checkpoints |
| "Just help me post about [thing]" | Skip Hummingbird, start at Squirrel/Firefly |
| "What should I post this week?" | Hummingbird + Squirrel only |
| "I have drafts, just check SEO" | Wren only |
| User runs out of energy mid-gathering | Save state, note what's done, suggest when to resume |
Before: rabbit-inspect — audit first impressions before driving traffic to pages
After: hummingbird-pollinate — track which growth experiments bloomed
Parallel: Individual animals can be invoked standalone anytime
When one animal isn't enough and the grove needs to grow — the gathering answers. 🌲