gsd-plant-seed

To capture deferred ideas and surface them at the right planning milestone, create a structured seed file with metadata for trigger conditions and breadcrumbs. This preserves the idea rationale and presents it automatically via milestone scanners when the specified date or event arrives.

Preventing context rot for backlog items in knowledge management requires attaching explicit trigger conditions to your ideas. By creating persistent seed files containing motivation, acceptance criteria, and links to supporting notes, the full context is preserved until the milestone trigger activates.

Yes, you can use custom trigger criteria for surfacing deferred product feature concepts. Seeds support triggers based on dates, events, or custom criteria, ensuring that specific design notes or backlog items are matched and presented by automated scanners when relevant planning milestones are reached.

To record a new seed for a product launch milestone, summarize the idea, specify the milestone trigger, add required context like acceptance criteria, and include links to related research notes. This ensures the team sees the concept again when planning the next release.

Yes, this milestone trigger approach works for both personal planning and team workflows. The seed creation process applies to any planning environment where deferred ideas, backlog items, or design notes must be preserved and surfaced by date, event, or custom criteria.

A limitation of relying on automated milestone scanners is that seeds are only presented when explicit trigger conditions are met. If a date or event trigger is never reached, the preserved idea and its supporting breadcrumbs remain stored under .planning/seeds without automatically surfacing.