Files
claude-archeflow-plugin/skills/using-archeflow/SKILL.md
Christian Nennemann 130c04fa58 feat: corrective action framework + CLAUDE.md rewrite + v0.8.0 cleanup
- Extend shadow-detection with 3-layer corrective action framework:
  archetype shadows, system shadows (tunnel vision, echo chamber, etc.),
  and policy boundaries (checkpoints, budget gates, circuit breakers)
- Rewrite CLAUDE.md with proper guardrails (DO/DO NOT, skill writing rules,
  200-line max per skill, no bash pseudo-code in skills)
- Update plugin.json to v0.8.0 with consolidated 19-skill list
- Update README architecture tree and skills reference
- Update using-archeflow version string to v0.8.0 / 19 skills
- Remove 8 empty skill directories (absorbed into run skill)
2026-04-06 20:52:27 +02:00

56 lines
2.2 KiB
Markdown

---
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 -- Active
On activation, print ONE line then proceed silently:
```
archeflow v0.8.0 · 19 skills · <domain> domain
```
Domain auto-detected: `writing` if `colette.yaml` exists, `research` if paper/thesis files, `code` otherwise.
## When to Use What
| Need | Command | When |
|------|---------|------|
| **Work the queue** | `/af-sprint` | Multiple tasks pending across projects, "run the sprint" |
| **Deep orchestration** | `/af-run` | Writing/research tasks, security-sensitive code, complex multi-module refactors |
| **Code review** | `/af-review` | Review diff/branch/commits before merging, security-sensitive changes |
| **Single feature** | `feature-dev` or direct | Clear scope, one project -- no orchestration needed |
## When to Skip ArcheFlow
Do NOT use for: single-line fixes, questions, reading/exploring, config tweaks, git ops.
## Workflow Selection
| Signal | Workflow | Pipeline |
|--------|----------|----------|
| Small fix, low risk | `fast` | Creator --> Maker --> Guardian |
| Feature, multi-file, moderate risk | `standard` | Explorer + Creator --> Maker --> Guardian + Skeptic + Sage |
| Security, breaking changes, public API | `thorough` | Explorer + Creator --> Maker --> All 4 reviewers |
## Available Commands
| Command | What it does |
|---------|-------------|
| `/af-sprint` | Queue-driven parallel agent runner (primary mode) |
| `/af-run <task>` | PDCA orchestration loop (`--dry-run`, `--start-from`, `--workflow`) |
| `/af-review` | Guardian-led code review on diff/branch/range |
| `/af-status` | Current run state, active agents, findings |
| `/af-report` | Full process report for a run |
| `/af-init` | Initialize ArcheFlow in a project |
| `/af-score` | Archetype effectiveness scores |
| `/af-memory` | Cross-run lesson memory |
| `/af-fanout` | Colette book fanout via agents |
| `/af-dag` | DAG of current/last run |
## Mini-Reflect Fallback
Even when skipping ArcheFlow, apply for non-trivial changes:
1. Restate what you're changing
2. Name one assumption
3. Check if it could break anything