gsd-plant-seed

Capture forward-looking ideas into structured markdown seed files with milestone metadata.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-plant-seed-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plant-seed
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-plant-seed
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-plant-seed-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects and product teams lose valuable long-term ideas to context rot when they are noted briefly and never revisited; this Skill captures those ideas with the full rationale and scheduling metadata so they resurface at the appropriate milestone.

Core Features & Use Cases

  • Structured Idea Capture: Save an idea with WHY, WHEN (trigger milestone), acceptance notes, and breadcrumbs to deeper references.
  • Persistent Seed Files: Automatically creates a markdown seed under .planning/seeds/ (SEED-NNN-slug.md) that preserves context and links.
  • Milestone Integration: Designed to be consumed by milestone scanners (e.g., /gsd-new-milestone) so matching seeds are presented when relevant.
  • Use Case: During backlog grooming, record a cross-team architectural idea as a seed to surface at the next quarterly architecture review along with links to related docs.

Quick Start

Plant a seed capturing the idea, the WHY, the trigger milestone (for example "Q3 roadmap review"), acceptance criteria, and reference links so the workflow creates the seed file and it will surface at the specified 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 deferred product ideas so they resurface at the right roadmap milestone?

Capturing deferred ideas requires recording the rationale, trigger milestone, and reference links into a structured seed file. This markdown file is stored under .planning/seeds/ to automatically resurface during sprint planning or roadmap reviews.

What is the best way to prevent context rot for long-term project planning ideas?

Preventing context rot involves scheduling forward-looking ideas with full context and trigger metadata. By creating persistent seed files, the original rationale and breadcrumbs are preserved until automatically presented at the appropriate milestone.

How do I schedule a backlog grooming idea to appear at a specific sprint planning gate?

Scheduling a backlog idea involves defining a trigger milestone, acceptance notes, and breadcrumbs when planting a seed. The workflow creates a markdown file that integrates with milestone scanners to present the idea at the specified sprint gate.

Can I use markdown files to preserve architectural rationale until a quarterly review?

Yes, you can use markdown seed files to preserve architectural rationale until a quarterly review. The file captures the WHY, WHEN, and reference links, ensuring the full context is maintained and integrated with milestone scanners for presentation.

Does scheduling deferred ideas require a specific project workflow environment?

Scheduling deferred ideas is applicable to standard product and project workflows without strict dependencies. It requires creating structured markdown seed files in a .planning/seeds/ directory and integrates with milestone scanners like gsd-new-milestone for automatic presentation.

When should I not use scheduled seed files for idea capture in project planning?

Scheduled seed files should not be used for immediate action items or ideas lacking a clear future trigger milestone. They are designed specifically for forward-looking concepts that need to be deferred and automatically resurfaced at later roadmap reviews or release gates.