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

feat: Ralph Loop integration — mini-reflect, alternatives, structured confidence

Browse Source 
- 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)
This commit is contained in:
Christian Nennemann
2026-04-03 06:08:01 +02:00
parent df0c81ae89
commit 5139f1ad89
3 changed files with 44 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
skills/orchestration/SKILL.md
View File

@@ -47,19 +47,30 @@ Agent(
**Context to include:** Task description, Explorer's research output. On cycle 2+: prior cycle's structured feedback (see Cycle Feedback Protocol).
**Context to exclude:** Raw file contents (Explorer already summarized), git diffs, reviewer full outputs.
**Fast workflow only (no Explorer):** The Creator must perform a Mini-Reflect before proposing:
1. Restate the task in your own words (catch misunderstandings early)
2. List 3 assumptions you're making
3. Name the one risk that would cause most damage if wrong
```
Agent(
description: "🏗️ Creator: design proposal",
prompt: "<task description>
You are the CREATOR archetype.
Based on the research findings: <Explorer's output>
<if fast workflow (no Explorer): Before proposing, perform a Mini-Reflect:
1. Restate the task in one sentence
2. List 3 assumptions you're making
3. Name the highest-damage risk
Then propose.>
<if standard/thorough: Based on the research findings: <Explorer's output>>
<if cycle 2+: Prior cycle feedback: <structured feedback — see Cycle Feedback Protocol>>
Design a solution proposal including:
1. Architecture decisions (with rationale)
2. Files to create/modify (with specific changes)
3. Test strategy
4. Confidence score (0.0 to 1.0)
5. Risks you foresee
3. Alternatives considered (at least 2, with rejection rationale)
4. Test strategy
5. Confidence (scored by axis: task understanding, solution completeness, risk coverage)
6. Risks you foresee
<if cycle 2+: 6. How you addressed each unresolved issue from prior feedback>
Be decisive. Ship a clear plan, not a menu of options.",
subagent_type: "Plan"