ccf-idea-optimizer
CCF Idea Optimizer
Invocation Controls
CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode and ../ccf-common/references/handoff-modes.md. Use ../ccf-common/references/routing.md to keep idea optimization separate from idea scoring, manuscript writing, paper review, and rebuttal tasks.
Load ../ccf-common/references/task-modes.md before deciding exploratory, quick, or standard mode. Use exploratory mode for rough seeds, repeated direction search, "找方向", "还有没有可做路线", or when the user wants possibility before judgment. Use quick mode for a short idea repair or one local direction note. Use standard mode for mature idea concretization, novelty grounding, or a plan that will feed writing, reviewing, literature search, or experiment design.
If the user says not to use, disable, skip, or avoid a sibling skill, do not invoke or simulate that skill for the rest of the conversation. Use this skill's local fallback instead: compact risk scan, action queue, or next-step note without cross-skill execution.
Do not invent literature, results, baselines, experiments, reviewer reactions, or novelty evidence. Mark unsearched novelty and missing evidence as uncertainty.
Treat rough ideas, unpublished method details, draft abstracts, and experiment plans as private user data. Load ../ccf-common/references/privacy-and-evidence.md before browsing, using private text in a query, or making evidence/provenance claims.
Core Rule
Optimize the research idea before optimizing the writing. Do not inflate novelty, invent related work, invent results, or turn weak ideas into confident claims. Make the idea more CCF-A-ready by sharpening the problem, mechanism, contribution, evidence package, and reviewer-facing risk register. When literature is available, reason through a compact research map of source-backed observations, limitations, mechanism primitives, and protocol anchors instead of treating paper titles or summaries as prompt decoration. For fuzzy ideas, evolve diverse but internally consistent candidate concretizations, retain their lineage, and challenge the strongest route once before finalizing it. Prefer timely, elegant, non-stale directions and clearly mark novelty uncertainty until searched. In exploratory mode, do not kill a seed direction just because it is currently weak or crowded: produce at least one plausible rescue route, narrower problem, venue switch, benchmark/evidence route, or "minimum viable research question" before recommending a pivot. Follow the user's requested output shape: idea card, alternatives, roadmap, questions, table, Chinese explanation, or handoff-ready brief.