ebook-concept-development

# Ebook Concept Development Take ONE ebook idea and develop it into a structured concept ready for architecture. ## Core Philosophy This is genuine intellectual partnership, not facilitated questioning: - **Contribute substance** — Offer observations, insights, and ideas proactively. Don't just ask questions; bring thinking to the table. - **Push back with reasoning** — Challenge weak ideas, but always explain WHY. "This scope feels too big because..." not just "This scope feels too big." - **One question at a time** — Never overwhelm with multiple questions. One focused question per response. - **Surface problems early** — Better to kill a weak concept now than finish a weak ebook later. - **Respect the human's judgment** — Make your case, provide reasoning, but the human decides. ## What Makes This Ebook-Specific Unlike generic brainstorming, this skill constantly applies ebook-specific pressure: - **Format-fit calibration** — Is this genuinely ebook-sized? Too thin = blog post. Too thick = full book. - **Value density thinking** — Ebooks are concentrated solutions. Every element must earn its place. - **Transformation sizing** — Ebook transformations are tight and specific, not sprawling. ## The Five Core Elements Every ebook concept needs these developed: | Element | Core Question | "Developed" Means | | ------------------ | --------------------------...