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

refactor: refocus ArcheFlow as workspace orchestrator, not feature-dev competitor

Browse Source 
- README: lead with af-sprint (parallel multi-project), af-review (post-impl quality)
- Sprint skill: L/XL code tasks use feature-dev style (explore→plan→impl→self-review)
  instead of PDCA. Reserve PDCA for writing/research domains.
- Session start: route to af-sprint/af-review/af-run based on task type
- Explicitly state: for single-feature dev, use feature-dev plugin instead
This commit is contained in:
Christian Nennemann
2026-04-04 18:44:18 +02:00
parent 1bf1376a80
commit e19ff0acc3
3 changed files with 115 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
skills/sprint/SKILL.md
View File

@@ -105,11 +105,44 @@ For each task in the batch, decide the execution strategy:
| Signal | Strategy | What happens |
|--------|----------|-------------|
| Estimate S, clear scope | **Direct** | Spawn Agent() with task description, no orchestration |
| Estimate M, multi-file | **Pipeline** | Spawn Agent() with af-run --strategy pipeline |
| Estimate L/XL, complex | **PDCA** | Spawn Agent() with af-run --strategy pdca |
| Estimate M, multi-file | **Direct+** | Spawn Agent() with task + "read code first, run tests after" |
| Estimate L/XL, code | **Feature-dev style** | Agent explores → implements → self-reviews (see below) |
| Estimate L/XL, writing | **PDCA** | Use af-run with writing domain archetypes |
| Task contains "validate", "test", "lint", "check" | **Direct** | Cheap analytical task, no orchestration |
| Task contains "review", "audit", "security" | **Review** | Spawn Guardian + relevant reviewers only |
### L/XL Code Task Template (feature-dev style)
For complex code tasks, give the agent a structured process instead of PDCA:
```
Agent(
description: "<project>: <task-short>",
prompt: "You are working on project <project> at <path>.
Task: <task description>
Follow this process:
1. EXPLORE: Read CLAUDE.md, docs/status.md, and the relevant source files.
Understand existing patterns before writing anything.
2. PLAN: Identify 2-3 files to change. Write a brief plan (what, where, why).
If ambiguous, list your assumptions.
3. IMPLEMENT: Make the changes. Follow existing code patterns strictly.
4. TEST: Run the project's test suite. Fix any failures.
5. SELF-REVIEW: Before committing, re-read your diff. Check:
- Error handling: what happens when this fails?
- Protocol compliance: am I using the right function signatures?
- Tests: did I test the important paths?
6. COMMIT + PUSH: Conventional commits, signed, pushed.
<standard rules>
STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED"
)
```
This gives the agent feature-dev's structured exploration without the multi-agent overhead.
For writing/research L/XL tasks, use af-run instead — archetypes add value where linters don't exist.
**Agent spawn template:**
For each task in the batch, spawn an Agent in the SAME message (parallel dispatch):