gsd:plant-seed
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
Profile →npx skills add davepoon/buildwithclaude --skill plant-seed --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<objective> Capture an idea that's too big for now but should surface automatically when the right milestone arrives. Seeds solve context rot: instead of a one-liner in Deferred that nobody reads, a seed preserves the full WHY, WHEN to surface, and breadcrumbs to details. Creates: .planning/seeds/SEED-NNN-slug.md Consumed by: /gsd:new-milestone (scans seeds and presents matches) </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/plant-seed.md </execution_context> <process> Execute the plant-seed workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/plant-seed.md end-to-end. </process>
What does the gsd:plant-seed skill do?
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill plant-seed --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.