计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
co-storm【效率与协作】Operate collaborative Co-STORM workflows in knowledge_storm: configure models and retrievers, warm start a shared mind map, step through user/system turns, generate reports, and persist state/logs.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when the task is about collaborative Co-STORM: human-in-the-loop knowledge curation with a warm-started discourse, moderator/multi-expert turn policy, dynamic mind map, final report generation, and state/log export.
Do not use this sub-skill for the non-collaborative STORM article pipeline; route that to sub-skills/storm-wiki. Do not use it for building a VectorRM/Qdrant corpus; route that to sub-skills/vector-corpus unless the caller has already supplied a ready retriever object for CoStormRunner.
pip install knowledge-storm.Encoder during CoStormRunner.__init__, so ENCODER_API_TYPE and the matching embedding credentials must be set before runner construction.bing, you, brave, serper, duckduckgo, tavily, or searxng.CollaborativeStormLMConfigs, RunnerArgument, LoggingWrapper, retriever, optional callback handler, then CoStormRunner.warm_start() before step(). step() assumes conversation_history is non-empty.step(user_utterance="...")) and system observation (step()), then reorganize the knowledge base and call generate_report().report.md or report.txt, instance_dump.json, and log.json.CollaborativeStormLMConfigs, RunnerArgument, CoStormRunner, callbacks, retrievers, turn policy fields, and output contracts.LoggingWrapper, ConversationTurn, KnowledgeBase, to_dict, from_dict, redaction, and log/state inspection.from_dict caveat, and empty report failures.LitellmModel, supports --topic, --output-dir, --retriever, Co-STORM hyperparameters, --observe-turns, --user-utterance, and --dry-run, and writes report/state/log files. --dry-run performs no LLM or network calls.