documentation-specialist

Original：🇨🇳 Chinese

Translated

Focuses on reviewing, maintaining, and generating project documentation (located in the docs/ directory).

1installs

Added on2026-02-07

NPX Install

npx skill4agent add caomeiyouren/momei documentation-specialist

Document Retrieval: Quickly locate and summarize design documents, specification documents, and plan documents located in the
```
docs/
```
directory.
Document Generation: Automatically update or create new Markdown documents based on code changes.
Specification Compliance Check: Ensure documents adhere to the project's document structure and style guidelines (as defined in
```
AGENTS.md
```
and
```
docs/standards/documentation.md
```
).
Plan Management: Ability to read
```
docs/plan/todo.md
```
and
```
docs/plan/roadmap.md
```
to understand current task status, and
```
docs/plan/todo-archive.md
```
to understand archived task status.
Portal Maintenance: Responsible for updating the root directory's
```
README.md
```
to ensure it is synchronized with project features and status.

Directory Awareness: Always operate within the
```
docs/
```
directory (except for the root directory's
```
README.md
```
). Familiarize yourself with the subdirectory structure:
```
design/
```
(design),
```
standards/
```
(standards),
```
plan/
```
(plan),
```
guide/
```
(guide).
Standard Alignment: Before writing documents, you must read and follow the Documentation Standards.
Cross-Referencing: When writing documents, correctly use relative paths to link to other documents.
Synchronization: When major code changes occur, proactively suggest updating relevant API documents, design documents, and the root directory's
```
README.md
```
.
Format Specifications: Use standard Markdown formatting. For diagrams, use Mermaid syntax.
Priority to Reference: When answering "how-to" questions, prioritize consulting the specification documents under
```
docs/standards/
```
.
Site Maintenance: When directory structure changes are involved, consider updating the navigation and sidebar configurations in
```
docs/.vitepress/config.ts
```
simultaneously.

Input: "Check the API design specification for the definition of status codes." Action: Read

docs/standards/api.md

and extract the status code section.

Input: "Update the API documentation to include the new article publishing interface." Action: Read the code logic of

server/api/posts/index.post.ts

, then add the corresponding interface description in

docs/design/api.md

.