gendoc

Generate engineering documents from templates and upstream sources.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ibalasite/gendoc --skill gendoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gendoc
Source: https://github.com/ibalasite/gendoc/tree/main/skills/gendoc
Command: npx skills add https://github.com/ibalasite/gendoc --skill gendoc

SYSTEM DOCUMENTATION & REQUIREMENTS

Universal document generator. Reads templates/<TYPE>.md (structure) and templates/<TYPE>.gen.md (generation rules) to produce docs/<TYPE>.md from upstream engineering documents. Type is provided as the first argument. Use when asked to "gendoc edd", "gen brd", "生成 PRD", "gendoc local-deploy", etc. Proactively invoke when the user specifies a document type to generate. (gendoc)

What problem does it solve?

The GENDOC pipeline streamlines producing consistent, up-to-date documentation from templates and upstream sources, eliminating manual drafting and ensuring traceability.

Core Features & Use Cases

  • Cumulative upstream reading: every doc reads all ancestor documents, never just the direct parent.
  • Universal generation and review: supports /gendoc <type> generation and /reviewdoc <type> review loop with configurable strategies.
  • Breakpoint resume and quality tracking: tracks progress and quality status to ensure reliable, auditable output.

Quick Start

Run /gendoc <type> to generate your docs from templates and upstream documents.

Frequently Asked Questions about gendoc

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

FAQPage Schema
How do I automate engineering documentation generation from markdown templates?

Generate engineering docs from markdown templates by running a single command that reads template structures and upstream ancestor documents. The pipeline applies generation rules to produce consistent, production-ready files with enforced quality and traceability.

What's the best way to maintain traceability across upstream documents like EDD, BRD, and PRD?

Maintain traceability across EDD, BRD, and PRD files by using cumulative upstream reading, where every generated document reads all ancestor documents rather than just the direct parent. This ensures full context and consistency across engineering docs.

Can I resume document generation from a checkpoint if the process is interrupted?

Yes, you can resume document generation from a checkpoint. The pipeline tracks progress and quality status through breakpoint resume functionality, ensuring reliable and auditable output even if the generation process is interrupted midway.

How do I review generated engineering docs for quality and structural compliance?

Review generated engineering docs for quality by using a configurable review loop. This validates the produced files against generation rules and template structures to ensure structural compliance, consistency, and traceability before finalizing.

Do I need to manually format architecture and API docs when using template-driven generation?

No, manual formatting is unnecessary for architecture and API docs. Template-driven generation reads predefined structures and generation rules to automatically produce consistent, formatted markdown files for ARCH, API, and other document types.

What are the limitations of automating documentation with rule-based templates?

The limitation of rule-based template automation is the strict dependency on predefined template structures and upstream document availability. Generation quality relies entirely on the completeness of ancestor documents and the configured generation rules.