refactor: one shadow per archetype, trim bootstrap skill
- Consolidate to single shadow per archetype (fold best bits from dropped shadows into the remaining one) - Trim bootstrap skill from 515 to 254 words (~50% token reduction) - Remove redundant shadow table from bootstrap (already in archetype table)
This commit is contained in:
@@ -1,96 +1,50 @@
|
||||
---
|
||||
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.
|
||||
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 — Multi-Agent Orchestration
|
||||
# ArcheFlow
|
||||
|
||||
You have ArcheFlow installed. ArcheFlow gives you a structured way to coordinate multiple agents through quality cycles using Jungian archetypes as behavioral protocols.
|
||||
Multi-agent orchestration using archetypal roles and PDCA quality cycles.
|
||||
|
||||
## How It Works
|
||||
## Archetypes
|
||||
|
||||
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 | Shadow | Phase |
|
||||
|-----------|--------|--------|-------|
|
||||
| **Explorer** | Contextual Clarity | Rabbit Hole | Plan |
|
||||
| **Creator** | Decisive Framing | Perfectionist | Plan |
|
||||
| **Maker** | Execution Discipline | Cowboy | Do |
|
||||
| **Guardian** | Threat Intuition | Paranoid | Check |
|
||||
| **Skeptic** | Assumption Surfacing | Paralytic | Check |
|
||||
| **Trickster** | Adversarial Creativity | Saboteur | Check |
|
||||
| **Sage** | Maintainability Judgment | Bureaucrat | Check |
|
||||
|
||||
| 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:
|
||||
## PDCA Cycle
|
||||
|
||||
```
|
||||
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
|
||||
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.
|
||||
```
|
||||
|
||||
Each cycle builds on feedback from the last.
|
||||
## Workflows
|
||||
|
||||
## When to Use ArcheFlow
|
||||
| Workflow | Archetypes | Cycles |
|
||||
|----------|-----------|:------:|
|
||||
| `fast` | Creator → Maker → Guardian | 1 |
|
||||
| `standard` | Explorer + Creator → Maker → Guardian + Skeptic + Sage | 2 |
|
||||
| `thorough` | Explorer + Creator → Maker → All 4 reviewers | 3 |
|
||||
|
||||
**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
|
||||
## When to Use
|
||||
|
||||
**SKIP IT when:**
|
||||
- Single-file typo fix or formatting change
|
||||
- User explicitly wants quick-and-dirty
|
||||
- Task is purely informational (reading, explaining)
|
||||
**Use** for features spanning multiple files, security-sensitive changes, or when multiple perspectives help.
|
||||
**Skip** for single-file fixes, formatting, or purely informational tasks.
|
||||
|
||||
## Built-in Workflows
|
||||
## Skills
|
||||
|
||||
| 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
|
||||
- **archeflow:orchestration** — Step-by-step execution guide
|
||||
- **archeflow:plan-phase** / **do-phase** / **check-phase** — Phase protocols
|
||||
- **archeflow:shadow-detection** — Recognizing dysfunction
|
||||
- **archeflow:autonomous-mode** — Unattended sessions
|
||||
- **archeflow:custom-archetypes** / **workflow-design** — Extending ArcheFlow
|
||||
|
||||
Reference in New Issue
Block a user