arch-flow

Generate architecture-flow.md with ASCII diagrams and pseudocode.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/hferello/ai --skill arch-flow-hferello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-flow
Source: https://github.com/hferello/ai/tree/main/arch-flow
Command: npx skills add https://github.com/hferello/ai --skill arch-flow-hferello

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts architecture documentation with ASCII box diagrams and pseudocode (no raw code) to help teams quickly capture system designs during feature planning.

Core Features & Use Cases

  • ASCII box diagrams for flow documentation
  • Pseudocode-based control-flow descriptions
  • Outputs architecture-flow.md next to the feature for easy reference

Quick Start

Ask Arch Flow to generate architecture-flow.md beside the feature and include ASCII diagrams and pseudocode.

Frequently Asked Questions about arch-flow

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

FAQPage Schema
How do I generate architecture documentation with ASCII diagrams and pseudocode?

You generate architecture documentation by requesting an architecture-flow.md file, which produces ASCII box diagrams and pseudocode-based control-flow descriptions to capture system designs during feature planning.

What is the best way to document API flows and cron jobs without raw code?

Documenting API and cron flows is best handled using pseudocode-based control-flow descriptions and ASCII box diagrams, which outline logic without raw code while satisfying a structured template with data-flow steps.

Can I use ASCII diagrams for feature planning flow documentation?

ASCII diagrams work for feature planning flow documentation by providing visual box diagrams that map system designs, allowing teams to quickly capture architecture alongside the feature for easy reference.

How does pseudocode-based architecture documentation compare to raw code diagrams?

Pseudocode-based architecture documentation abstracts implementation details into control-flow descriptions, whereas raw code diagrams expose exact syntax, making pseudocode better for high-level design and quick team alignment.

Does architecture-flow documentation require any specific frameworks or dependencies?

Architecture-flow documentation requires no specific frameworks or dependencies, operating independently to generate structured templates with ASCII diagrams and completion checklists directly next to your feature.

When should I not use ASCII diagrams for architecture documentation?

ASCII diagrams for architecture documentation should be avoided when your system design requires complex visual rendering beyond simple box diagrams, as the format is limited to text-based flow representation.