One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-plant-seed-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plant-seed
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-plant-seed
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-plant-seed-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture forward-looking ideas that are too large for immediate action and surface them automatically when the right milestone arrives, preventing context rot.

Core Features & Use Cases

  • Seeds ideas with full context, WHY, WHEN to surface, and breadcrumbs to details.
  • Creates: .planning/seeds/SEED-NNN-slug.md and is consumed by gsd-new-milestone (scans seeds and presents matches).
  • Supports integration with planning and milestone-review workflows to maintain evergreen context.

Quick Start

Provide an idea summary and run the plant-seed workflow to create a seed file in .planning/seeds.

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 forward-looking product ideas for future milestones without losing context?

You capture forward-looking product ideas by creating Markdown seed files that store full context, WHY, and WHEN to surface them. These seeds are preserved at .planning/seeds/SEED-NNN-slug.md to prevent context rot until the right milestone arrives.

How does a seed workflow surface ideas automatically when a milestone is reached?

The seed workflow surfaces ideas by integrating with the gsd-new-milestone workflow, which scans existing seed files and automatically presents matches when a milestone is reached. This preserves evergreen context for product planning.

When should I use a seed file instead of immediately acting on a product idea?

Use a seed file when you have forward-looking ideas that are too large for immediate action. Planting a seed preserves the idea's context and breadcrumbs, ensuring it surfaces automatically during future milestone reviews.

What information do I need to provide to start planting seeds for product planning?

To start planting seeds, provide an idea summary. The workflow takes this input and creates a structured Markdown seed file at .planning/seeds/SEED-NNN-slug.md, capturing WHY and WHEN details for future milestone integration.

Can I integrate planted seeds with existing planning and milestone-review workflows?

Yes, planted seeds support integration with planning and milestone-review workflows. The created seed files are consumed by the gsd-new-milestone workflow to maintain evergreen context across teams and projects.

What is the best way to manage long-term strategy ideas across multiple teams?

The best way to manage long-term strategy ideas is planting them as structured Markdown seeds. This applies to workflows across teams and projects, preserving context with breadcrumbs until the correct milestone triggers automatic surfacing.