Menü
將已完成的spec歸檔到 `docs/archive/` 下。當你需要將spec歸檔時，調用這個技能。
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Reads SPEC.md, validates technical feasibility through web research, finds quality reference implementations, confirms tech stack compatibility, then produces DESIGN.md (architecture design, external dependencies), CHECKLIST.md (verification strategy), Architecture Diff, and design-time refactoring plan. Not for use without a SPEC.md.
Helps users clarify vague requirements through structured conversation, producing a high-level design (PROPOSAL.md) with requirement summaries. Does not read any repo files — relies entirely on conversation. Suitable for requirement discussions, feature ideation, or greenfield project planning.
Executes FIX.md (from the qa skill) as the fix coordinator. The coordinator reads the fix plan, dispatches fix workers and regression test workers, verifies batch gates, and manages the execution flow — it does not write or fix code itself.
Executes PROMPT.md (from the plan skill) as the implementation coordinator. The coordinator reads the plan, dispatches workers, verifies batch gates, and manages the execution flow — it does not write implementation code itself.
Converts SPEC.md + DESIGN.md + CHECKLIST.md into a self-contained coordinator prompt (PROMPT.md) with complete task decomposition, dependency analysis, batch scheduling, and pre-written worker prompts. The generated PROMPT.md is consumed directly by the implement skill.
Reads spec documents and the review output REPORT.md, then generates a self-contained fix coordinator prompt (FIX.md) with issue inventory, dependency analysis, batch scheduling, regression test design, and pre-written worker prompts. The generated FIX.md is consumed directly by the fix skill.
| name | archive |
| description | 將已完成的spec歸檔到 `docs/archive/` 下。當你需要將spec歸檔時，調用這個技能。 |
把已完成的規劃文件轉成專案的長期文檔資產，讓正式文件反映目前真實系統，而活動中的 planning artifacts 與已消耗完的 spec 能被清楚分離。
docs/plans/ 目錄下不存在任何完成但未歸檔的spec在 docs/plans/ 目錄下找到現有的所有spec。閱讀每一份spec的 checklist.md, tasks.md, spec.md 並檢查當中的markdown checkboxes是否被全部勾選為完成（除與任務無關的 checkboxes 外，比如 spec 的批准狀態）。
將 checklist.md, tasks.md, spec.md 三份文檔checkboxes皆完成勾選的spec標記為已完成。
使用 docs-project, maintain-project-constraints 技能，按照這兩個技能之中的指引，更新項目文檔。
使用 apltk CLI 工具將 architecture diff 合併回項目架構圖。在操作前先閱讀 references/architecture.md，並執行 apltk architecture --help 與相關子命令 --help，以 live CLI 指引確認 merge 與相關參數。
將完成的spec全部移動到 docs/archive/。
references/architecture.md — apltk architecture 工具參考；仍必須以 apltk architecture --help 的 live 輸出確認最新用法。assets/templates/readme.md：README.md 模板