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

# ArcheFlow — Active

Multi-agent orchestration using archetypal roles and PDCA quality cycles.

## IMPORTANT: When to Activate

You MUST use ArcheFlow orchestration (load `archeflow:orchestration` skill and follow its steps) for any task that matches:

- **New features** — any feature touching 2+ files
- **Refactoring** — structural changes across modules
- **Security-sensitive changes** — auth, encryption, input handling, API keys
- **Bug fixes with unclear root cause** — use Explorer to investigate first
- **Code review requests** — spawn Guardian + relevant reviewers
- **Multi-file changes** — anything beyond a single-file edit

Choose the workflow based on risk:

| Signal | Workflow | Command |
|--------|----------|---------|
| Small fix, low risk, single concern | `fast` | Creator → Maker → Guardian |
| Feature, multiple files, moderate risk | `standard` | Explorer + Creator → Maker → Guardian + Skeptic + Sage |
| Security-sensitive, breaking changes, public API | `thorough` | Explorer + Creator → Maker → All 4 reviewers |

## When to Skip ArcheFlow

Do NOT use ArcheFlow for these — just do them directly:

- Single-line fixes, typos, formatting
- Answering questions (no code changes)
- Reading/exploring code without making changes
- Config changes to a single file
- Git operations (commit, push, branch)

## Archetypes

| Archetype | Avatar | Virtue | Shadow | Phase |
|-----------|--------|--------|--------|-------|
| **Explorer** | 🔍 | Contextual Clarity | Rabbit Hole | Plan |
| **Creator** | 🏗️ | Decisive Framing | Over-Architect | Plan |
| **Maker** | ⚒️ | Execution Discipline | Rogue | Do |
| **Guardian** | 🛡️ | Threat Intuition | Paranoid | Check |
| **Skeptic** | 🤔 | Assumption Surfacing | Paralytic | Check |
| **Trickster** | 🃏 | Adversarial Creativity | False Alarm | Check |
| **Sage** | 📚 | Maintainability Judgment | Bureaucrat | Check |

## PDCA Cycle

```
Plan  → Explorer researches, Creator proposes
Do    → Maker implements in isolated worktree
Check → Reviewers assess in parallel (approve/reject)
Act   → All approved? Merge. Issues? Cycle back to Plan.
```

## Quick Start

When the user gives an implementation task:

1. Assess: does this need ArcheFlow? (see criteria above)
2. If yes: load `archeflow:orchestration` skill
3. Pick workflow (fast/standard/thorough)
4. Execute the PDCA steps from the orchestration skill

## Skills Reference

- **archeflow:orchestration** — Step-by-step execution guide (load this to run)
- **archeflow:plan-phase** / **do-phase** / **check-phase** — Phase protocols
- **archeflow:shadow-detection** — Recognizing and correcting dysfunction
- **archeflow:attention-filters** — What context each archetype receives
- **archeflow:autonomous-mode** — Unattended sessions
- **archeflow:custom-archetypes** / **workflow-design** — Extending ArcheFlow