gsd-plant-seed

Capture forward-looking ideas with trigger conditions into milestone-scanned seed files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Forward-looking ideas often get lost as one-line notes in a deferred list that nobody revisits. This Skill preserves the full context of an idea—why it matters, when it should resurface, and where to find details—so it automatically appears when the right project milestone arrives. ## Core Features & Use Cases - Seed File Creation: Writes a structured seed file to .planning/seeds/SEED-NNN-slug.md capturing the idea summary, rationale, and trigger conditions. - Milestone-Based Resurfacing: Seeds are scanned by the /gsd-new-milestone workflow, which presents matching ideas when a new milestone begins. - Context Preservation: Stores the full WHY, WHEN, and breadcrumbs instead of a bare one-liner, preventing context rot over long projects. - Use Case: During a sprint you realize the codebase needs a plugin architecture, but it is out of scope. Plant a seed with the trigger condition "when the extension API milestone starts" so the idea resurfaces with full context at planning time. ## Quick Start Ask the assistant to plant a seed for your idea, for example: plant a seed for adding a plugin architecture that should surface when the extension API milestone begins.

Frequently Asked Questions about gsd-plant-seed

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

FAQPage Schema
How do I save a project idea for a future milestone?▼

Invoke the skill with a short idea summary, and it creates a seed file in .planning/seeds/ containing the full rationale, trigger conditions, and reference breadcrumbs. The idea then resurfaces automatically when the matching milestone starts.

How do deferred ideas resurface at the right milestone?▼

The /gsd-new-milestone workflow scans the .planning/seeds/ directory and presents seeds whose trigger conditions match the new milestone. This replaces manual backlog reviews with automatic, context-rich surfacing.

What information does a seed file contain?▼

Each seed file stores the idea summary, the full WHY behind it, WHEN it should surface (trigger conditions), and breadcrumbs pointing to relevant details. Files follow the naming pattern SEED-NNN-slug.md under .planning/seeds/.

When should I use a seed instead of a backlog task?▼

Use a seed when an idea is too large or premature for the current scope but tied to a specific future milestone. Backlog tasks suit actionable near-term work, while seeds preserve long-term ideas with their full context and trigger conditions.