plant-seed

# Plant Seed Skill ## Overview Capture forward-looking ideas with trigger conditions so they resurface at the right time. Seeds carry WHY (rationale) and WHEN (trigger), making them far more valuable than bare TODO comments. Seeds are stored locally in `.seeds/` (gitignored) and automatically surfaced during feature-lifecycle design phase when their trigger conditions match. This workflow is designed for deferred ideas only — if the user describes work that should happen now, suggest creating a task or issue instead. --- ## Instructions ### Phase 1: CAPTURE **Goal**: Gather the idea, trigger condition, scope, and rationale from the user. **Key Constraint**: This skill captures deferred ideas only. If the user describes something that should happen in the current session, suggest creating a task or issue instead. Planting a seed for immediate work means it never gets surfaced — it just gets forgotten in a different way. **Step 1: Understand the idea** Extract from the user's description: - **What** (action): The specific thing to do when the time is right - **Why** (rationale): The insight or observation that motivates this idea - **When** (trigger): A human-readable string describing when this becomes relevant If the user provides all three, proceed. If any are missing, ask: For missing **trigger condition**: > When should this idea resurface? Describe the condition, e.g.: > - "when we add user accounts" > - "when performance optimization is needed" > - "when the ...