flow-docs

Validate, capture, archive, and clean up software project documentation.

15|4|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/cofin/flow --skill flow-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-docs
Source: https://github.com/cofin/flow/tree/main/templates/codex/skills/flow-docs
Command: npx skills add https://github.com/cofin/flow --skill flow-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of validating, capturing, and archiving project documentation, ensuring consistency and knowledge retention.

Core Features & Use Cases

  • Documentation Validation: Enforces structural, content, and consistency checks on project documents.
  • Knowledge Capture: Extracts and summarizes key patterns and information from completed flows into a knowledge base.
  • Archiving & Cleanup: Manages the lifecycle of documentation by archiving completed items and removing stale artifacts.
  • Use Case: After completing a development cycle, use this Skill to automatically validate all generated documentation, capture new design patterns, and archive the completed project artifacts.

Quick Start

Run the flow-docs skill to perform a full documentation cycle including validation, knowledge capture, archiving, and cleanup.

Frequently Asked Questions about flow-docs

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

FAQPage Schema
How do I validate project documentation against consistency and currency requirements?

Documentation validation enforces structural, content, consistency, and currency checks on project documents. This process ensures all generated artifacts meet predefined requirements before a development cycle concludes, verifying accuracy and completeness across files.

What is the best way to capture recurring design patterns into a knowledge base?

Knowledge capture extracts and summarizes key patterns from completed flows into a knowledge base. This automates pattern retention by updating the central repository with new design information after project completion, preserving team insights automatically.

How do I archive completed documentation flows and clean up stale artifacts?

Archiving completed documentation flows and cleaning up stale artifacts manages the document lifecycle. This process archives finished items and automatically removes outdated artifacts to maintain a streamlined workspace, ensuring only active files remain.

Can I run a full documentation workflow cycle automatically after a development phase?

Yes, running a full documentation workflow cycle automates validation, knowledge capture, archiving, and cleanup. This manages the five-phase workflow automatically after completing a development cycle to ensure documentation consistency and knowledge retention.

What specific checks are included in documentation validation for software projects?

Documentation validation for software projects includes structural, content, consistency, and currency checks. These checks verify that project documents are properly formatted, accurately populated, internally consistent, and up to date with current standards.

When do I need to use a five-phase documentation workflow?

A five-phase documentation workflow is needed when completing a development cycle and requiring automated validation, knowledge capture, archiving, and cleanup. It ensures consistency and knowledge retention for software project artifacts, preventing information loss.