القائمة
以 repo 程式碼為唯一依據，維護標準化的 docs/features/、docs/architecture/、docs/principles/ 文檔， 並清理已失效或重複的舊文檔。每條文檔記述必須可追溯至實際程式碼證據。
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | docs-project |
| description | 以 repo 程式碼為唯一依據，維護標準化的 docs/features/、docs/architecture/、docs/principles/ 文檔， 並清理已失效或重複的舊文檔。每條文檔記述必須可追溯至實際程式碼證據。 |
以整個生產 repo 為唯一依據，建立或維護標準化的 docs/features/、docs/architecture/、docs/principles/ 文檔。
清理已失效或重複的舊文檔。
完成後同步刷新根目錄約束文件。
apltk codegraph 完成 repo 深度調查，產出模組邊界與關鍵 API 證據摘要docs/features/、docs/architecture/、docs/principles/ 文檔[INFERRED]AGENTS.md / CLAUDE.md 已被同步更新在開始文檔工作前，先用 apltk codegraph 建立對 repo 的深度理解。
apltk codegraph --help，再對候選 subcommand 執行 apltk codegraph <subcommand> --help。將調查結果記錄為結構化摘要，供後續文檔撰寫使用。
閱讀項目現有文檔，並結合 CodeGraph 調查結果，建立對 repo 的基線認知，制定後續閱讀策略。
按照上一步建立的閱讀策略，通過並行調度 subagents 全面搜索整個 repo，驗證並確保現有項目文檔的描述正確、無遺漏。
使用 subagents 深入閱讀關鍵程式碼片段：
根據上一步發現的文檔遺漏或脫節之處，制定文檔更新策略。
閱讀模板文檔；使用模板規定的格式重寫所有項目文檔。
移除舊有說明文檔（必要文檔如 CHANGELOG.md、CONTRIBUTION.md 除外）。
完成初始文檔後，在 docs/README.md 中記錄以下維護指引：
[INFERRED] 而非偽造。git diff 識別變更範圍，再決定哪些 .md 檔案需要更新。assets/templates/standardized-docs-template.md - 三類文檔的目標結構、分類規則與清理檢查表。