---
name: using-archeflow
description: Use at session start when implementing features, reviewing code, debugging, or any task that benefits from multiple perspectives. This skill activates ArcheFlow multi-agent orchestration with Jungian archetypes.
---

# ArcheFlow — Multi-Agent Orchestration

You have ArcheFlow installed. ArcheFlow gives you a structured way to coordinate multiple agents through quality cycles using Jungian archetypes as behavioral protocols.

## How It Works

Instead of one agent doing everything, ArcheFlow splits work across **archetypal roles** that think differently. Each has a virtue (what they contribute) and shadows (how they fail):

| Archetype | Virtue | Shadows |
|-----------|--------|---------|
| **Explorer** | Contextual Clarity — maps the landscape | Rabbit Hole · Catalog Fetish |
| **Creator** | Decisive Framing — one clear plan | Perfectionist · Over-Architect |
| **Maker** | Execution Discipline — working, tested code | Cowboy · Scope Creep |
| **Guardian** | Threat Intuition — sees real risks | Paranoid · Gatekeeper |
| **Skeptic** | Assumption Surfacing — finds blind spots | Paralytic · Whataboutist |
| **Trickster** | Adversarial Creativity — breaks before users do | Saboteur · Scope Escape |
| **Sage** | Maintainability Judgment — sees the forest | Bureaucrat · Philosopher |

## PDCA Quality Cycles

Work flows through **Plan → Do → Check → Act** in a rising spiral using **PDCA cycles**. Each cycle incorporates feedback from the previous one:

```
Plan:  Explorer researches → Creator proposes solution
  ↓
Do:    Maker implements in isolated worktree
  ↓
Check: Guardian + Skeptic + Sage review in parallel
  ↓
Act:   All approved? → Merge and done
       Issues found? → Spiral up: feed back to Plan, cycle again
```

Each cycle builds on feedback from the last.

## When to Use ArcheFlow

**USE IT when:**
- Implementing features that span multiple files or concerns
- The task has security, performance, or reliability implications
- You'd benefit from a code review before merging
- Debugging requires testing multiple hypotheses in parallel
- The user asks for thorough, multi-perspective work

**SKIP IT when:**
- Single-file typo fix or formatting change
- User explicitly wants quick-and-dirty
- Task is purely informational (reading, explaining)

## Built-in Workflows

| Workflow | Phases | Cycles | Best For |
|----------|--------|--------|----------|
| `fast` | Creator → Maker → Guardian | 1 | Bug fixes, small changes |
| `standard` | Explorer + Creator → Maker → Guardian + Skeptic + Sage | 2 | Features, refactors |
| `thorough` | Explorer + Creator → Maker → All 4 reviewers | 3 | Security-critical, public APIs |

## How to Run an Orchestration

When a task matches, use the **archeflow:orchestration** skill. It will guide you through:
1. Selecting the right workflow
2. Spawning archetype agents (using the Agent tool with worktree isolation)
3. Managing PDCA cycles
4. Merging results

## Shadow Detection

Each virtue has shadows — what happens when the strength is pushed too far:

| Virtue → | Shadow 1 | Shadow 2 |
|----------|----------|----------|
| Contextual Clarity → | **Rabbit Hole** (won't stop searching) | **Catalog Fetish** (dumps, doesn't analyze) |
| Decisive Framing → | **Perfectionist** (revises endlessly) | **Over-Architect** (designs for 100x) |
| Execution Discipline → | **Cowboy** (ships without tests) | **Scope Creep** (fixes unrelated code) |
| Threat Intuition → | **Paranoid** (blocks everything) | **Gatekeeper** (rejects without fix) |
| Assumption Surfacing → | **Paralytic** (approves nothing) | **Whataboutist** (tangent chains) |
| Adversarial Creativity → | **Saboteur** (destroys, doesn't report) | **Scope Escape** (tests unrelated code) |
| Maintainability Judgment → | **Bureaucrat** (review > code change) | **Philosopher** (insight without action) |

If you detect shadow behavior in an agent's output, apply the correction from the **archeflow:shadow-detection** skill.

## Other ArcheFlow Skills

- **archeflow:orchestration** — Step-by-step orchestration execution
- **archeflow:plan-phase** — Explorer + Creator behavior
- **archeflow:do-phase** — Maker implementation rules
- **archeflow:check-phase** — Reviewer protocols
- **archeflow:shadow-detection** — Recognizing and handling dysfunction
- **archeflow:custom-archetypes** — Creating domain-specific roles
- **archeflow:workflow-design** — Designing custom PDCA workflows
- **archeflow:autonomous-mode** — Unattended overnight sessions with full visibility