| name | write-technical-book |
| description | Complete workflow for writing and publishing a technical book, from crafting a compelling proposal through building a detailed outline, writing and revising the manuscript, conducting technical review, and navigating the publishing process for both traditional and self-publishing paths.
Use when the user wants to write technical book or needs a structured multi-step process for this goal.
Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance. |
| license | Apache-2.0 |
| type | workflow |
| skills | book-proposal-writer book-outliner non-fiction-author developmental-editor self-publishing-guide |
| trigger_phrases | I want to write a technical book write a programming book technical book proposal publish a tech book write a book about software author a technical guide book about technology |
| metadata | {"author":"foundry-skills","version":"1.0.0","tags":"writing content-marketing career step-by-step planning","category":"career","depends":"book-proposal-writer book-outliner non-fiction-author developmental-editor self-publishing-guide"} |
Write Technical Book
Estimated time: 6-12 months
This workflow guides technical professionals through writing and publishing a
technical book. Technical books are distinct from other nonfiction -- they
require code examples that work, explanations that teach, and content that
remains relevant despite rapidly changing technology. A well-executed technical
book can establish you as a definitive authority in your field, generate
passive income, and create career opportunities for years.
The workflow covers the unique challenges of technical authoring: writing a
proposal that publishers care about, structuring content for progressive
learning, balancing depth with accessibility, managing code examples and
technical accuracy, and choosing between traditional publishers (O'Reilly,
Manning, Pragmatic) and self-publishing.
By the end of this workflow you will have: a polished book proposal, a
detailed chapter outline, a complete manuscript, technically reviewed content,
and a published technical book.
When to Use
- User wants to write technical book
- User needs a structured, step-by-step process for write technical book
- User wants to write a technical book
- write a programming book
- technical book proposal
- Do NOT use when: the request is outside the scope of write technical book or requires professional advice beyond educational guidance
- Do NOT use for single-step tasks that one atomic skill can handle independently
Prerequisites
Before starting this workflow, ensure:
- Deep expertise in the technical subject (at least 3-5 years of hands-on experience)
- Some existing content (blog posts, talks, tutorials) that demonstrates your ability to teach
- Dedicated writing time (10-15 hours per week for 6-12 months)
- A working development environment for creating and testing code examples
- Clarity on your target reader and their skill level
Steps
Step 1: Craft Your Book Proposal (uses: book-proposal-writer)
create a compelling book proposal. Even
if you plan to self-publish, the proposal process forces the discipline of
thinking through audience, market, and differentiation.
- Input: technical expertise and the subject they want to write about, Target audience and their current skill level, Competing books in the space (what already exists)
- Output: Complete proposal document with all required sections, One fully written chapter demonstrating style and depth, Competitive landscape with differentiation strategy
- Key focus: Book concept refinement: what specific angle or approach makes this book
Step 2: Build Your Detailed Outline (uses: book-outliner)
