gsd-plant-seed

Capture large ideas with trigger conditions and surface them at milestones.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-plant-seed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plant-seed
Source: https://github.com/onelee85/my-skills/tree/main/gsd-plant-seed
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-plant-seed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seeds are large and nebulous ideas that often fail to surface at the right moment. This skill preserves the rationale, timing, and breadcrumbs so they can be retrieved when needed.

Core Features & Use Cases

  • Capture forward-looking seeds with trigger conditions that specify when to surface.
  • Persist context, rationale, and breadcrumbs for future reference.
  • Use case: when planning a roadmap, seed ideas that should surface at the next major milestone.

Quick Start

Describe the seed with its trigger and context to enable automatic surfacing at the milestone.

Frequently Asked Questions about gsd-plant-seed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture product roadmap ideas to surface at future milestones?

To capture product roadmap ideas, you define the seed with its trigger conditions and context. The skill stores these seeds under .planning/seeds and automatically surfaces them when the specified milestone is reached.

What is the best way to preserve context for forward-looking project plans?

The best way to preserve context for project plans is to capture the rationale, timing, and breadcrumbs as a seed. This ensures the full context is automatically retrieved for review and decision-making when a milestone triggers.

How do I manage seed ideas that are too large for immediate action in product management?

To manage seed ideas too large for immediate action, you capture them with specific trigger conditions. The system persists the context and automatically surfaces the seed at the appropriate milestone for evaluation.

Does this workflow require a specific file format for storing idea seeds?

Yes, the workflow requires a SKILL.md with name and description frontmatter. It stores captured seeds as markdown files under the .planning/seeds directory using the SEED-NNN-slug.md naming convention.

When should I not use automatic seed surfacing for project planning?

You should not use automatic seed surfacing for immediate action items or small ideas. It is specifically designed for large, nebulous ideas that require context preservation and need to trigger review at future milestones.