actualizar-documentacion-taimbox

Name: actualizar-documentacion-taimbox
Availability: InStock
Author: peypons

Align modular docs/* with the DOCUMENTACION.md index after code changes.

Updated Dec 13, 2025

Search Tags:#workflow #documentation #markdown #alignment #docs #documentation-management #product-change

Ready to run

npx skills add https://github.com/PeyPons/Timeboxing --skill actualizar-documentacion-taimbox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: actualizar-documentacion-taimbox
Source: https://github.com/PeyPons/Timeboxing/tree/main/.cursor/skills/actualizar-documentacion-taimbox
Command: npx skills add https://github.com/PeyPons/Timeboxing --skill actualizar-documentacion-taimbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mantiene la alineación entre los docs modulares (docs/*) y el índice DOCUMENTACION.md tras cambios de código, evitando desalineaciones que confundan a los lectores.

Core Features & Use Cases

Ajusta la documentación afectada cuando se libera o cierra una feature de producto.
Actualiza referencias en DOCUMENTACION.md para reflejar cambios visibles para el usuario.
Complementa la regla documentacion-cambios-producto para evitar ruido innecesario en los docs.

Quick Start

Solicita al agente que alinee docs/* y DOCUMENTACION.md luego de un cambio de código o cuando se solicite documentación.

Frequently Asked Questions about actualizar-documentacion-taimbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep modular documentation aligned with an index file after code changes?▼

Documentation drift happens when code changes alter features or Edge Functions without updating the corresponding docs/* files or the DOCUMENTACION.md index. This causes reader confusion as modular documentation no longer reflects the actual product behavior.

When should I update modular markdown documentation?▼

You should update modular markdown documentation when releasing or closing a product feature, touching Edge Functions or contract references, or when documentation is explicitly requested. Updates are enforced only for user-visible changes to avoid unnecessary noise.

How do I prevent documentation drift in a modular markdown workflow?▼

You prevent documentation drift in a modular markdown workflow by enforcing synchronization between docs/* files and the DOCUMENTACION.md index. This ensures modular documentation accurately reflects code changes without generating unnecessary noise for non-user-visible updates.

Does documentation alignment trigger on every code change?▼

No, documentation alignment does not trigger on every code change. It enforces updates to docs/* and DOCUMENTACION.md only when there is a user-visible change, such as releasing or closing a product feature, to avoid unnecessary documentation noise.

What is the best way to sync docs/* with a central documentation index?▼

The best way to sync docs/* with a central documentation index is to align them after code changes by applying updates only for user-visible product changes. This complements existing product-change rules and prevents modular documentation desynchronization.