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

6
skills/autonomous-mode/SKILL.md
View File

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