Daily Research Review

Core Contract

Treat the review as a personal research-company operating review, not a diary. The review must answer two questions:

1. Did today turn time, AI, papers, code, experiments, and communication into reusable research assets?
2. Did today make the user more like a researcher worth betting on: better at defining problems, testing hypotheses, building systems, and judging direction?

Default language is Chinese. Use English terms when they are the natural technical labels.

Also use chinese-technical-writing for reader-facing Chinese review prose and TODOs: keep method names, acronyms, project names, and simulation terms when they are names, but translate ordinary technical concepts into Chinese instead of mixing raw English phrases into Chinese sentences.

For weekly literature picks / Week Summary pages, use weekly-research-summary instead of this skill.

Platform Placement

Use research-doc-workflow and the matching *-doc-workflow adapter for destination selection and durable writes. Preserve an existing review hub's platform; do not create a parallel Feishu copy when the active review system is Notion or Obsidian.