docs-hero

Coordinate seven sub-skills to generate and synchronize a full documentation suite from inputs and OpenSpec changes.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/mor-duongmh/morkit-plugin --skill docs-hero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-hero
Source: https://github.com/mor-duongmh/morkit-plugin/tree/main/plugins/morkit/skills/docs-hero-orchestrator
Command: npx skills add https://github.com/mor-duongmh/morkit-plugin --skill docs-hero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, python-docx, and includes scripts (resource) components.

What problem does it solve?

The orchestrator coordinates seven sub-skills to automatically generate and update a full documentation suite (SRS / API / DB / system-architecture / code-standards / codebase-summary / design-guidelines) from inputs, OpenSpec changes, and codebase scans.

Core Features & Use Cases

  • Orchestrates seven sub-skills with shared parsers, the diff engine, atomic write workflows, and session locks.
  • Supports init / update / sync flows, managing multi-doc outputs and user-driven selections via a single coordinator.
  • Handles environment context, integrates with plugin-based tools, and bootstraps per-project metadata for consistent rendering.

Quick Start

Run /docs-hero init to generate the requested doc outputs from inputs and OpenSpec changes.

Frequently Asked Questions about docs-hero

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

FAQPage Schema
How do I automate documentation generation for a full software suite including SRS and API docs?

Orchestrating documentation generation involves coordinating multiple sub-skills to produce a full suite, including SRS, API, database design, and system architecture docs. It processes codebase scans and OpenSpec changes to apply delta-driven updates automatically.

What is delta-driven documentation synchronization and how does it work?

Delta-driven documentation synchronization applies updates by detecting changes from OpenSpec inputs and codebase scans, then using a diff engine to render only the modified sections. It ensures multi-doc outputs stay consistent without rewriting entire files.

How do I update multiple technical documents simultaneously without causing write conflicts?

Updating multiple technical documents simultaneously requires a coordinator that manages atomic write workflows and session locks across sub-skills. This conflict-aware rendering ensures shared parsers and project-wide metadata remain synchronized.

Does docs-hero work with OpenSpec inputs for project documentation automation?

Yes, the orchestrator works directly with OpenSpec inputs, using deltas from specification changes to drive updates across the documentation pipeline. It bootstraps per-project metadata to maintain consistent rendering across all seven sub-skills.

What are the limitations of orchestrating multi-subskill documentation pipelines?

Orchestrating multi-subskill pipelines depends on shared parsers and a project-wide meta store, meaning it requires environment context setup and plugin-based tool integration. It is limited to structured inputs like OpenSpec deltas and codebase scans rather than freeform text.