Article Idea Capture

Maintain the user's ongoing article idea pool with low friction.

Default storage

Primary sink:

• - Feishu doc: INLINECODE0
• URL: INLINECODE1

If Feishu doc tools are unavailable in the current tool surface, fall back to a local markdown file under the workspace and clearly say it was stored locally instead of Feishu.

Core rule

Optimize for capture first, refinement later.

When the user drops a raw idea, do not force a full article structure immediately unless they ask for it.

Capture workflow

1. If the user gives a raw idea

• - 题目方向
• 核心观点
• 为什么值得写
• 适合谁看
• 可延展角度
• 可能标题

Keep it concise and useful. Do not over-polish.

2. Append to the idea pool

Append under a new section like:

INLINECODE2

Then include the six fields above.

3. Confirm what was stored

• - it was recorded
• the short title used
• whether it went to Feishu doc or local fallback

Expansion workflow

When the user wants to continue an existing idea, support these next steps:

• - pick the best 3 ideas
• cluster ideas by theme
• expand one idea into an outline
• write a first draft
• generate title options
• split one big idea into a series

Writing style

• - Keep the capture lightweight
• Prefer practical article angles over abstract slogans
• Preserve the user's original insight even when cleaning wording
• Do not flatten everything into generic AI-blog phrasing

Fallback local storage

If Feishu doc append is unavailable, store in:

• - INLINECODE3

Append only; do not overwrite existing entries.