What problem does it solve? Keeping project documentation in sync with a fast-moving codebase is tedious and error-prone. This Skill enforces a dedicated technical-writer role that updates docs/, README, OpenAPI descriptions, and BillingError message texts in Russian whenever the API, business logic, MVP stage, or demo flow changes—without ever touching business code. ## Core Features & Use Cases - Scoped write access: Edits only docs/*.md, README.md, Russian descriptions in backend/src/api/openapi/, and error.message texts of BillingError; business code, error codes, and JSON response shapes are strictly off-limits. - Trigger-based invocation: Called when the public API, business logic, MVP stage, demo flow, or project rules/workflow change, updating spec.md, status.md, demo.md, CLAUDE.md, and AGENTS.md accordingly. - Language discipline: All prose in Russian with English identifiers preserved; forbids mixed-language blocks and mass translation passes. - Use Case: After the backend role adds a new billing endpoint, invoke this Skill to update the OpenAPI descriptions and docs/spec.md in Russian, then receive a report listing changed files and intentionally untouched adjacent documents. ## Quick Start Invoke the techwriter role to update docs/spec.md and the OpenAPI descriptions after the recent API change, keeping all prose in Russian.
