How to Set Up OpenCode as Your Product Second Brain (and more)
Hey everyone, ending the week with a roundup of new posts for you... This week we cover the last post of what accidentally turned into a trilogy on how I use AI, plus some other fun weekend reading for you. Enjoy!
Full Posts
How to Set Up OpenCode as Your Product Second Brain
A 30-minute walkthrough for building a working OpenCode setup with slash commands tailored to product work. The guide covers folder structure, context files, and three starter commands: /debate for stress-testing ideas, /okr for reviewing OKRs, and /prd for PRD feedback. The design pattern separates thin command wrappers from full prompts, keeping commands easy to invoke while allowing prompts to be detailed and shareable.
Link Posts
- The B2B Product Leadership Delusion — Jason Knight's survey reveals a consistent gap between how B2B product leaders rate themselves and how their IC PMs rate them across every core responsibility.
- The invention of "classic rock" — Daniel Parris traces how "classic rock" was invented by radio executives chasing advertising demographics, not by music fans debating what deserved the label.
- Learning in the Age of AI — Scott H. Young examines what skills remain worth developing as AI reshapes work, finding that generalists and experienced workers may fare better than specialists and newcomers.
- Don't Outsource Your Love of Music to AI — Liz Pelly argues that letting algorithms tell us what mattered to us means losing our own sense of why it connected.
Don't miss what's next. Subscribe to Elezea:
Share this email: