golem-cc 0.1.0
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 +240 -0
- package/bin/golem +555 -0
- package/bin/install.cjs +338 -0
- package/commands/golem/build.md +145 -0
- package/commands/golem/help.md +58 -0
- package/commands/golem/plan.md +125 -0
- package/commands/golem/simplify.md +131 -0
- package/commands/golem/spec.md +159 -0
- package/commands/golem/status.md +89 -0
- package/golem/agents/code-simplifier.md +113 -0
- package/golem/agents/spec-builder.md +152 -0
- package/golem/prompts/PROMPT_build.md +60 -0
- package/golem/prompts/PROMPT_plan.md +84 -0
- package/package.json +31 -0
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
# Ralph Planning Mode
|
|
2
|
+
|
|
3
|
+
You are operating in **planning mode** - your job is to analyze specs versus existing code and create/update the implementation plan.
|
|
4
|
+
|
|
5
|
+
## Execution Flow
|
|
6
|
+
|
|
7
|
+
1. **Read Specs** - Understand all requirements from specs/*.md
|
|
8
|
+
2. **Analyze Code** - Search the codebase to understand current state
|
|
9
|
+
3. **Gap Analysis** - Identify what needs to be built vs. what exists
|
|
10
|
+
4. **Prioritize** - Order tasks by dependencies and criticality
|
|
11
|
+
5. **Generate Plan** - Create/update IMPLEMENTATION_PLAN.md
|
|
12
|
+
|
|
13
|
+
## Rules
|
|
14
|
+
|
|
15
|
+
### Spec Analysis
|
|
16
|
+
- Read each spec file completely
|
|
17
|
+
- Extract concrete requirements (must have, should have)
|
|
18
|
+
- Note acceptance criteria and constraints
|
|
19
|
+
- Identify dependencies between specs
|
|
20
|
+
|
|
21
|
+
### Code Analysis
|
|
22
|
+
- Search for existing implementations
|
|
23
|
+
- Understand current architecture and patterns
|
|
24
|
+
- Identify reusable components
|
|
25
|
+
- Note technical debt or issues
|
|
26
|
+
|
|
27
|
+
### Gap Analysis
|
|
28
|
+
For each requirement, determine:
|
|
29
|
+
- **Done**: Already implemented and tested
|
|
30
|
+
- **Partial**: Partially implemented, needs completion
|
|
31
|
+
- **Missing**: Not implemented at all
|
|
32
|
+
- **Blocked**: Depends on something not yet built
|
|
33
|
+
|
|
34
|
+
### Task Generation
|
|
35
|
+
Each task should be:
|
|
36
|
+
- **Atomic** - Completable in one focused session
|
|
37
|
+
- **Testable** - Has clear verification criteria
|
|
38
|
+
- **Scoped** - Affects 1-3 files typically
|
|
39
|
+
- **Independent** - Minimal dependencies on other tasks
|
|
40
|
+
|
|
41
|
+
Bad task: "Implement authentication"
|
|
42
|
+
Good task: "Implement user registration with email/password"
|
|
43
|
+
|
|
44
|
+
### Priority Rules
|
|
45
|
+
Order tasks by:
|
|
46
|
+
1. **Critical path** - What blocks other work?
|
|
47
|
+
2. **Dependencies** - What must be built first?
|
|
48
|
+
3. **Risk** - Tackle unknowns early
|
|
49
|
+
4. **Value** - Higher value tasks before nice-to-haves
|
|
50
|
+
|
|
51
|
+
### Plan Format
|
|
52
|
+
|
|
53
|
+
Write `IMPLEMENTATION_PLAN.md` in this format:
|
|
54
|
+
|
|
55
|
+
```markdown
|
|
56
|
+
# Implementation Plan
|
|
57
|
+
|
|
58
|
+
Generated: {timestamp}
|
|
59
|
+
Based on: specs/*.md
|
|
60
|
+
|
|
61
|
+
## Status
|
|
62
|
+
- Total tasks: N
|
|
63
|
+
- Completed: 0
|
|
64
|
+
- Remaining: N
|
|
65
|
+
|
|
66
|
+
## Tasks
|
|
67
|
+
|
|
68
|
+
### [ ] 1. {Task title}
|
|
69
|
+
Priority: Critical|High|Medium|Low
|
|
70
|
+
Files: {expected files to create/modify}
|
|
71
|
+
Notes: {implementation hints, constraints}
|
|
72
|
+
Depends on: {task numbers if any}
|
|
73
|
+
|
|
74
|
+
### [ ] 2. {Next task}
|
|
75
|
+
...
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
## Important
|
|
79
|
+
|
|
80
|
+
- Do NOT implement anything in planning mode
|
|
81
|
+
- Do NOT modify source code
|
|
82
|
+
- ONLY create/update IMPLEMENTATION_PLAN.md
|
|
83
|
+
- Be thorough - missing tasks cause problems later
|
|
84
|
+
- Be realistic - tasks should be achievable in one iteration
|
package/package.json
ADDED
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "golem-cc",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "Autonomous coding loop with Claude - structured specs, ralph loop execution, code simplification",
|
|
5
|
+
"bin": {
|
|
6
|
+
"golem-cc": "./bin/install.cjs"
|
|
7
|
+
},
|
|
8
|
+
"files": [
|
|
9
|
+
"bin/",
|
|
10
|
+
"commands/",
|
|
11
|
+
"golem/"
|
|
12
|
+
],
|
|
13
|
+
"keywords": [
|
|
14
|
+
"claude",
|
|
15
|
+
"ai",
|
|
16
|
+
"coding",
|
|
17
|
+
"autonomous",
|
|
18
|
+
"llm",
|
|
19
|
+
"ralph",
|
|
20
|
+
"golem"
|
|
21
|
+
],
|
|
22
|
+
"author": "David Kay (dkay@fastmail.com)",
|
|
23
|
+
"license": "MIT",
|
|
24
|
+
"engines": {
|
|
25
|
+
"node": ">=18"
|
|
26
|
+
},
|
|
27
|
+
"repository": {
|
|
28
|
+
"type": "git",
|
|
29
|
+
"url": "git+https://github.com/daresTheDevil/golem-cc.git"
|
|
30
|
+
}
|
|
31
|
+
}
|