| name | daniel-pink-writing-structure |
| description | Daniel Pink's non-fiction writing system — structure discovery before drafting, the proposal-as-stress-test idea validation pipeline, fresh-yet-familiar positioning, research saturation and ruthless inclusion, and the reader-promise contract that makes a book worth $25 and nine hours of a stranger's life. |
| version | 2.0 |
| format | completion-engine |
| workflows | 3 |
| source | claude.ai export 2026-07-01 |
Daniel Pink — Writing & Book Structure
Daniel Pink (Drive, When, The Power of Regret, To Sell Is Human — six NYT bestsellers over 30 years) treats writing as engineering: you are building something that has to work, and you stress-test it like a structure under load. His system runs idea → socialization → 30-40 page proposal-as-test → months of structure hunting → daily word-count production, chapter at a time — and every piece is governed by one question: what is the promise I'm making to the reader, and does every page pay it off?
Available Workflows
| # | Workflow | Produces |
|---|
| 01 | discover-structure | A stress-tested organizing architecture (skeleton) for a book, long article, or content body — 3-4 candidate frameworks tried and broken until one holds |
| 02 | test-book-idea | A kill-or-commit verdict on a book/major-project idea: socialization script, fresh-yet-familiar positioning, and a proposal-grade stress test run BEFORE years get committed |
| 03 | engineer-reader-promise | An explicit reader-promise contract plus a chapter/section payoff audit and engagement-density pacing map for a draft or outline |
Quick Reference
- Structure before sentences. Pink cannot write until he sees the skeleton. Months of research go to finding the organizing principle; drafting starts only after a framework survives staring at the wall.
- The proposal is the test. If an idea can't withstand a 30-page proposal, it can't withstand a 300-page book. And if you hate writing the proposal, you'll hate writing the book. Kill early — 10 days, not a signed contract.
- Fresh yet familiar. The pitch for When: "We have lots of how-to books. We need a when-to book." New enough to matter, recognizable enough to want.
- Socialize ideas. Talk about the idea and read the room: dead eyes vs. questions vs. "I disagree" — all three are data.
- Consilience is the generalist's edge. Different disciplines asking the same question without talking to each other = a book. One obscure paper (green socks) = skepticism; converging piles across fields = include it.
- Ruthless inclusion. Three weeks of research can rightfully become one paragraph. The reader's need decides, not your sunk cost.
- The reader promise. A book costs $25 and nine hours of someone's life. Win = they think differently AND do different stuff. Useful beats merely interesting.
- Routine is liberating. Fixed time, fixed place, daily word count (even 500), no phone, chapter at a time. Consistency over intensity — the tortoise won.
- Write to figure it out. When you don't know what you think, drafting IS the thinking. (Charlie Yarnoff: "Sometimes you have to write to figure it out.")
Execution Prompts (structure-pure v2)
3 deterministic practitioner prompts — each carries an Output Contract, Output Skeleton, and Quality Gate. When a deliverable matches one, Read it and honor its contract instead of improvising the output shape.
- Daniel Pink — Book Idea Stress Test —
skills/daniel-pink-writing-structure/references/prompts-v2/book-idea-stress-test.md
- Daniel Pink — Reader Promise Engineering —
skills/daniel-pink-writing-structure/references/prompts-v2/reader-promise-engineering.md
- Daniel Pink — Structure Discovery —
skills/daniel-pink-writing-structure/references/prompts-v2/structure-discovery.md
