Seeds are reusable thinking patterns. Use /seed to get suggestions, or browse this reference.
Each seed has:
- Trigger: The situation that activates it
- Pattern: The core insight
- Steps: How to apply it
- Evidence: Where it's proven
Seeds live in the seeds/ directory. Full details for each seed are in their individual files.
| Seed | Trigger Phrase | One-Line Pattern |
|---|---|---|
| Three-Tiered Governance | "We need more structure" | Principles → Protocols → Practices |
| Pace of Understanding | "We need to ship faster" | Understanding IS the work |
| Cost Consciousness | "This is too expensive" | Cost is a design constraint |
| Voice Before Structure | "Fill in this template" | Read philosophy first |
| Liberation Psychology | "Only experts can do this" | Remove barriers to contribution |
| Patient Learning | "I'm overwhelmed" | Methodology prevents rabbit holes |
| Era Architecture | "Plan the next 3 releases" | Group into eras with shared constraints |
| Semantic Clustering | "What does this system do?" | Map by actions, not file paths |
| Context Iceberg | "Too much information" | 4 tiers: tip, waterline, deep, archive |
| Spec-to-Prompt Pipeline | "Let's just build it" | Scout → Spec → Pre-flight → Prompt |
| Portability Tiers | "Will this work elsewhere?" | Classify by dependency depth |
| Agent Workspace | "Multiple agents on this" | Structured shared spaces |
| Handoff Protocol | "You take over from here" | State + Decisions + Questions + Done |
After running /retro, if a pattern emerges:
- Use
templates/seed_template.mdas a starting point - Name the trigger (when to use it)
- Document the steps (how to apply)
- Record the evidence (where it worked)
- Save to
seeds/directory
The best seeds come from real experience, not theory.