chore: remove ArcheHelix branding, use plain PDCA language

The archetypes and shadows are distinctive enough — no need for
a fancy name on top of the standard PDCA cycle terminology.
This commit is contained in:
2026-04-02 18:09:28 +00:00
parent a6fa708f8b
commit 21becd8b58
7 changed files with 29 additions and 29 deletions

View File

@@ -2,11 +2,11 @@
**Multi-agent orchestration with Jungian archetypes for Claude Code.**
ArcheFlow gives Claude Code a structured way to coordinate multiple agents through quality cycles. Instead of one agent doing everything, specialized archetypes collaborate through the **ArcheHelix** — a rising PDCA spiral where each iteration builds on feedback from the last.
ArcheFlow gives Claude Code a structured way to coordinate multiple agents through quality cycles. Instead of one agent doing everything, specialized archetypes collaborate through **PDCA cycles** — Plan, Do, Check, Act — where each iteration builds on feedback from the last.
Zero dependencies. No build step. Just install and go.
## The ArcheHelix
## The PDCA Cycle
```
Act ──────────── Done ✓
@@ -26,7 +26,7 @@ Zero dependencies. No build step. Just install and go.
│ Plan ← Cycle 1
```
Each turn of the helix produces better results. No unreviewed code reaches your main branch.
Each cycle produces better results. No unreviewed code reaches your main branch.
## The Seven Archetypes
@@ -44,7 +44,7 @@ Every archetype has a **shadow** — the destructive inversion of its strength.
## Built-in Workflows
| Workflow | ArcheHelix Turns | Archetypes | Best For |
| Workflow | Cycles | Archetypes | Best For |
|----------|:---:|------------|----------|
| `fast` | 1 | Creator → Maker → Guardian | Bug fixes, small changes |
| `standard` | 2 | Explorer + Creator → Maker → Guardian + Skeptic + Sage | Features, refactors |
@@ -54,7 +54,7 @@ Every archetype has a **shadow** — the destructive inversion of its strength.
ArcheFlow can run fully unattended — queue your tasks, walk away, read the results in the morning:
- **Self-organizing:** Archetypes coordinate through the ArcheHelix without human input
- **Self-organizing:** Archetypes coordinate through PDCA cycles without human input
- **Self-correcting:** Failed reviews trigger automatic revision cycles
- **Safe:** All code stays on worktree branches until all reviewers approve
- **Visible:** Full session log with every decision, finding, and merge
@@ -81,14 +81,14 @@ archeflow/
├── .claude-plugin/plugin.json # Plugin manifest
├── skills/
│ ├── using-archeflow/ # Bootstrap — loaded at session start
│ ├── orchestration/ # Step-by-step ArcheHelix execution
│ ├── orchestration/ # Step-by-step PDCA execution
│ ├── plan-phase/ # Explorer + Creator protocols
│ ├── do-phase/ # Maker implementation rules
│ ├── check-phase/ # Reviewer protocols (all 4)
│ ├── shadow-detection/ # Recognizing and correcting dysfunction
│ ├── autonomous-mode/ # Unattended overnight sessions
│ ├── custom-archetypes/ # Creating domain-specific roles
│ └── workflow-design/ # Designing custom ArcheHelix workflows
│ └── workflow-design/ # Designing custom workflows
├── agents/
│ ├── explorer.md # Research agent (Haiku)
│ ├── creator.md # Design agent (Sonnet)
@@ -131,10 +131,10 @@ Add domain-specific roles (database reviewer, compliance auditor, etc.):
```
### Custom Workflows
Design your own ArcheHelix configuration:
Design your own workflow:
```yaml
# .archeflow/workflows/api-design.yaml
archehelix:
pdca:
plan: { archetypes: [explorer, creator] }
do: { archetypes: [maker] }
check: { archetypes: [guardian, skeptic, trickster] }
@@ -147,7 +147,7 @@ ArcheFlow is built on three beliefs:
1. **Strength has a shadow.** Every capability becomes destructive when unchecked. The Explorer who won't stop researching. The Guardian who blocks everything. The Maker who ships without review. ArcheFlow names these shadows and corrects them.
2. **Quality is a spiral, not a gate.** A single review pass misses things. The ArcheHelix spirals upward — each cycle catches what the previous one missed, until the reviewers have nothing left to find.
2. **Quality is a spiral, not a gate.** A single review pass misses things. PDCA cycles spiral upward — each cycle catches what the previous one missed, until the reviewers have nothing left to find.
3. **Autonomy needs structure.** Agents left to their own devices produce mediocre results. Agents given clear roles, typed communication, and quality gates produce exceptional work — even overnight, even unattended.