agentleFS
TashanGKDTashanGKD/tashan-cursor-skills/skills/cognitive-review-brain-map/SKILL.md

cognitive-review-brain-map

Skill21 starsChanged 8 months agoMITView on GitHub

生成认知结构当前状态快照,帮助用户了解知识体系全貌并决定今日优先处理项。触发词:「大脑地图」「认知状态」「今天做什么」「复盘」「系统状态」「看一下状态」「有什么积压」。

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

大脑地图复盘 Skill(Review Brain Map)

读取认知结构各层状态,生成「今日认知快照」,帮助用户快速恢复上下文,决定下一步行动。


激活后立即执行

Step 1  读取全系统状态
        Read: _内部总控/认知结构/L0_大脑总地图.md
        Read: _内部总控/认知结构/L2_碎片化思考/碎片整合索引.md
        Read: _内部总控/认知结构/L3_原始记录/待完成总清单.md
        Read: _内部总控/认知结构/L1.5_底层原则层/底层原则库.md(只读候选原则部分)

Step 2  统计关键指标
        从碎片整合索引统计:
        → 待整合碎片总数(🔲状态)
        → 部分整合数(⚠️状态)
        → 待整合碎片的类型分布

        从待完成总清单统计:
        → 🔴 高优先级待处理数量
        → TOP 3 最紧急项(标题+涉及文档)

        从L1.5原则库统计:
        → 已确认原则数量
        → 候选原则数量(🟡状态)

        从L0文档读取:
        → 各L1文档的最后更新时间(找出最久未更新的)
        → 当前Gap状态(已完成/待处理)

Step 3  生成状态快照,清晰展示

        「━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
          🧠 认知状态快照(今日:YYYY-MM-DD)
          ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
          📝 待整合碎片:N 个(类型:产品理论M个、自我反思K个...)
          📋 高优先级待办:M 项
          💡 候选原则待确认:K 个
          📅 最久未更新L1文档:[文档名](N天前)
          ⚠️  当前已知缺口:X 个(见L0)

          TOP 待处理项:
          1. [TODO-XXX] [高优先] [描述] → 涉及[文档名]
          2. [TODO-XXX] [高优先] [描述] → 涉及[文档名]
          3. [TODO-XXX] [中优先] [描述] → 涉及[文档名]
          ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━」

Step 4  建议今日优先处理(根据积压情况自动推断)
        基于数量和优先级,给出1-3条建议:
        例:
        「建议今日优先:
          [1] 处理 N 个待整合碎片(运行「整合碎片」)
          [2] 确认候选原则 P? 是否成立(运行「提炼原则」)
          [3] 完善 [文档名](运行「更新知识」)
          [开始处理第1项] [开始处理第2项] [开始处理第3项] [我来决定]」

Step 5  追加 L3/系统日志.md
        [LOG-今日日期-NN] cognitive-review-brain-map | 生成认知快照 | 无文档变更

注意事项

  • 快照是只读的,本 Skill 不修改任何 L0/L1/L2/L3 文档内容
  • 如果 L0 不存在:「L0 大脑总地图不存在,建议先运行认知结构初始化」
  • 快照后直接建议行动,不要只展示数据,要帮用户做决策
  • 一次复盘后如果用户选择处理某项,直接过渡到对应 Skill,不要让用户重新说触发词

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.