← ClaudeAtlas

iw-doc-generatorlisted

Generate or update documentation for InnoForge modules, architecture areas, release notes, error catalog, or webhook reference. Use when asked to "generate docs", "update documentation", "document module", "document architecture", "generate release notes", "update error catalog", "/iw-doc-generator".
innovation-ways/iw-ai-core · ★ 0 · AI & Automation · score 70
Install: claude install-skill innovation-ways/iw-ai-core
# InnoForge Documentation Generator Generate or update documentation for: **$ARGUMENTS** ## Supported Targets | Target Type | Syntax | Output | |-------------|--------|--------| | `module <name>` | `/iw-doc-generator module auth` | Module deep-dive in `docs/architecture/modules/` | | `release-notes <version>` | `/iw-doc-generator release-notes v1.2.0` | Release notes in `docs/releases/` | | `error-catalog` | `/iw-doc-generator error-catalog` | Updated `docs/api/ERROR_CATALOG.md` | | `webhook-reference` | `/iw-doc-generator webhook-reference` | Updated `docs/api/webhooks.md` | ## Step 1: Parse Target **If `$ARGUMENTS` starts with `doc-job`** (e.g. `doc-job 4914211f-...`): skip directly to the **[Job lifecycle](#job-lifecycle-when-invoked-via-iw-doc-generator-doc-job-job-id)** section at the bottom of this skill. Do not execute Steps 2–6. Otherwise, extract the target type and name from `$ARGUMENTS`. If ambiguous, ask the user to clarify. ## Step 2: Read Context Before generating anything, read the relevant source files: **For module docs:** 1. Read `docs/documentation-strategy.md` section 4.3 for the module doc template 2. Read `src/innoforge/CLAUDE.md` for backend architecture context 3. Read the target module's source files: - `src/innoforge/models/{module}.py` (if exists) - `src/innoforge/services/{module}_service.py` (if exists) - `src/innoforge/repositories/{module}_repository.py` (if exists) - `src/innoforge/api/v1/{modu