claude-prism 0.7.0 → 0.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -21
- package/package.json +1 -1
- package/templates/rules.md +10 -7
package/README.md
CHANGED
|
@@ -1,12 +1,9 @@
|
|
|
1
1
|
```
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
/ / ─── C Checkpoint
|
|
8
|
-
/__/ ── H Handoff
|
|
9
|
-
spectrum
|
|
2
|
+
╱╲
|
|
3
|
+
━━━━━━━━━▶ ╱ ╲ ── U Understand
|
|
4
|
+
complex ╱ ╲ ── D Decompose
|
|
5
|
+
problem ╱ PRISM╲── E Execute
|
|
6
|
+
╱________╲─ C Checkpoint
|
|
10
7
|
```
|
|
11
8
|
|
|
12
9
|
[](https://www.npmjs.com/package/claude-prism)
|
|
@@ -19,7 +16,7 @@
|
|
|
19
16
|
|
|
20
17
|
**UDEC methodology framework for AI coding agents.**
|
|
21
18
|
|
|
22
|
-
Installs the UDEC methodology —
|
|
19
|
+
Installs the UDEC methodology — **Understand, Decompose, Execute, Checkpoint** — directly into your project's Claude Code environment. Includes an entry protocol (Assess) and session transition protocol (Handoff) that bookend the core cycle. Three lightweight hooks enforce the methodology where it matters most.
|
|
23
20
|
|
|
24
21
|
## The Problem
|
|
25
22
|
|
|
@@ -27,7 +24,7 @@ AI coding agents fail in predictable ways:
|
|
|
27
24
|
|
|
28
25
|
| Failure Mode | What Happens | UDEC Fix |
|
|
29
26
|
|---|---|---|
|
|
30
|
-
| Skip understanding | Builds the wrong thing for 30 minutes |
|
|
27
|
+
| Skip understanding | Builds the wrong thing for 30 minutes | UNDERSTAND phase |
|
|
31
28
|
| No decomposition | One massive change that's hard to review | DECOMPOSE into verifiable batches |
|
|
32
29
|
| No verification | "should work" without evidence | Risk-based verification strategy |
|
|
33
30
|
| Scope creep | "While I'm here..." changes nobody asked for | Scope Guard in methodology |
|
|
@@ -46,17 +43,23 @@ AI coding agents fail in predictable ways:
|
|
|
46
43
|
Injected into `CLAUDE.md`, UDEC is a behavioral framework that corrects how AI agents approach tasks:
|
|
47
44
|
|
|
48
45
|
```
|
|
49
|
-
ASSESS ─── Classify: bugfix / feature / migration / refactor / investigation
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
46
|
+
ASSESS ─── Classify: bugfix / feature / migration / refactor / investigation
|
|
47
|
+
│ (entry protocol)
|
|
48
|
+
▼
|
|
49
|
+
┌─────────────────── UDEC Core Cycle ───────────────────┐
|
|
50
|
+
│ UNDERSTAND ── Sufficiency assessment → ask → align │
|
|
51
|
+
│ │ │
|
|
52
|
+
│ DECOMPOSE ── Batches → plan file for 6+ files → [S][M][L] │
|
|
53
|
+
│ │ │
|
|
54
|
+
│ EXECUTE ── Adaptive batches → risk-based verification │
|
|
55
|
+
│ │ │
|
|
56
|
+
│ CHECKPOINT ── Report with evidence → get approval ─────┤
|
|
57
|
+
│ (loops back for next batch) │
|
|
58
|
+
└────────────────────────────────────────────────────────┘
|
|
59
|
+
│
|
|
60
|
+
▼
|
|
61
|
+
HANDOFF ── Session transition doc → next steps
|
|
62
|
+
(exit protocol)
|
|
60
63
|
```
|
|
61
64
|
|
|
62
65
|
**Task-type aware**: Each task type (bugfix, feature, migration, refactor, investigation) follows a different optimal path. Migrations skip per-file decomposition. Bugfixes skip straight to locate-fix-verify. Investigations skip decomposition entirely.
|
package/package.json
CHANGED
package/templates/rules.md
CHANGED
|
@@ -1,6 +1,9 @@
|
|
|
1
1
|
|
|
2
2
|
<!-- PRISM:START -->
|
|
3
|
-
# Prism
|
|
3
|
+
# Prism — UDEC Methodology Framework
|
|
4
|
+
|
|
5
|
+
**UDEC = Understand, Decompose, Execute, Checkpoint** — the core cycle.
|
|
6
|
+
Bookended by ASSESS (entry protocol) and HANDOFF (exit protocol).
|
|
4
7
|
|
|
5
8
|
## Core Principle
|
|
6
9
|
|
|
@@ -8,7 +11,7 @@
|
|
|
8
11
|
|
|
9
12
|
---
|
|
10
13
|
|
|
11
|
-
##
|
|
14
|
+
## Entry: ASSESS — Task Type Classification
|
|
12
15
|
|
|
13
16
|
Before any work, classify the task. Each type follows a different optimal path.
|
|
14
17
|
|
|
@@ -24,7 +27,7 @@ Before any work, classify the task. Each type follows a different optimal path.
|
|
|
24
27
|
|
|
25
28
|
---
|
|
26
29
|
|
|
27
|
-
##
|
|
30
|
+
## UDEC 1. UNDERSTAND — Understanding Protocol
|
|
28
31
|
|
|
29
32
|
### 2-1. Information Sufficiency Assessment (MANDATORY)
|
|
30
33
|
|
|
@@ -70,7 +73,7 @@ Before moving to DECOMPOSE:
|
|
|
70
73
|
|
|
71
74
|
---
|
|
72
75
|
|
|
73
|
-
##
|
|
76
|
+
## UDEC 2. DECOMPOSE — Planning Protocol
|
|
74
77
|
|
|
75
78
|
### 3-1. Decomposition Trigger
|
|
76
79
|
|
|
@@ -130,7 +133,7 @@ Before creating the plan:
|
|
|
130
133
|
|
|
131
134
|
---
|
|
132
135
|
|
|
133
|
-
##
|
|
136
|
+
## UDEC 3. EXECUTE — Execution Protocol
|
|
134
137
|
|
|
135
138
|
### 4-1. Batch Execution
|
|
136
139
|
|
|
@@ -203,7 +206,7 @@ When delegating work to sub-agents:
|
|
|
203
206
|
|
|
204
207
|
---
|
|
205
208
|
|
|
206
|
-
##
|
|
209
|
+
## UDEC 4. CHECKPOINT — Confirmation Protocol
|
|
207
210
|
|
|
208
211
|
### 5-1. Batch Checkpoint
|
|
209
212
|
|
|
@@ -231,7 +234,7 @@ User says "stop here" → clean exit
|
|
|
231
234
|
|
|
232
235
|
---
|
|
233
236
|
|
|
234
|
-
##
|
|
237
|
+
## Exit: HANDOFF — Session Transition Protocol
|
|
235
238
|
|
|
236
239
|
### 6-1. When to Handoff
|
|
237
240
|
|