Results for “documentation-audit”

Use this skill for README, ADRs, runbooks, changelogs, decision records, operator docs. Trigger when the task involves programming work related to Documentation Adrs, production implementation, audits, debugging, strategy, or validation.

Verifies that blockchain code implements exactly what documentation specifies, identifying gaps between specs and implementation for audit engagements.

Generates, formats, and validates technical documentation including docstrings, OpenAPI specs, JSDoc annotations, documentation sites, and user guides.

Use before delivering any documentation to validate quality, accuracy, and completeness. This skill provides a checklist for reviewing all documentation deliverables to ensure they meet minimum quality standards before distribution.

Creates, structures, and reviews technical documentation using the Diátaxis framework, organizing content into tutorials, how-to guides, reference material, and explanations.

Generate clear documentation for each task including technical descriptions, architecture diagrams, and usage guides. Use when documenting completed features, creating README files, writing API documentation, generating architecture diagrams, or maintaining project documentation. Ensures knowledge is preserved and accessible.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Updates technical docs for verified behavior, public contracts, commands, configuration, and operations.

Guides users through a structured workflow for co-authoring documentation, proposals, technical specs, and decision docs across three stages: context gathering, iterative refinement, and reader testing.

Guides users through a structured three-stage workflow for co-authoring documentation, proposals, technical specs, and similar documents.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Automatically generate clear, comprehensive documentation for codebases — including API references, inline docstrings, README files, and usage guides. Use when the user requests code documentation or provides relevant inputs for this workflow.

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

Guides users through a structured three-stage workflow for co-authoring documentation, from context gathering to iterative refinement and reader testing.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Writing effective project documentation — READMEs, API doc comments, and inline comments that explain why. Use when writing or improving documentation — READMEs, doc comments, inline comments, or when code lacks explanation for non-obvious behavior.

Reconciles project documentation, agent memory, and rule files against the actual codebase after a development session, ensuring accuracy and consistency across all knowledge layers.

Bootstraps a two-part _docs directory (_build/ for technical docs, _public/ for research and proposals) with a CONSTITUTION.md governing the split, and can audit or migrate an existing structure.

Documents AI-built apps with architecture, permissions, secrets, and test coverage maps to make them reviewable before shipping.

GDPR and German DSGVO compliance automation. Scans codebases for privacy risks, generates DPIA documentation, tracks data subject rights requests. Use for GDPR compliance assessments, privacy audits, data protection planning, DPIA generation, and data subject rights management.

Prepare ISO 13485:2016 certification documentation for medical device Quality Management Systems, including gap analysis, template-based document creation, and compliance checklists.

Writes documents in a plain, human voice and removes phrasing that reads as machine-generated, applying a two-pass write-and-audit process to any written artifact meant to be read by a person.

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "UX experiment", "collaborative design", "outcome over output", "design studio method", "assumption mapping", or "lightweight research". Also trigger when reducing design documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.