Prompt

 Library

A design session for building a sustainable creative practice around full-time employment — not 'just wake up earlier,' but a structured intake that diagnoses your specific failure mode (time scarcity, energy depletion, schedule chaos, or identity friction) and builds a weekly architecture calibrated to your actual life. For writers, musicians, visual artists, and makers who want to keep creating without quitting their job.

For senior and mid-level engineers who pair with stuck juniors and reach for the fix — this diagnoses why the junior is actually stuck (six conceptual failure modes, from hypothesis-free searching to fear paralysis), picks the exact coaching move that matches the failure mode, and names the three senior-engineer instincts that feel helpful but quietly kill debugging fluency. Ends with a script for the first question you should ask in the next five minutes.

A diagnostic coaching protocol for creative blocks — not 'just start' advice, but a three-round process that identifies the specific root cause of your block (fear of judgment, perfectionism, wrong project, undefined audience, emotional avoidance, or unclear next action) and builds a targeted protocol to match. For writers, musicians, designers, filmmakers, and anyone stuck on making something they care about.

A clear-eyed audit for anyone who's built a successful career in the wrong field. Not a motivation boost, not a pivot plan — an honest inventory of the four types of handcuffs (financial, identity, social, temporal), a reality test on each, and a framework for distinguishing 'I'm staying because this is actually right' from 'I'm staying because leaving feels catastrophic.' For mid-career professionals 10-25 years in who wonder if they've optimized their way into a corner.

You've got a technical proposal — microservices migration, new data layer, service rewrite, provider switch — and you need to find where it breaks before your team does. Plays the sharpest skeptic in the room: stress-tests across five dimensions (migration reality, team capability gap, operational load, organizational fit, and the simpler alternative), surfaces which objections are real vs. defended, and helps you either close the holes or scope down to a first step that gets the value without the risk.

Engineers know when a codebase needs a fundamental overhaul. The hard part isn't identifying the problem — it's convincing a VP of Product, CTO, or CFO who has seen too many rewrites turn into multi-year sinkholes. This devil's advocate prompt plays a skeptical but fair business stakeholder and presses your proposal through the five objections every business leader will raise. By the end, you'll have a tighter argument and a structured one-page case you can actually use.