From 21becd8b58eb4eb5a49a8f21b87a7b8c77814526 Mon Sep 17 00:00:00 2001 From: Christian Nennemann Date: Thu, 2 Apr 2026 18:09:28 +0000 Subject: [PATCH] chore: remove ArcheHelix branding, use plain PDCA language MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The archetypes and shadows are distinctive enough — no need for a fancy name on top of the standard PDCA cycle terminology. --- README.md | 20 ++++++++++---------- examples/custom-workflow.yaml | 4 ++-- examples/feature-implementation.md | 4 ++-- examples/security-review.md | 4 ++-- skills/autonomous-mode/SKILL.md | 6 +++--- skills/using-archeflow/SKILL.md | 8 ++++---- skills/workflow-design/SKILL.md | 12 ++++++------ 7 files changed, 29 insertions(+), 29 deletions(-) diff --git a/README.md b/README.md index c273836..2981de6 100644 --- a/README.md +++ b/README.md @@ -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. diff --git a/examples/custom-workflow.yaml b/examples/custom-workflow.yaml index 4d47ec6..08b95ff 100644 --- a/examples/custom-workflow.yaml +++ b/examples/custom-workflow.yaml @@ -4,8 +4,8 @@ name: api-design description: "API-first workflow with contract validation and adversarial testing" -# The ArcheHelix configuration -archehelix: +# PDCA workflow configuration +pdca: plan: archetypes: [explorer, creator] parallel: false # sequential: Explorer feeds Creator diff --git a/examples/feature-implementation.md b/examples/feature-implementation.md index 6be74da..4db8d94 100644 --- a/examples/feature-implementation.md +++ b/examples/feature-implementation.md @@ -1,4 +1,4 @@ -# Example: Feature Implementation (Standard ArcheHelix) +# Example: Feature Implementation (Standard Workflow) ## Task "Add rate limiting to the API authentication endpoint" @@ -41,4 +41,4 @@ - 8 tests added (including real Redis failure simulation) - Rate limiting active on 3 auth routes - Documentation updated -- 2 ArcheHelix cycles, standard workflow +- 2 PDCA cycles, standard workflow diff --git a/examples/security-review.md b/examples/security-review.md index 11e3f2c..9eb4634 100644 --- a/examples/security-review.md +++ b/examples/security-review.md @@ -1,4 +1,4 @@ -# Example: Security Review (Thorough ArcheHelix) +# Example: Security Review (Thorough Workflow) ## Task "Review the new file upload endpoint for security issues" @@ -54,5 +54,5 @@ After Creator revises and Maker fixes all findings... - Virus scanner circuit breaker added - Zero-byte file handling added - Unicode filename normalization added -- 3 ArcheHelix cycles, thorough workflow +- 3 PDCA cycles, thorough workflow - 5 CRITICAL findings caught before production diff --git a/skills/autonomous-mode/SKILL.md b/skills/autonomous-mode/SKILL.md index 5171e8b..f5a5b04 100644 --- a/skills/autonomous-mode/SKILL.md +++ b/skills/autonomous-mode/SKILL.md @@ -3,13 +3,13 @@ name: autonomous-mode description: Use when the user wants to run ArcheFlow orchestrations unattended — overnight sessions, batch processing multiple tasks, or fully autonomous coding. Handles self-organization, progress logging, and safe stopping. --- -# Autonomous Mode — Unattended ArcheHelix +# Autonomous Mode ArcheFlow orchestrations can run fully autonomously because the archetypes self-organize through the PDCA cycle. The user sets the task queue, walks away, and reviews results later. ## How Autonomous Mode Works -The ArcheHelix provides natural quality gates at every turn of the spiral: +The PDCA cycle provides natural quality gates at every turn of the spiral: - **Plan** phase produces a proposal — reviewable artifact - **Do** phase produces committed code in a worktree — isolated, reversible - **Check** phase produces approval/rejection — automatic quality control @@ -29,7 +29,7 @@ Task queue: 4. "Add rate limiting to public endpoints" (standard) Rules: -- Process tasks sequentially (one ArcheHelix at a time) +- Process tasks sequentially (one orchestration at a time) - Log progress to .archeflow/session-log.md after each task - If a task fails after max cycles: log findings, skip to next task - If 3 consecutive tasks fail: STOP and wait for user diff --git a/skills/using-archeflow/SKILL.md b/skills/using-archeflow/SKILL.md index 5e9189a..1b278f1 100644 --- a/skills/using-archeflow/SKILL.md +++ b/skills/using-archeflow/SKILL.md @@ -21,9 +21,9 @@ Instead of one agent doing everything, ArcheFlow splits work across **archetypal | **Trickster** | Adversarial tester — finds edge cases, breaks things | Edge case challenges | | **Sage** | Senior reviewer — holistic quality judgment | Quality report (approve/reject) | -## The ArcheHelix — Rising Quality Spiral +## PDCA Quality Cycles -Work flows through **Plan → Do → Check → Act** in a rising spiral called the **ArcheHelix**. Each cycle incorporates feedback from the previous one: +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 @@ -36,7 +36,7 @@ Act: All approved? → Merge and done Issues found? → Spiral up: feed back to Plan, cycle again ``` -The helix ensures that every iteration is better than the last — not just repeated. +Each cycle builds on feedback from the last. ## When to Use ArcheFlow @@ -65,7 +65,7 @@ The helix ensures that every iteration is better than the last — not just repe 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 the PDCA cycle +3. Managing PDCA cycles 4. Merging results ## Shadow Detection diff --git a/skills/workflow-design/SKILL.md b/skills/workflow-design/SKILL.md index 9486a7a..a277768 100644 --- a/skills/workflow-design/SKILL.md +++ b/skills/workflow-design/SKILL.md @@ -1,11 +1,11 @@ --- name: workflow-design -description: Use when designing custom orchestration workflows — choosing which archetypes run in each PDCA phase, setting exit conditions, and configuring the ArcheHelix cycle. +description: Use when designing custom orchestration workflows — choosing which archetypes run in each PDCA phase, setting exit conditions, and configuring PDCA cycles. --- -# Workflow Design — The ArcheHelix +# Workflow Design — PDCA Cycles -ArcheFlow's PDCA cycles spiral upward through iterations — each cycle incorporates feedback from the previous one, producing progressively better results. We call this the **ArcheHelix**: a rising spiral of Plan → Do → Check → Act, where each turn is informed by all previous turns. +ArcheFlow's PDCA cycles spiral upward through iterations — each cycle incorporates feedback from the previous one, producing progressively better results. Each cycle incorporates feedback from the previous one. ``` ╱ Act ──────────── Done ✓ @@ -36,7 +36,7 @@ Act: Approve or reject (1 cycle max) ``` **Use for:** Bug fixes, small changes, low-risk tasks. -### `standard` — Double Helix +### `standard` — Two Cycles ``` Plan: Explorer researches → Creator designs Do: Maker implements (worktree) @@ -45,7 +45,7 @@ Act: Approve or cycle (2 cycles max) ``` **Use for:** Features, refactors, moderate-risk changes. -### `thorough` — Triple Helix +### `thorough` — Three Cycles ``` Plan: Explorer researches → Creator designs Do: Maker implements (worktree) @@ -132,7 +132,7 @@ Exit: no_critical, max 1 cycle ## Anti-Patterns - **Kitchen sink:** Putting all 7 archetypes in Check. Most can't add value simultaneously. -- **Infinite helix:** maxCycles > 4 burns tokens without convergence. +- **Runaway cycles:** maxCycles > 4 burns tokens without convergence. - **Reviewerless Do:** Skipping Check phase "to save time." You'll pay in bugs. - **Maker in Plan:** Maker should implement from a proposal, not design on the fly. - **Solo orchestration:** One archetype in every phase. That's just a single agent with extra steps.