Book Teardown Notes

Problem

When working with a history or decision-logic book, the hard part is often not finding materials, but turning reviews, table-of-contents signals, reader discussions, and chapter notes into a reusable knowledge note. Claims, concepts, practical paths, and reading priorities may be scattered across pages, making manual curation inconsistent and hard to verify.

How It Works

• Input: Accept a book title + author, for example Wu Gu Lu Chang An + author.
• Search: Query title author review summary to collect reviews, summaries, table of contents, and reader feedback; broaden to Douban or Zhihu when needed.
• Confirm: Before writing, list the found title, author, score, and source notes, then proceed after confirmation.
• Breakdown: Produce a structured outline, core claims, key concepts, quote matrix, and a three-step practice path, followed by comparison, potential reasoning limits, reading advice, and extension questions.
• Output: Save the note into the 拆书 folder through the obsidian CLI, using the book title as the file name.

Boundaries

It is best used for history/decision-logic books and as a pre-reading index rather than a substitute for close reading. Search quality depends on external web availability; ambiguous titles, missing authors, or thin results may require manual follow-up. Public search results can be secondhand, so verify important claims and quotations against the original book before citing them.