Menú
Use when changing docs, skills, AGENTS files, specs, ADRs, source-of-truth routing, or when code changes make existing docs stale.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Use when adding or changing backend HTTP API handlers, REST controllers, request/response DTOs, Joi schemes, or OpenAPI REST contract entries.
Use for backend bug fixes, cleanup, extraction, or moving code between layers while preserving behavior and architecture boundaries.
Use when changing Redis or cache behavior.
Use when changing backend game, package, validation, or service rules.
Use when changing backend timers, scheduled work, Redis expiration handlers, pub/sub listeners, cleanup work, or lifecycle notifications.
Use when adding or changing server Socket.IO game events, GameActionType handlers, action use cases, socket payloads, GameActionExecutor flows, or public socket contracts. Do not use for REST-only endpoint changes.
Basado en la clasificación ocupacional SOC
| name | docs-upkeep |
| description | Use when changing docs, skills, AGENTS files, specs, ADRs, source-of-truth routing, or when code changes make existing docs stale. |
Use this skill when creating, changing, removing, or collapsing project documentation, or when implementation work changes behavior that docs describe.
docs/agent/02-source-of-truth.mddocs/agent/04-docs-drift-policy.mdAGENTS.mdAGENTS.md for the affected areaDocumentation is part of implementation. If a task changes architecture, workflows, commands, public contracts, game behavior, generated-code flow, validation structure, or product decisions, update the related docs in the same task when practical.
Do not wait for a periodic docs cleanup if the current task made a doc stale.
Update docs when changing:
Add a doc/skill when:
Do not add a new doc just because a small feature was implemented. Prefer updating an existing spec or skill.
Remove or collapse docs when they are stale, misleading, duplicated, no longer relevant after a release phase, or replaced by a better source of truth.
When removing docs, update all links that pointed to them.
Report docs added/changed/removed, stale docs fixed, source-of-truth links updated, commands or workflows changed, and docs intentionally not updated with reason.