gendoc-flow

Orchestrate BRD/IDEA-driven document pipelines through generation, review, and fix cycles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end document generation by coordinating a template-driven pipeline that stitches BRD/IDEA inputs into a complete documentation suite through Gen, Review, and Fix cycles with explicit state management.

Core Features & Use Cases

  • Cumulative upstream reading: every doc reads all ancestor docs to ensure consistency.
  • Universal generation and review: run generation, review, and fix loops for any document type via templates.
  • Deterministic progress and resume: breakpoint/resume support, quality status tracking, and committed round histories.
  • Interactive prototypes and diagrams: supports prototype generation and UML-like diagrams to aid implementation.
  • Use Case: Produce a full PRD/BRD-driven doc set from IDEA/BRD for a software project.

Quick Start

Run gendoc-flow to orchestrate your BRD/IDEA-driven documentation pipeline and generate all downstream artifacts.

Frequently Asked Questions about gendoc-flow

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

FAQPage Schema
How do I automate documentation generation from a BRD or idea?

Automate documentation generation from a BRD or idea by running a template-driven pipeline that orchestrates generation, review, and fix cycles to produce a complete documentation suite. The pipeline reads upstream documents to ensure consistency across all output artifacts.

What is a template-driven document pipeline and how does it work?

A template-driven document pipeline coordinates generation, review, and iteration cycles using defined templates for each document type. It reads all ancestor documents cumulatively to maintain consistency and tracks state to enable deterministic progress and resumption.

How do I resume an interrupted document generation workflow?

Resume an interrupted document generation workflow by relying on the pipeline's built-in state tracking and breakpoint support. The system records committed round histories and quality statuses, allowing you to restart the pipeline deterministically from the last completed step.

Do I need specific template files to run the documentation pipeline?

Yes, you need specific template files to run the documentation pipeline. The orchestration requires a pipeline.json configuration alongside generation and review markdown templates for each document type to define steps and enforce quality gating.

Can I generate interactive prototypes and diagrams alongside documentation?

Yes, you can generate interactive prototypes and UML-like diagrams alongside documentation. The pipeline supports prototype generation and diagram creation within its template-driven workflow to aid software implementation directly.

Best way to ensure consistency across a full PRD-driven documentation suite?

Ensure consistency across a PRD-driven documentation suite by using a pipeline that applies cumulative upstream reading, where every generated document reads all ancestor documents to maintain alignment throughout the generation, review, and fix cycles.