메뉴
在一个 change 已完成实现、修正和审查后，负责做归档收尾与知识沉淀。用于用户要求 archive、归档需求目录、从 `log.md` 提炼知识发现与踩坑记录、逐条确认是否沉淀到 `docs/knowledge/`，并将已完成的 change 目录移入 `docs/archives/` 时使用。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
| name | spec-archive |
| description | 在一个 change 已完成实现、修正和审查后，负责做归档收尾与知识沉淀。用于用户要求 archive、归档需求目录、从 `log.md` 提炼知识发现与踩坑记录、逐条确认是否沉淀到 `docs/knowledge/`，并将已完成的 change 目录移入 `docs/archives/` 时使用。 |
在执行本 skill 时，同时遵守 ../../references/full-sdd-lifecycle.md 中 spec-archive 阶段的协同规则。
skills/documentation-and-adrs/SKILL.md 判断什么该沉淀为长期知识skills/shipping-and-launch/SKILL.md 的收尾心智确认当前 change 已真正闭环完成需求闭环后的最后一步：先提炼和确认长期有效知识，再归档 change 目录。
log.md 中识别值得长期保留的知识发现和踩坑记录docs/knowledge/docs/archives/执行前先确认以下条件成立：
log.mdspec.md、tasks.md，以便判断该 change 是否已闭环若以下任一情况成立，先停止，不归档：
log.md 缺失，无法提炼知识发现docs/knowledge/按以下顺序执行，不要跳步。
先读取最小必要上下文：
log.mdspec.md、tasks.md，确认该 change 的完成状态与范围docs/knowledge/README.md，确认知识沉淀的位置和索引方式docs/archives/执行时坚持下面约束：
docs/knowledge/从 log.md 中拆出候选条目，至少区分两类：
提炼时要做筛选：
在落盘前，必须逐条展示候选内容并征求确认。
docs/knowledge/不要把“展示候选”和“已经写入”混为一谈。
对已确认的条目，立即同步到 docs/knowledge/。
docs/knowledge/README.md 中合适的小节或索引docs/rules/若沉淀内容已经触达长期规则边界，应停止并建议改写到 docs/rules/，不要误放到 docs/knowledge/。
在知识沉淀完成后，再执行目录归档。
docs/archives/docs/archives/若移动目录会覆盖已有归档、破坏现有结构或导致引用失效，先停止并汇报。
向用户汇报时至少包含：
log.md 提炼出了哪些候选条目docs/knowledge/docs/archives/遇到以下情况时立即停止：
knowledge 还是 rules停止时要说明：
log.md 中的知识发现和踩坑记录docs/knowledge/docs/archives/docs/knowledge/交付前自行检查：
log.md 的真实记录docs/knowledge/docs/archives/feat: xxx需求已完成。注意，提交后等待用户审查后再执行push操作！