Christian Nennemann
5139f1ad89
- Mini-Reflect for fast workflow: Creator must restate task, list assumptions, name highest-damage risk before proposing (catches misunderstandings early) - Alternatives Considered section: Creator must evaluate 2+ approaches with rejection rationale before committing to one (prevents tunnel vision) - Structured confidence scoring: 3-axis table (task understanding, solution completeness, risk coverage) replaces bare 0.0-1.0 number. Low scores trigger targeted action (clarify, upgrade workflow, or research) - Mini-Reflect fallback for skipped tasks: quick reflection even when ArcheFlow doesn't activate (non-trivial single-file changes)
3.3 KiB
3.3 KiB
name, description
| name | description |
|---|---|
| using-archeflow | Use at session start when implementing features, reviewing code, debugging, or any task that benefits from multiple perspectives. Activates ArcheFlow multi-agent orchestration. |
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)
Mini-Reflect fallback: Even when skipping ArcheFlow, apply a quick reflection for non-trivial single-file changes: (1) restate what you're changing, (2) name one assumption, (3) check if it could break anything. This takes ~10 seconds and catches misunderstandings before they become commits.
Archetypes
| 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
Plan → Explorer researches, Creator proposes
Do → Maker implements in isolated worktree
Check → Reviewers assess in parallel (approve/reject)
Act → All approved? Merge. Issues? Cycle back to Plan.
Quick Start
When the user gives an implementation task:
- Assess: does this need ArcheFlow? (see criteria above)
- If yes: load
archeflow:orchestrationskill - Pick workflow (fast/standard/thorough)
- Execute the PDCA steps from the orchestration skill
Skills Reference
- archeflow:orchestration — Step-by-step execution guide (load this to run)
- archeflow:plan-phase / do-phase / check-phase — Phase protocols
- 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