跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

ebook-concept-development

Ebook Concept Development

robertguss · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add robertguss/claude-code-toolkit --skill ebook-concept-development

技能说明


name: ebook-concept-development description: Develop ebook ideas into structured concepts ready for architecture. Use when the user has an ebook idea (from a brainstorm document, existing content to repurpose, a book section to extract, or a fresh concept) and wants to develop it into a clear, validated concept. Produces an Ebook Concept Document with reader, transformation, promise, content source, scope/format, and key topics. Handles multi-session development with living documents.

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:

ElementCore Question"Developed" Means
ReaderWho specifically is this for?A specific person, not a category. Their situation, problem, what they've tried.
TransformationWhere before → where after?Concrete states. You can picture the person at each point.
PromiseWhat does the reader get?One compelling sentence. Specific, believable, would make someone pay.
Content SourceWhat existing content feeds this?Clear inventory: original creation, repurposed content, extracted from larger work.
Scope & FormatWhat's the shape?Word count range, format type, platform, what's explicitly OUT.

Situational Elements

Surface these naturally when signals appear — don't force them:

ElementWhen It AppliesSignal Phrases
Value GapCreator-led ebooks (repurposed content)"I have videos on this," "my newsletter covers this," "readers already know my work"
EnemyArgument-driven ebooks"Most people think X but actually Y," "the conventional wisdom is wrong," "I'm pushing back against"

Also Capture

  • Author's intent — Income, authority, audience service, lead generation, passion project
  • Key topics/themes/concepts — Raw ingredients that need a home in the ebook
  • Decisions made — With reasoning, not just conclusions
  • Out of scope — What's explicitly NOT this ebook

Session Flow

Arriving with Material

The human may bring:

  • A single sentence idea
  • A rough paragraph
  • A brainstorm document from Ebook Discovery
  • Existing content to repurpose
  • A section from a larger book to extract

Read the room. For developed material, come in hot with analysis and observations. For thin material, draw out more before engaging deeply.

If the idea isn't cooked enough: "I'm noticing [specific gap]. You have a topic but not a transformation yet. We could work on finding that together, or you might benefit from the Ebook Discovery skill first. What feels right?"

First Response Pattern

After receiving material, provide:

  1. Summary of what you understand the core idea to be
  2. What seems strongest or clearest
  3. What seems fuzzy or underdeveloped
  4. Your initial observations or concerns (with reasoning)
  5. One focused question to start developing

During the Session

Collaboration behaviors:

  • Proactively offer observations: "I notice the transformation you're describing actually has two stages — is this one ebook or two?"
  • Challenge with reasoning: "The scope feels ambitious for ebook format because you're describing three distinct skill-building stages. Am I reading this right?"
  • Surface element connections: "Your reader and your promise seem misaligned — the reader is beginners but the promise assumes they already understand X."
  • Ask the hard questions the human might avoid

Working the elements:

  • Don't march through elements like a checklist
  • Follow the natural flow of conversation
  • Notice when an element gets developed and acknowledge it
  • Circle back to fuzzy elements naturally

Update the document at milestones:

  • When an element moves from fuzzy to developed
  • When a significant decision is made
  • When the scope shifts meaningfully
  • At session end

Returning to Continue

When the human returns with a working document:

  1. Read the document to orient yourself
  2. Provide status summary: current state of each element, what's developed vs. fuzzy, where you left off
  3. Ask where they'd like to f
阅读完整来源 ↗