Menu
诊断并激活长期停滞的项目文档。Use when: (1) 项目状态为 active 但周记录/里程碑/工作日志大面积空白， (2) 项目已进行多周但文档未更新，(3) 用户感到"做了很多但看不到成果"，(4) 项目文档沦为空模板。 核心方法：从已有记录反推补全进展 → 定义阶段性里程碑 → 建立同步闭环。
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | activate-stale-project-doc |
| description | 诊断并激活长期停滞的项目文档。Use when: (1) 项目状态为 active 但周记录/里程碑/工作日志大面积空白， (2) 项目已进行多周但文档未更新，(3) 用户感到"做了很多但看不到成果"，(4) 项目文档沦为空模板。 核心方法：从已有记录反推补全进展 → 定义阶段性里程碑 → 建立同步闭环。 |
| author | Claude Code |
| version | 1.0.0 |
| date | "2026-04-29T00:00:00.000Z" |
项目文档沦为"空壳"：状态是 active，但周记录全空、里程碑是模板占位符、工作日志只有 onboarding 第一天。用户每天都在工作，但由于文档没有运转起来，无法直观看到累积的进展，产生"出不了成果"的焦虑。
出现以下任意一条即可触发：
{{占位符}} 或未勾选的任务，没有已完成标记快速扫描项目文档的三个核心区域：
已进行 X / Y 周 是否与实际时间匹配？不要从零开始写，而是从用户已有的工作痕迹中提取：
diary/YYYY-MM-DD-weekly.md）：提取每周的关键产出补全优先级：
基于项目剩余时间和目标，将剩余工作拆分为 3-5 个阶段。典型 research intern 的五阶段模板：
| 阶段 | 目标 | 时间 |
|---|---|---|
| M1 熟悉与环境 | 跑通第一个实验，完成 onboarding | W1-W2 |
| M2 数据/框架积累 | 建立评测流程，积累实验数据 | W3-W5 |
| M3 机制深度分析 | 定位瓶颈，产出分析报告 | W6-W7 |
| M4 方案验证 | 实现改进，跑实验，确认指标提升 | W8-W9 |
| M5 成果产出 | 论文/专利/技术报告初稿与交付 | W10+ |
关键原则：
确保日常记录能自动流入项目文档：
/daily-review（或等价的同步命令），自动同步到项目工作日志激活成功的标志：
激活前（ResearchAgent.md）：
{{里程碑1名称}} 占位符激活后：
projects/项目文档模板.md.claude/skills/daily-review/SKILL.mdCapture a multi-step workflow into a timestamped pipeline memory after trial-and-error sessions. The core output is: (1) the final working commands saved as executable scripts (not bare shell commands), and (2) a structured markdown document separating the clean reproducible pipeline from the detours and pitfalls. Timestamped snapshots live in pipeline_memory/; mature pipelines can be promoted to PIPELINE.md and auto-loaded. Fully environment-agnostic — works for any project, any toolset, any domain. Use when the user finishes a multi-step task, says "保存工作流记忆", "save pipeline memory", "记录一下当前进展", or "/save-pipeline-memory". Takes an optional folder path.
Run Claude Code commands (including /insights, /doctor, custom prompts) via system crontab in non-interactive mode. Use when: (1) setting up daily/weekly automated Claude Code tasks, (2) scheduling reports or analysis via cron, (3) running Claude Code with third-party API backends (DeepSeek, Qwen, etc.) in headless environments, (4) "set up a daily report", "automate this in cron", "schedule insights". Covers: cron PATH setup, third-party API env vars for non-interactive mode, nvm/node auto-discovery, and wechat-reminder integration for notification delivery.
Use when the user wants to *learn* or *understand* a technical concept (an algorithm, a math derivation, an ML architecture, a systems internal) rather than just get a one-shot answer — triggers include "explain X", "teach me X", "help me understand X", or being stuck on a concept while reading a paper or code. Probe the user's level with a few questions FIRST, then teach interactively through a runnable Jupyter notebook with LaTeX derivations and small experiments.
Claudeception is a continuous learning system that extracts reusable knowledge from work sessions. Triggers: (1) /claudeception command to review session learnings, (2) "save this as a skill" or "extract a skill from this", (3) "what did we learn?", (4) After any task involving non-obvious debugging, workarounds, or trial-and-error discovery. Creates new Claude Code skills when valuable, reusable knowledge is identified.
Record a debugging session's findings into a timestamped markdown file under debug_experience/. Captures problem, root cause, solution, and key learnings in a structured, reusable format. Use when: you've just resolved a non-obvious bug, found an undocumented edge case, encountered an issue that took multiple attempts to fix, or when you say things like "保存调试经验", "save debug experience", "记录这次调试", "/save-debug-experience". Takes an optional folder path as argument.
MCP Notion工具使用指南，包含常见问题解决方案和最佳实践。使用当： (1) 访问Notion数据库view URL出现"URL type view not currently supported"错误， (2) 需要获取数据库schema和表结构信息， (3) 查询数据库中的条目内容， (4) 创建页面时MULTI_SELECT字段值不存在导致失败， (5) 需要更新数据库schema添加新选项， (6) 开发需要集成Notion数据的自动化工作流， (7) query_data_sources/query-database-view返回Business Plan要求错误， (8) 需要在无Business Plan的情况下枚举数据库所有条目。