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

29
skills/plan-phase/SKILL.md
View File

@@ -32,11 +32,21 @@ Explorer researches, then Creator designs. Sequential — Creator needs Explorer
```markdown
## Proposal: <task>
**Confidence:** <0.0 to 1.0>
### Mini-Reflect (fast workflow only — skip if Explorer ran)
- **Task restated:** <one sentence>
- **Assumptions:** 1) ... 2) ... 3) ...
- **Highest-damage risk:** <the one thing that would hurt most if wrong>
### Architecture Decision
<What and WHY>
### Alternatives Considered
| Approach | Why Rejected |
|----------|-------------|
| <option A> | <reason> |
| <option B> | <reason> |
### Changes
1. **`path/file.ext`** — What changes and why
2. **`path/test.ext`** — What tests to add
@@ -44,6 +54,13 @@ Explorer researches, then Creator designs. Sequential — Creator needs Explorer
### Test Strategy
- <specific test cases>
### Confidence
| Axis | Score | Note |
|------|-------|------|
| Task understanding | <0.0-1.0> | <why> |
| Solution completeness | <0.0-1.0> | <gaps?> |
| Risk coverage | <0.0-1.0> | <unknowns?> |
### Risks
- <what could go wrong + mitigations>
@@ -51,13 +68,14 @@ Explorer researches, then Creator designs. Sequential — Creator needs Explorer
- <adjacent concerns deliberately excluded>
```
**Confidence triggers:** If any axis scores below 0.5, flag it to the orchestrator. Low task understanding → clarify with user. Low solution completeness → consider standard workflow. Low risk coverage → spawn targeted Explorer research.
## Creator with Prior Feedback (Cycle 2+)
When the Creator receives structured feedback from a prior cycle, the proposal must include an additional section addressing each unresolved issue:
```markdown
## Proposal: <task> (Revision — Cycle N)
**Confidence:** <0.0 to 1.0>
### Prior Feedback Response
| Issue | Source | Action | Rationale |
@@ -75,6 +93,13 @@ When the Creator receives structured feedback from a prior cycle, the proposal m
### Test Strategy
<updated test cases>
### Confidence
| Axis | Score | Note |
|------|-------|------|
| Task understanding | <0.0-1.0> | <why> |
| Solution completeness | <0.0-1.0> | <gaps?> |
| Risk coverage | <0.0-1.0> | <unknowns?> |
### Risks
<updated risks — include any new risks from the revision>