Menú
Checks if documentation needs updating after implementation changes
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.
Systematic troubleshooting for Woods — diagnose extraction, MCP, embedding, and storage issues
Generate correct .mcp.json configuration for Woods in any environment
Guide through Woods initial setup — install, configure, extract, verify, and connect MCP servers
Setup, operation, and debugging of the Unblocked integration — collection creation, incremental sync, the sync manifest, escape hatches, live API quirks, and smoke testing. Use when working on lib/woods/unblocked/, the woods:unblocked_sync rake task, sync CI wiring, or when a sync misbehaves (everything re-pushes, deletes refused, budget exhausted, 400s from the API).
Woods backlog workflow — picking items, implementing with TDD, marking resolved, and adding new work. Use when the user asks "what's next?", references backlog items, opens a session without a clear task, or when closing out work to record what shipped.
Generates boilerplate for a new Woods extractor and its spec
Basado en la clasificación ocupacional SOC
| name | doc-sync |
| description | Checks if documentation needs updating after implementation changes |
| disable-model-invocation | true |
After any implementation that changes extraction output, dependencies, configuration, or MCP tools, check whether documentation needs updating.
docs/README.md — Is the status table current? Mark completed features, update phase status.docs/design/OPTIMIZATION_BACKLOG.md — Is the resolved item marked ✅ with commit ref?CLAUDE.md — Do the Architecture, Gotchas, or Commands sections reflect the change?