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

feat: core improvements — feedback loop, attention filters, shadow heuristics, metrics, auto-activation

Browse Source 
- Cross-cycle feedback protocol with structured finding format, routing, and resolution tracking
- Attention filter enforcement: explicit context include/exclude per archetype
- Shadow detection: quantitative checklists with concrete thresholds
- Orchestration metrics: per-phase timing, agent count, findings summary
- Autonomous mode wiring: checkpoint protocol, session log, stop conditions
- Auto-activation: SessionStart hook fires ArcheFlow for implementation tasks without user config
- Emoji avatars for all 7 archetypes
- Standardized finding format across all reviewers for cross-cycle tracking
- Persisted implementation plan in docs/
This commit is contained in:
Christian Nennemann
2026-04-03 06:02:10 +02:00
parent eec1fc3d82
commit d08dc657d1
14 changed files with 553 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -3,21 +3,50 @@ name: using-archeflow
description: Use at session start when implementing features, reviewing code, debugging, or any task that benefits from multiple perspectives. Activates ArcheFlow multi-agent orchestration.
---
# ArcheFlow
# ArcheFlow — Active
Multi-agent orchestration using archetypal roles and PDCA quality cycles.
## IMPORTANT: When to Activate
You MUST use ArcheFlow orchestration (load `archeflow:orchestration` skill and follow its steps) for any task that matches:
- **New features** — any feature touching 2+ files
- **Refactoring** — structural changes across modules
- **Security-sensitive changes** — auth, encryption, input handling, API keys
- **Bug fixes with unclear root cause** — use Explorer to investigate first
- **Code review requests** — spawn Guardian + relevant reviewers
- **Multi-file changes** — anything beyond a single-file edit
Choose the workflow based on risk:
| Signal | Workflow | Command |
|--------|----------|---------|
| Small fix, low risk, single concern | `fast` | Creator → Maker → Guardian |
| Feature, multiple files, moderate risk | `standard` | Explorer + Creator → Maker → Guardian + Skeptic + Sage |
| Security-sensitive, breaking changes, public API | `thorough` | Explorer + Creator → Maker → All 4 reviewers |
## When to Skip ArcheFlow
Do NOT use ArcheFlow for these — just do them directly:
- Single-line fixes, typos, formatting
- Answering questions (no code changes)
- Reading/exploring code without making changes
- Config changes to a single file
- Git operations (commit, push, branch)
## Archetypes
| Archetype | Virtue | Shadow | Phase |
|-----------|--------|--------|-------|
| **Explorer** | Contextual Clarity | Rabbit Hole | Plan |
| **Creator** | Decisive Framing | Over-Architect | Plan |
| **Maker** | Execution Discipline | Rogue | Do |
| **Guardian** | Threat Intuition | Paranoid | Check |
| **Skeptic** | Assumption Surfacing | Paralytic | Check |
| **Trickster** | Adversarial Creativity | False Alarm | Check |
| **Sage** | Maintainability Judgment | Bureaucrat | Check |
| Archetype | Avatar | Virtue | Shadow | Phase |
|-----------|--------|--------|--------|-------|
| **Explorer** | 🔍 | Contextual Clarity | Rabbit Hole | Plan |
| **Creator** | 🏗️ | Decisive Framing | Over-Architect | Plan |
| **Maker** | ⚒️ | Execution Discipline | Rogue | Do |
| **Guardian** | 🛡️ | Threat Intuition | Paranoid | Check |
| **Skeptic** | 🤔 | Assumption Surfacing | Paralytic | Check |
| **Trickster** | 🃏 | Adversarial Creativity | False Alarm | Check |
| **Sage** | 📚 | Maintainability Judgment | Bureaucrat | Check |
## PDCA Cycle
@@ -28,24 +57,20 @@ Check → Reviewers assess in parallel (approve/reject)
Act → All approved? Merge. Issues? Cycle back to Plan.
```
## Workflows
## Quick Start
| Workflow | Archetypes | Cycles |
|----------|-----------|:------:|
| `fast` | Creator → Maker → Guardian | 1 |
| `standard` | Explorer + Creator → Maker → Guardian + Skeptic + Sage | 2 |
| `thorough` | Explorer + Creator → Maker → All 4 reviewers | 3 |
When the user gives an implementation task:
## When to Use
1. Assess: does this need ArcheFlow? (see criteria above)
2. If yes: load `archeflow:orchestration` skill
3. Pick workflow (fast/standard/thorough)
4. Execute the PDCA steps from the orchestration skill
**Use** for features spanning multiple files, security-sensitive changes, or when multiple perspectives help.
**Skip** for single-file fixes, formatting, or purely informational tasks.
## Skills Reference
## Skills
- **archeflow:orchestration** — Step-by-step execution guide
- **archeflow:orchestration** — Step-by-step execution guide (load this to run)
- **archeflow:plan-phase** / **do-phase** / **check-phase** — Phase protocols
- **archeflow:shadow-detection** — Recognizing dysfunction
- **archeflow:shadow-detection** — Recognizing and correcting dysfunction
- **archeflow:attention-filters** — What context each archetype receives
- **archeflow:autonomous-mode** — Unattended sessions
- **archeflow:custom-archetypes** / **workflow-design** — Extending ArcheFlow