architecture-map

Use when the user asks whether architecture docs are stale, whether docs and code still match, whether to validate before refresh, or when map validate needs…

当用户要求“create git commit”、“manage branches”、“follow git workflow”、“use Conventional Commits”、“handle merge conflicts”，或询问 Git 分支策略、版本控制最佳实践、Pull Request…

将工作流切换为 Manus 风格的持久化 Markdown 文件，用于规划、进度跟踪和知识存储。适用于复杂任务、多步骤项目、研究任务，或用户提到 planning、organizing work、tracking progress、需要结构化输出时。

用于涉及编写或修改源码的日常编码任务。

Initialize hello-scholar project assets for the current repository.

验证总入口，对照 contract、diff、change record 和 experiment evidence 完成交付门槛检查。

实验分析命令，基于 experiment package、runs、metrics 和 evidence 形成结果解释与下一轮实验计划。

实现命令，把 plan package、change record 或 experiment package 落成代码、配置、文档或实验变更。

结构化规划命令，优先复用 planning-with-files，并把方案包写入 hello-scholar/plans。

Use when the user asks for call order, startup order, command lifecycle, request lifecycle, experiment lifecycle, skill routing, agent dispatch, or how…

Use when the user asks to open the architecture viewer, view diagrams, inspect node evidence, export the local architecture map, or troubleshoot hello-scholar…

Use when the user asks to understand an unfamiliar repo, be onboarded, find entrypoints, map project structure, or identify where to change something.