flow-archive

Archive completed development flows and elevate reusable patterns to a project knowledge base.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed development flows, ensuring that valuable learnings and patterns are captured and elevated to a project-wide knowledge base.

Core Features & Use Cases

  • Flow Archiving: Moves completed flow directories to a designated archive location.
  • Pattern Elevation: Identifies and extracts reusable patterns from flow learnings to a project-level file.
  • Knowledge Extraction: Generates detailed knowledge base entries for each archived flow.
  • Beads Integration: Closes associated Beads epics upon successful archiving.

Quick Start

Archive the flow with ID 'epic-123' and elevate its patterns.

Frequently Asked Questions about flow-archive

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

FAQPage Schema
How do I archive completed development flows and save reusable patterns?

Archiving completed development workflows involves moving associated directories to a designated archive location while extracting reusable patterns from flow learnings to a project-level knowledge base file.

What is pattern elevation in knowledge management for development workflows?

Pattern elevation identifies and extracts reusable patterns from flow learnings, storing them in a project-level file to ensure valuable insights are captured and accessible across the entire project knowledge base.

Can I close Beads epics automatically when archiving a flow?

Yes, flow archiving integrates directly with Beads to close associated epics automatically upon successful archival, ensuring your project tracking stays synchronized with completed development workflows.

How do I generate knowledge base entries for archived flows?

Generating knowledge entries for archived flows happens automatically during the archival process, creating detailed documentation that captures learnings and patterns from each completed development flow.

Do I need any specific dependencies to use this flow archiving workflow?

No external dependencies are required for flow archiving and pattern elevation, though integration with Beads is supported to automatically close associated epics upon successful archival.