metodologia-technical-writing

What problem does it solve?

Technical documentation often collapses into verbose prose with inconsistent terminology and unverified claims. This skill enforces a disciplined approach to produce precise, traceable, and reproducible documentation that supports auditability and clear decision-making.

Core Features & Use Cases

• Progressive disclosure structure: TL;DR at the top, section-level TL;DRs, and detailed appendices to serve executives, architects, and implementers.
• Evidence tagging and provenance: Every quantitative claim and critical assertion carries an explicit tag such as [CÓDIGO], [CONFIG], [DOC], [INFERENCIA], [SUPUESTO], or [STAKEHOLDER].
• Terminology contract and cross-deliverables: One canonical term per concept across 00–09 deliverables, with explicit cross-references and glossaries.
• Templates and standards alignment: Aligns with ISO/IEC 26514, Diátaxis, and progressive disclosure patterns for enterprise technical writing.

Quick Start

Produce a production-ready technical writing deliverable that follows progressive disclosure and evidence tagging guidelines.