code-to-hdsd

Generate structured HDSD documentation from FE and BE source code.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill code-to-hdsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-to-hdsd
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/.agent/skills/ba-code-to-hdsd
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill code-to-hdsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates structured HDSD from FE and BE source code and optional PRD, ensuring consistent system overview, workflows, and feature specs.

Core Features & Use Cases

  • Mapping FE routes, screens, and BE endpoints to a systematic HDSD structure (system overview, process, app lists, feature specs)
  • Output in md/docx/pdf
  • Supports optional PRD integration and automated export

Quick Start

Provide the FE and BE source repositories and an optional PRD, then run the built-in script to generate the HDSD in Markdown, Docx, or PDF.

Frequently Asked Questions about code-to-hdsd

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

FAQPage Schema
How do I generate end-user documentation from frontend and backend source code?

To generate end-user documentation from source code, provide your frontend and backend repositories to map UI flows to API calls. The tool traces routes and endpoints to output a structured HDSD summarizing actors, apps, and features.

What is the best way to create structured HDSD from multiple repositories?

Creating structured HDSD from multiple repositories involves analyzing both frontend and backend codebases to enforce extraction of business rules, system overviews, and procedural steps. This ensures consistent feature specs across your project.

Can I integrate a PRD into automated documentation generation?

Yes, you can integrate an optional PRD into the documentation generation process. Providing a PRD alongside your frontend and backend source code helps produce PRD-informed docs with accurate workflows and feature specifications.

Does this documentation automation tool support exporting to Markdown, Docx, and PDF?

Yes, this documentation automation tool supports exporting to Markdown, Docx, and PDF formats. After mapping your frontend and backend code structure, you can run the built-in script to generate the HDSD in your preferred format.

Do I need to provide both frontend and backend code to generate system overview documentation?

You need to provide both frontend and backend source repositories to generate comprehensive system overview documentation. Tracing UI flows from the frontend to API calls in the backend ensures accurate mapping of actors and features.