c/claude-archeflow-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: remove ArcheHelix branding, use plain PDCA language

Browse Source 
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:
Christian Nennemann
2026-04-02 18:09:28 +00:00
parent a6fa708f8b
commit 21becd8b58
7 changed files with 29 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
skills/using-archeflow/SKILL.md
View File

@@ -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