flow-export

Generate project summary exports from flow definitions, patterns, and archives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of a comprehensive project summary export, consolidating information about flows, patterns, and archives.

Core Features & Use Cases

  • Consolidated Reporting: Gathers data from multiple sources (.agent/flows.md, .agent/patterns.md, .agent/specs/*/, .agent/archive/*/) into a single report.
  • Export Formats: Supports Markdown and JSON output formats.
  • Use Case: After completing a complex project with multiple development flows, use this Skill to generate a final report detailing all active and archived flows, project patterns, and overall task completion rates.

Quick Start

Use the flow-export skill to generate a markdown summary of the current project.

Frequently Asked Questions about flow-export

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

FAQPage Schema
How do I generate a project summary export from flow definitions and patterns?

Generate a project summary export by gathering data from flow definitions, patterns, specifications, and archives into a single consolidated report available in Markdown or JSON formats.

Can I export my codebase overview in JSON format?

Yes, you can export your codebase overview in JSON format, which structures data from flows, patterns, specifications, and archives for programmatic reporting use.

How do I create a consolidated report of archived flows and project patterns?

Create a consolidated report by gathering data from `.agent/flows.md`, `.agent/patterns.md`, `.agent/specs/*/`, and `.agent/archive/*/` to document active flows, archived flows, and task completion rates.

Does the project summary export include sensitive information?

No, the project summary export ensures all relevant data is included while strictly excluding sensitive information from the final Markdown or JSON report.

What's the best way to document task completion rates after completing complex development flows?

Document task completion rates by generating a final summary report that consolidates active and archived flows, project patterns, and overall task completion data into Markdown or JSON.

Are there limitations on what data sources can be included in the project reporting export?

The project reporting export is limited to gathering data from `.agent/flows.md`, `.agent/patterns.md`, `.agent/specs/*/`, and `.agent/archive/*/` directories while actively filtering out sensitive information.