Idea Trace
by @lakendocean
Don't just save ideas - trace how they mature. Use when a user wants to follow how an important idea was shaped by later conversations, work, projects, and l...
clawhub install idea-traceπ About This Skill
name: idea-trace description: Don't just save ideas - trace how they mature. Use when a user wants to follow how an important idea was shaped by later conversations, work, projects, and lived experience; decide whether it deserves long-term tracking; classify what changed it; and explain how it became a more mature view.
Idea Trace
Don't just save ideas - trace how they mature.
Good ideas rarely arrive complete. They often begin as a vague hunch, then get shaped by later conversations, work, projects, and lived experience. Idea Trace helps you follow that process instead of losing it in daily noise.
AI is making execution cheaper, but genuinely strong ideas are still rare. What is missing is often not more capture, but a way to see how a promising early idea was later shaped into something real.
This is not an idea inbox. It is for following how important ideas evolve.
Before substantive work, read references/taxonomy.md.
If the user wants a formal artifact or asks what the output should look like, also read references/output-shapes.md.
Use This Skill When
Do not use this skill for:
What Good Looks Like
The skill succeeds only when the output makes these questions easy to answer:
Workflow
1. Qualify the object.
- Test whether it is a true core proposition using references/taxonomy.md.
- If it fails, say clearly that it is a fleeting idea, local task thought, or unsupported fragment.
2. Define the proposition spine.
- Capture the earliest seed form, current form, scope, and why it matters.
3. Gather candidate contributions.
- Look across life, work, projects, and dialogue.
- Prefer items that changed definition, boundary, evidence, expression, priority, or operating conditions.
4. Classify shaping roles.
- Label each contribution using the contribution-type taxonomy.
- Reject items that are only adjacent or repetitive.
5. Build the evolution chain.
- Organize by turning points, not raw chronology.
- State what changed at each step and why it mattered.
6. Produce the right artifact.
- Use references/output-shapes.md when the user needs a map, narrative, dossier, or active-line snapshot.
7. Mark confidence honestly.
- Separate confirmed links from inference.
- Mark weak, partial, or speculative connections explicitly.
Core Rules
Trigger Examples
Use this skill for asks like: