# ArcheFlow Examples

Ready-to-use examples showing different ArcheFlow configurations.

## Single-Project Runs

| Example | Description |
|---------|-------------|
| [feature-implementation.md](feature-implementation.md) | Walkthrough of a standard-workflow feature (rate limiting) across 2 PDCA cycles |
| [security-review.md](security-review.md) | Security-focused review using Guardian and Trickster archetypes |
| [custom-workflow.yaml](custom-workflow.yaml) | Custom workflow definition for API-first design with contract validation |

## Multi-Project Runs

| Example | Description |
|---------|-------------|
| [multi-project-giesing.yaml](multi-project-giesing.yaml) | Improve ArcheFlow + Colette in parallel, then write a story using both (3 projects, 2 layers) |
| [multi-project-fullstack.yaml](multi-project-fullstack.yaml) | Fullstack auth feature: shared types first, then backend + frontend in parallel (3 projects, 2 layers) |

## Directories

| Directory | Description |
|-----------|-------------|
| [custom-archetypes/](custom-archetypes/) | Domain-specific archetype definitions (story-explorer, story-sage) |
| [teams/](teams/) | Team composition files for multi-agent runs (story-development) |
| [workflows/](workflows/) | Custom workflow definitions (kurzgeschichte) |

## Usage

Single-project run with default settings:

```bash
archeflow:run
```

Multi-project run from a config file:

```bash
archeflow:multi-project --config examples/multi-project-giesing.yaml
```

Dry-run to preview cost estimates without executing:

```bash
archeflow:multi-project --config examples/multi-project-fullstack.yaml --dry-run
```