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.

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

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

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.