Skip to content
Agentmart
Submit a tool

documentation-organization

Organize project documentation into a clear authoritative structure, classify source documents, preserve traceability, and create indexes or handoff maps.

Skill by linjuhon

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/linjuhon-documentation-organization

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Organize project documentation into a clear authoritative structure, classify source documents, preserve traceability, and create indexes or handoff maps. Use when documentation is scattered, duplicated, stale, being archived, or needs a durable reading order for another agent.

Use cases: agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/documentation-organization

What's inside

Skill name
documentation-organization
Description
Organize project documentation into a clear authoritative structure, classify source documents, preserve traceability, and create indexes or handoff maps. Use when documentation is scattered, duplicated, stale, being archived, or needs a durable reading order for another agent.
License
MIT
Instructions
35 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Documentation Organization

建立可追溯、可導航且適合 agent 閱讀的專案文檔結構。先辨識權威來源與作用域，再整理索引、封存重複內容，並保留原始檔案與決策脈絡。

## Workflow

1. **盤點**：列出目標範圍內的文檔、格式、日期、狀態與相互引用；不要先移動或刪除檔案。
2. **分級**：將內容分成 contract／authority、active plan、execution evidence、handoff／status、archive 五類。
3. **指定權威來源**：每個主題只能有一個 canonical 文件；在索引中記錄其他文件是副本、快照、證據或已封存版本。
4. **設計閱讀路徑**：先放入口與 authority map，再放目前狀態、有效 gate、證據與詳細參考資料。
5. **整理與封存**：只在確認引用與檔案所有權後移動；保留 archive index、原始相對路徑與封存理由。
6. **驗證**：檢查索引中的路徑存在、連結可解析、沒有互相衝突的 canonical 宣告，並清楚標出缺失或過期資料。

## Classification Rules

- **Authority／contract**：定義規則、gate、schema 或不可推翻的操作契約。
- **Active plan**：目前執行目標、步驟、阻塞與下一個動作。
- **Evidence**：由實際命令、測試或觀察產生的可驗證結果；不能用推測取代。
- **Handoff／status**：給下一個 agent 的狀態、剩餘工作、限制與回復路徑。
- **Archive**：不再是目前操作來源，但仍需保留以供追溯的歷史材料。

## Output Contract

整理完成時，回報：

- 目標範圍與未處理範圍
- canonical 文件與其理由
- 新增、修改、移動或封存的路徑
- 索引／閱讀順序
- 未解決的重複、斷鏈、過期或缺失項目
- 是否有任何檔案因 dirty worktree、所有權或證據不足而保留原位

不要為了「看起來整齊」而批次重命名、刪除或覆寫檔案；若來源衝突，先保留並標記衝突，交由使用者決定。

From linjuhon/codex-personal-skills, MIT.

More from linjuhon/codex-personal-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 8, 2026 (2 months ago)
Last release
Aug 8, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/linjuhon/codex-personal-skills
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from linjuhon

Cite this page

documentation-organization skill. Agent Mart. https://agentmart.dev/skills/linjuhon-documentation-organization (last updated 2026-10-24)