document

Generate Markdown and HTML modularity review documents from coupling analysis results.

504|32|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/vladikk/modularity --skill document-vladikk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/vladikk/modularity/tree/main/skills/document
Command: npx skills add https://github.com/vladikk/modularity --skill document-vladikk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Manually creating modularity review documents that adhere to the Balanced Coupling model's requirements (including mandatory coupling.dev links, structured issue sections, and consistent formatting) is time-consuming and prone to human error, leading to incomplete or non-compliant review outputs.

Core Features & Use Cases

  • Dual-Format Document Generation: Produces both Markdown and HTML versions of the review document with identical content, ensuring accessibility for different stakeholders.
  • Structured, Standards-Compliant Output: Enforces the required document structure (executive summary, coupling overview table, detailed issue sections with severity classifications) and mandatory hyperlinks to all referenced coupling.dev concepts for full traceability to the Balanced Coupling model.
  • Use Case: After completing a modularity analysis of a codebase to identify coupling imbalances, use this skill to instantly generate a professional, shareable review document that stakeholders can use to prioritize architectural improvements.

Quick Start

Use the document skill to generate the final modularity review document for your completed codebase analysis, producing both Markdown and HTML versions in the correct dated output directory.

Frequently Asked Questions about document

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

FAQPage Schema
How do I generate a modularity review document from codebase coupling analysis results?

To generate a modularity review document from coupling analysis results, use this skill to automatically produce standardized Markdown and HTML outputs with executive summaries, coupling overview tables, and issue severity classifications.

What is the best way to create a Balanced Coupling model review document with required coupling.dev links?

Creating a Balanced Coupling model review document requires structured issue sections and mandatory coupling.dev hyperlinks for traceability, which this skill automatically enforces during Markdown and HTML document generation.

Can I output both Markdown and HTML versions of an architecture code review report simultaneously?

Yes, you can output both Markdown and HTML versions of an architecture code review report simultaneously, ensuring identical content is accessible across different stakeholder preferences and viewing environments.

How do I format code review documents to include severity classifications for coupling issues?

Formatting code review documents with severity classifications for coupling issues is handled automatically by applying predefined document structure and styling templates during the generation process.

Do I need to complete a codebase coupling analysis before generating a modularity review document?

Yes, completing a codebase coupling analysis is a prerequisite, as this skill requires completed analysis results to generate a professional, shareable modularity review document for prioritizing architectural improvements.

What structure is enforced when generating modularity review documents for architecture improvements?

The enforced structure for modularity review documents includes an executive summary, a coupling overview table, and detailed issue sections with severity classifications, all adhering to predefined styling templates.