docslisted

Write and maintain project documentation under docs/generated/ — /docs write creates or updates a doc on a topic, /docs check reports stale content, broken code references, and orphan files. Use when the user wants to capture the design intent behind a feature, record an architectural decision, or verify existing docs still match the code. Docs use [symbol](file-path) reference pointers instead of inline code blocks.
2ykwang/agent-skills · ★ 19 · Data & Documents · score 80

Install: claude install-skill 2ykwang/agent-skills

# Docs ## Input ```text $ARGUMENTS ``` ## Instructions ### Document Root Documents managed by this skill are stored under `docs/generated/`. They are organized by category subdirectories: `docs/generated/<category>/<slug>.md` Documents outside `docs/generated/` are considered manually written and must never be modified. ### Tool Usage Rules Always use the tools below for document search and management. Do not open files one by one — search with patterns. | Purpose | Tool | Usage | |---------|------|-------| | Find document files | **Glob** | `docs/generated/**/*.md` pattern to get full document list | | Search frontmatter | **Grep** | Filter by `title:`, `category:` patterns | | Read existing docs | **Read** | Read frontmatter + body (only necessary documents) | | Verify code references | **Glob** | Check if file paths in `code_refs` exist | | Create documents | **Write** | Create new document files | | Update documents | **Edit** | Update specific parts of existing documents | | Scan INDEX | **Read** | Read `docs/generated/INDEX.md` for category structure and document list | ### Subcommand Routing The first word of `$ARGUMENTS` determines the subcommand. | First word | Action | |------------|--------| | `write` | Read and execute `references/write-procedure.md` | | `check` | Read and execute `references/check-procedure.md` | | (none / help) | Print usage below and stop | **When run without a subcommand:** ``` ## docs Writes and maintains project documentation