The Cabbage Bath: My Method for an Ultimate Stovetop Chicken Breast
A one-pan chicken breast method that uses a mountain of cabbage and onions as an edible lid, creating juicy chicken and a deeply flavored vegetable side.
Read articleNotebook
Writing develops an argument. Prompts define assignments. Series put those assignments in working order. Loops sustain progress. Skills carry a method into the next problem. Quotes keep the sharpest ideas close.
From the notebook
A few recent entries from across the notebook, kept distinct enough to remain useful.
A one-pan chicken breast method that uses a mountain of cabbage and onions as an edible lid, creating juicy chicken and a deeply flavored vegetable side.
Read articleA product-quality loop that turns a business logic or product contract document into an evidence-backed implementation audit.
Open loopRead quoteDo you want to give it all away, or keep enough to keep building?
Read
Arguments, postmortems, technical notes, and ideas worked through in public.
Why stopping at 2 RIR can preserve strength and muscle gains while reducing fatigue—and where training to failure still belongs.
GTM may become almost entirely automated inside companies, but fragmented markets, human behavior, and competitive secrecy will keep the commercial layer alive.
My practical division of labor for AI tools: Grok for browser-centered exploration and Codex for grounded work inside a repository.
Logs, metrics, traces, and release context give agents a queryable account of production that browser checks and source code cannot provide alone.
Use
Use focused Codex assignments, fixed prompt workflows, or orchestrators that coordinate prompt series.
A graph-engineered series orchestrator with parallel evidence frontiers, isolated workers, independent skeptics, merger nodes, human gates, and durable cross-series state.
A workflow-observation prompt for mapping manual processes, templates, scripts, services, alternatives, and the reasons people may keep them.
A bounded competitor-observation prompt that records documented workflows, pricing, changes, incidents, limitations, and tradeoffs without feature-checklist theater.
A repository-grounding prompt that defines what the product demonstrably does, its apparent job, and the evidence ceiling for no-contact research.
A production-linked series orchestrator that routes observational intelligence, product development, and GTM through one gated, resumable operating loop.
A local synthesis prompt that unifies no-contact research streams into an atomic, deduplicated ledger while preserving source kind, directness, conflicts, and bias.
An evidence-capped ranking prompt that nominates no more than three public problem patterns for Product feedback without authorizing roadmap work.
A pattern-synthesis prompt that groups traceable observations by actor, situation, job, failed outcome, and workaround while testing rival explanations.
A contract-led verification prompt for proving the delivered increment across behavior, business rules, permissions, failure paths, tests, and declared quality bars.
An enablement prompt for preparing onboarding, in-product guidance, documentation, support, sales, and customer communication around an accepted product outcome.
A cycle-closing prompt that combines product outcomes, friction, commercial evidence, quality, and cost into one expand, iterate, maintain, rollback, retire, or rediscover decision.
An evidence-synthesis prompt for testing a defined product problem against authorized research, behavior, support, technical reality, and the fastest remaining discovery tests.
A diagnosis prompt for separating defects, discoverability, comprehension, workflow mismatch, missing value, and rollout failure before prescribing the next fix.
A repository-aware planning prompt that maps a contracted increment onto current architecture, dependencies, tests, migrations, observability, rollout, and rollback.
A contract-authoring prompt for converting one solution shape into explicit product behavior, business rules, permissions, non-goals, quality bars, and measurable acceptance.
A bounded implementation prompt for delivering one contracted increment, maintaining a requirement ledger, preserving unrelated work, and verifying every changed behavior.
An evidence-weighted prompt for choosing which product opportunity deserves attention without turning request volume, executive preference, or one large account into priority.
An outcome-review prompt for comparing mature, authorized post-release evidence with the original baseline, target behavior, customer result, and delivery cost.
A problem-framing prompt for turning one prioritized opportunity into a bounded user, context, failed outcome, baseline, and falsifiable product problem.
A release-gate prompt for deciding whether an accepted increment can be exposed safely given operational, migration, security, accessibility, support, and rollback evidence.
A read-only observation prompt for reconstructing which approved rollout stages actually happened, who approved them, who was exposed, and where execution diverged from plan.
A constrained rollout prompt for converting a release decision into cohorts, exposure stages, migrations, monitoring, human ownership, stop conditions, and rollback actions.
A solution-shaping prompt for comparing materially different product approaches against the problem, current architecture, risk, reversibility, and measurable outcome.
A policy-authoring prompt that bounds passive public research by source access, privacy, sampling, data minimization, and no-contact rules.
A source-discovery prompt for choosing a small, contrasting portfolio of public behavior, experience, search, workaround, and category evidence.
A no-contact mining prompt that separates public statements, reproducible behavior, requests, duplicates, counterevidence, and platform bias.
A bounded observation prompt for recording public problem language, desired outcomes, comparisons, and questions without turning search visibility into demand.
A reasoning prompt that uses explicitly assumed scenarios to challenge observational patterns, expose edge cases, and design falsification probes without fabricating feedback.
A capacity-constrained planning prompt for choosing at most three beachhead channels, specifying assets and commitments, and refusing omnichannel theater.
A pre-registration prompt for testing acquisition channels on the same beachhead commitment, with fully loaded cost and kill rules, without declaring winners from imagined results.
A founder-led deal playbook prompt covering discovery, a truthful demo, negotiation with walk-away conditions, and close or loss codes.
An operating-design prompt for activation, time-to-value, the implementation path, support boundaries, and onboarding capacity the sales motion cannot outrun.
A planning prompt for the path from first recognition to a commitment-bearing conversation, with landing surfaces, sequences, and qualification that can fail.
A measurement-design prompt for the few commercial metrics that can change a decision, with formulas, sources, and an honest unknown when the instrument does not exist.
A system-design prompt for pipeline entry, qualification that can fail, and stages that move only on evidence, counting purchasing units instead of CRM theater.
An evidence-capped prompt for turning an ICP, market audit, and position into a pricing unit, defensible bounds, and packages that sell the beachhead job without invented willingness to pay.
A diagnosis prompt for the actual commercial path and its constraint, with at most three handoff fixes and a bias against adding meetings, tools, or roles.
A synthesis prompt that turns current-product, customer, usage, support, commercial, and bounded public evidence into product input without letting volume capture the roadmap.
An operating-design prompt for retention at the product’s natural cadence, renewal without silent discounts, and expansion only along evidenced jobs.
An authoring prompt for the smallest playbook, pitch, proof appendix, and objection cards that stay inside the position and the evidence ceiling.
An architecture prompt for the minimum GTM stack, one source of truth per object, and an explicit list of tools not to buy yet.
An evidence-capped prompt for turning an ICP hypothesis, and a market audit when it exists, into one comparison, one retrieval noun, and a message hierarchy whose public claims cannot outrun the proof.
A weather-aware prompt that favors cloudy, post-rain conditions while weighing the full remainder of the day to choose one exact departure time.
A founder-led prompt for turning an ICP and market audit into a 30-day validation sprint with qualified accounts, commitment-bearing pilots, and decision gates.
A portable prompt workflow that infers a codebase-supported ICP, audits its market, and prepares a 30-day validation sprint while preserving earlier artifacts.
A bottom-up market-audit prompt for turning a completed ICP into a reproducible account census, economic model, reachable prospect universe, and capacity-constrained market decision.
An autonomous, evidence-backed prompt for reconstructing an implemented product’s strongest initial Ideal Customer Profile from its codebase.
An evidence-weighted prompt for updating a codebase-derived ICP with completed customer-discovery interviews while preserving contradictions and uncertainty.
An evidence-disciplined prompt for updating an interview-supported ICP with paid-pilot data across payment, activation, realized value, delivery cost, and repeatability.
An evidence-led prompt for promoting ICP v0.3 only when activation, customer value, retention, repeatability, and unit economics support it.
Play
Paginate through an ordered operating playlist instead of picking prompts from a pile.
A twenty-prompt playlist for owning the commercial engine from ICP through positioning, demand, sales, onboarding, and revenue operations.
A twelve-prompt no-contact playlist for turning public behavior, language, alternatives, experience reports, and category change into bounded product input without inventing customer certainty.
A sixteen-prompt playlist for turning customer and product evidence into a prioritized problem, a contracted increment, verified delivery, a controlled release, and the next product decision.
Install
Open, reusable capabilities with public source and direct Codex installation prompts.
Turn prior coding outcomes into better next actions instead of merely retaining them as memory.
Memory answers what happened. Intuition asks what those outcomes imply here, what is materially different now, and why the next move should work when a similar one did not.
Open skillRun
Small operating systems for making progress, measuring it, and continuing with discipline.
A visibility loop for improving technical SEO, answer readiness, and AI-search coverage through repeated audits and benchmarks.
A refactoring loop for improving architecture through small, live-tested, independently reviewed checkpoints.
A speed loop for local sites where the target is strict enough to force measurement discipline.
Remember
Lines and fragments worth keeping close when judgment needs a shorter form.
Anger may seem to be a source of energy, but it’s blind. It causes us to lose our restraint. It may stir courage, but again it’s blind courage. Negative emotions, which often arise from a spontaneous impulse, cannot be justified by reason, whereas positive emotions can. Scientists suggest that constant anger and hatred undermine our immune system. Compassion, bringing inner strength, is good for our health.
A reminder that anger can feel energizing while eroding restraint, and that compassion offers a steadier form of strength.
Read quoteDo not build an identity around being right. Build a method that becomes stronger each time you are wrong.
A reminder to let error improve the process instead of threaten the self.
Read quoteThe measure of progress is not how powerful the future becomes, but whether the lives already here become better along the way.
A standard for judging progress by whether it improves lives in the present, not only by the power it promises for the future.
Read quoteYour mistakes are evidence of where you've been—not a verdict on who you are.
A reminder that past failures describe history, not identity.
Read quote