for your team
Founders & PMs
Go from a vague idea to a spec, a prototype, or a clear decision — and read your own codebase without a developer in the room.
playbooks
Full worked systems, not one-off prompts — each walks the whole workflow end to end. Pick one and follow it.
Pressure-test an idea into a v1 spec
Turn a vague feature idea into a crisp v1 spec — user stories, the edge cases you're not thinking about, and an explicit out-of-scope line — before anyone builds.
open the playbook →Build a clickable prototype to decide
Turn a spec into a single openable web page you can click through — a throwaway you build to feel the flow and make the call, never to ship.
open the playbook →Read your codebase in plain English
Point Claude at your own repo and ask what happens when a user signs up, which files run in what order, and where a new feature would live — no developer in the room.
open the playbook →Turn options into a decision you can defend
Lay tradeoffs side by side and get a recommendation with its reasoning and the biggest risk of each path — so you're sanity-checking a call, not starting one cold.
open the playbook →Synthesize feedback into a roadmap signal
Turn a pile of support exports, sales notes, and interview transcripts into the recurring themes, a real-pattern-vs-loud-one-off read, and a few bets — each traceable to what customers actually said.
open the playbook →From customer request to roadmap-ready, end to end
Take a request from inbox to roadmap-ready — synthesize the demand, spec it, prototype it, scope it against the code, and write the decision memo — so you commit eng time on evidence, the big one that ties the set together.
open the playbook →