workflow-docs

Generate and synchronize README and AI-summary files from PRD, MVP, ADR, and CLAUDE.md artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of documentation drift by automatically generating and synchronizing project-level README and AI-summary files based on existing project artifacts like PRDs, MVPs, and ADRs.

Core Features & Use Cases

  • Automated Synchronization: Keeps README.md and design/ai-summary.md in sync with project source files using marker-fenced regions that preserve manual edits.
  • Context-Aware Generation: Dynamically omits or includes sections based on the presence of source data, ensuring documentation is never stale or filled with placeholders.
  • Use Case: After updating a project's ADRs or MVP scope, run this skill to instantly refresh the project's public-facing documentation and AI-readable summary without manual copy-pasting.

Quick Start

Run the workflow-docs skill from the root of your project directory to generate or refresh your project documentation.

Frequently Asked Questions about workflow-docs

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

FAQPage Schema
How do I automatically sync project documentation with source files?

To automatically sync project documentation, this Skill parses PRD, MVP, ADR, and CLAUDE.md files to generate standardized README and AI-summary outputs. It uses marker-fenced regions to preserve manual edits while keeping documentation consistent with your project artifacts.

How do I generate a README from existing PRD and ADR files?

You can generate a README from existing PRD and ADR files by running the Skill from the root of your git-initialized repository. It dynamically includes or omits sections based on the presence of source data, ensuring the output is never filled with stale placeholders.

Does documentation synchronization work with non-software projects?

Documentation synchronization works with non-software projects managed via GitHub and Claude Code. The Skill applies to any project context as long as the repository is git-initialized and contains the relevant design artifacts like PRDs and MVPs.

Will automated README generation overwrite my manual edits?

Automated README generation will not overwrite your manual edits because the Skill uses marker-fenced regions. This mechanism protects specific sections while dynamically updating and refreshing the rest of the documentation based on your latest project artifacts.

What is the best way to prevent documentation drift in a GitHub repository?

The best way to prevent documentation drift is to automatically synchronize project-level README and AI-summary files with existing artifacts. By parsing source files like PRDs and ADRs, this approach ensures project metadata remains consistent without manual copy-pasting.

Why does my documentation generation skill require a git-initialized repository?

Documentation generation requires a git-initialized repository to correctly locate and parse your project's design artifacts. Without this environment setup, the Skill cannot accurately read the necessary PRD, MVP, and ADR files to generate the standardized outputs.