eliteforge-tech-doc

Extract and structure technical design information from Markdown, PlantUML, Mermaid, and draw.io sources.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/CloudSen/eliteforge-skills --skill eliteforge-tech-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eliteforge-tech-doc
Source: https://github.com/CloudSen/eliteforge-skills/tree/main/skills/eliteforge-tech-doc
Command: npx skills add https://github.com/CloudSen/eliteforge-skills --skill eliteforge-tech-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Converts scattered project documents and diagrams into a cohesive, reviewable technical design document, with traceable sources and evidence.

Core Features & Use Cases

  • Source consolidation: scans Markdown, PlantUML/Mermaid diagrams, draw.io files, and images to build a unified design view.
  • Evidence-driven output: attaches the originating files as sources with each conclusion and flags gaps for confirmation.
  • Template-aware drafting: uses the tech-doc-template to produce a structured document ready for review.

Quick Start

Run eliteforge-tech-doc to scan the current directory and produce a structured tech design draft.

Frequently Asked Questions about eliteforge-tech-doc

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

FAQPage Schema
How do I consolidate scattered Markdown and Mermaid diagrams into a single technical design document?

To consolidate scattered Markdown and Mermaid diagrams into a technical design document, the tool scans current project sources and structures extracted information using a tech-doc-template. It produces a cohesive draft with traceable file provenance for review.

What is the best way to extract architecture information from PlantUML and draw.io files for a design review?

The best way to extract architecture information from PlantUML and draw.io files is using an automated scanner that enforces source provenance. It consolidates design content across these formats and flags gaps for confirmation during the review process.

Can I generate a reviewable tech design draft from existing project documentation?

Yes, you can generate a reviewable tech design draft from existing project documentation. The tool extracts and structures design information from Markdown and diagrams, attaching originating files as evidence to produce a template-aware output.

Does this technical design extraction approach work with draw.io images and PlantUML diagrams?

Yes, this technical design extraction approach works with draw.io images and PlantUML diagrams. It scans Markdown, PlantUML/Mermaid, and draw.io sources to build a unified design view while enforcing evidence and a clearly defined scope.

How does evidence-driven source provenance work when summarizing technical design documents?

Evidence-driven source provenance works by attaching the originating files as sources to each conclusion within the technical design document. This mechanism flags gaps requiring confirmation and ensures all consolidated design content remains traceable.

What are the limitations of automatically structuring technical design information from project docs?

A limitation of automatically structuring technical design information is that it requires confirmation for flagged gaps within the source materials. The tool enforces a clearly defined scope to prevent unverified content from entering the final reviewable draft.