name: gsd-plant-seed description: "Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone" argument-hint: "[idea summary]" allowed-tools:
- Read
- Write
- Edit
- Bash
- AskUserQuestion
<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>
<!-- Workflow content (was: plant-seed.md) --> <purpose> Capture a forward-looking idea as a structured seed file with trigger conditions. Seeds auto-surface during /gsd-new-milestone when trigger conditions match the new milestone's scope.Seeds beat deferred items because they:
- Preserve WHY the idea matters (not just WHAT)
- Define WHEN to surface (trigger conditions, not manual scanning)
- Track breadcrumbs (code references, related decisions)
- Auto-present at the right time via new-milestone scan </purpose>
If empty, ask:
What's the idea? (one sentence)
Store as $IDEA.
</step>
AskUserQuestion(
header: "Trigger",
question: "When should this idea surface? (e.g., 'when we add user accounts', 'next major version', 'when performance becomes a priority')",
options: [] // freeform
)
Store as $TRIGGER.
AskUserQuestion(
header: "Why",
question: "Why does this matter? What problem does it solve or what opportunity does it create?",
options: []
)
Store as $WHY.
AskUserQuestion(
header: "Scope",
question: "How big is this? (rough estimate)",
options: [
{ label: "Small", description: "A few hours — could be a quick task" },
{ label: "Medium", description: "A phase or two — needs planning" },
{ label: "Large", description: "A full milestone — significant effort" }
]
)
Store as $SCOPE.
</step>
# Find files related to the idea keywords
grep -rl "$KEYWORD" --include="*.ts" --include="*.js" --include="*.md" . 2>/dev/null | head -10
Also check:
- Current STATE.md for related decisions
- ROADMAP.md for related phases
- todos/ for related captured ideas
Store relevant file paths as $BREADCRUMBS.
</step>
Generate slug from idea summary. </step>
<step name="write_seed"> Write `.planning/seeds/SEED-{PADDED}-{slug}.md`:---
id: SEED-{PADDED}
status: dormant
planted: {ISO date}
planted_during: {current milestone/phase from STATE.md}
trigger_when: {$TRIGGER}
scope: {$SCOPE}
---
# SEED-{PADDED}: {$IDEA}
## Why This Matters
{$WHY}
## When to Surface
**Trigger:** {$TRIGGER}
This seed should be presented during `/gsd-new-milestone` when the milestone
scope matches any of these conditions:
- {trigger condition 1}
- {trigger condition 2}
## Scope Estimate
**{$SCOPE}** — {elaboration based on scope choice}
## Breadcrumbs
Related code and decisions found in the current codebase:
{list of $BREADCRUMBS with file paths}
## Notes
{any additional context from the current session}
</step>
<step name="commit_seed">
```bash
node "$GSD_TOOLS" commit "docs: plant seed — {$IDEA}" --files .planning/seeds/SEED-{PADDED}-{slug}.md
```
</step>
<step name="confirm">
```
✅ Seed planted: SEED-{PADDED}
"{$IDEA}" Trigger: {$TRIGGER} Scope: {$SCOPE} File: .planning/seeds/SEED-{PADDED}-{slug}.md
This seed will surface automatically when you run /gsd-new-milestone and the milestone scope matches the trigger condition.
</step>
</process>
<success_criteria>
- [ ] Seed file created in .planning/seeds/
- [ ] Frontmatter includes status, trigger, scope
- [ ] Breadcrumbs collected from codebase
- [ ] Committed to git
- [ ] User shown confirmation with trigger info
</success_criteria>
<process>
Execute the plant-seed workflow steps embedded above end-to-end.
</process>