golem-cc 2.1.2 → 3.0.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/.claude/commands/golem/build.md +18 -0
- package/.claude/commands/golem/config.md +39 -0
- package/.claude/commands/golem/continue.md +73 -0
- package/.claude/commands/golem/doctor.md +46 -0
- package/.claude/commands/golem/document.md +138 -0
- package/.claude/commands/golem/help.md +58 -0
- package/.claude/commands/golem/pause.md +130 -0
- package/.claude/commands/golem/plan.md +111 -0
- package/.claude/commands/golem/review.md +166 -0
- package/.claude/commands/golem/security.md +186 -0
- package/.claude/commands/golem/simplify.md +76 -0
- package/.claude/commands/golem/spec.md +105 -0
- package/.claude/commands/golem/status.md +33 -0
- package/.golem/agents/code-simplifier.md +54 -0
- package/.golem/agents/review-architecture.md +59 -0
- package/.golem/agents/review-logic.md +50 -0
- package/.golem/agents/review-security.md +50 -0
- package/.golem/agents/review-style.md +48 -0
- package/.golem/agents/review-tests.md +48 -0
- package/.golem/agents/spec-builder.md +60 -0
- package/.golem/bin/golem.mjs +270 -0
- package/.golem/lib/build.mjs +557 -0
- package/.golem/lib/claude.mjs +95 -0
- package/.golem/lib/config.mjs +421 -0
- package/.golem/lib/display.mjs +191 -0
- package/.golem/lib/doctor.mjs +197 -0
- package/.golem/lib/document.mjs +792 -0
- package/.golem/lib/gates.mjs +78 -0
- package/.golem/lib/init.mjs +166 -0
- package/.golem/lib/output.mjs +40 -0
- package/.golem/lib/ratelimit.mjs +86 -0
- package/.golem/lib/security.mjs +603 -0
- package/.golem/lib/simplify.mjs +101 -0
- package/.golem/lib/tui.mjs +368 -0
- package/.golem/lib/usage.mjs +119 -0
- package/.golem/lib/worktree.mjs +509 -0
- package/.golem/prompts/build.md +23 -0
- package/.golem/prompts/document-inline.md +66 -0
- package/.golem/prompts/document-markdown.md +80 -0
- package/.golem/prompts/simplify.md +35 -0
- package/README.md +141 -142
- package/bin/golem-shim.mjs +36 -0
- package/bin/install.mjs +193 -0
- package/package.json +27 -32
- package/.env.example +0 -17
- package/bin/golem +0 -1040
- package/commands/golem/build.md +0 -235
- package/commands/golem/config.md +0 -55
- package/commands/golem/doctor.md +0 -137
- package/commands/golem/help.md +0 -212
- package/commands/golem/plan.md +0 -214
- package/commands/golem/review.md +0 -376
- package/commands/golem/security.md +0 -204
- package/commands/golem/simplify.md +0 -94
- package/commands/golem/spec.md +0 -226
- package/commands/golem/status.md +0 -60
- package/dist/api/freshworks.d.ts +0 -61
- package/dist/api/freshworks.d.ts.map +0 -1
- package/dist/api/freshworks.js +0 -119
- package/dist/api/freshworks.js.map +0 -1
- package/dist/api/gitea.d.ts +0 -96
- package/dist/api/gitea.d.ts.map +0 -1
- package/dist/api/gitea.js +0 -154
- package/dist/api/gitea.js.map +0 -1
- package/dist/cli/index.d.ts +0 -9
- package/dist/cli/index.d.ts.map +0 -1
- package/dist/cli/index.js +0 -352
- package/dist/cli/index.js.map +0 -1
- package/dist/sync/ticket-sync.d.ts +0 -53
- package/dist/sync/ticket-sync.d.ts.map +0 -1
- package/dist/sync/ticket-sync.js +0 -226
- package/dist/sync/ticket-sync.js.map +0 -1
- package/dist/types.d.ts +0 -125
- package/dist/types.d.ts.map +0 -1
- package/dist/types.js +0 -5
- package/dist/types.js.map +0 -1
- package/dist/worktree/manager.d.ts +0 -54
- package/dist/worktree/manager.d.ts.map +0 -1
- package/dist/worktree/manager.js +0 -190
- package/dist/worktree/manager.js.map +0 -1
- package/golem/agents/code-simplifier.md +0 -81
- package/golem/agents/spec-builder.md +0 -90
- package/golem/prompts/PROMPT_build.md +0 -71
- package/golem/prompts/PROMPT_plan.md +0 -102
|
@@ -1,102 +0,0 @@
|
|
|
1
|
-
# Planning Mode
|
|
2
|
-
|
|
3
|
-
You are in PLANNING MODE. Analyze specs and create an implementation plan. Do NOT write any code.
|
|
4
|
-
|
|
5
|
-
## Phase 1: Read Specs
|
|
6
|
-
|
|
7
|
-
Read every file in `.golem/specs/`:
|
|
8
|
-
- Extract all requirements (must have, should have)
|
|
9
|
-
- Extract all acceptance criteria
|
|
10
|
-
- Extract all test definitions
|
|
11
|
-
- Note dependencies between topics
|
|
12
|
-
|
|
13
|
-
## Phase 2: Analyze Codebase
|
|
14
|
-
|
|
15
|
-
Search the existing code:
|
|
16
|
-
- What's already implemented?
|
|
17
|
-
- What patterns exist?
|
|
18
|
-
- What files will need modification?
|
|
19
|
-
- What new files will be needed?
|
|
20
|
-
|
|
21
|
-
Do NOT assume something doesn't exist - always search first.
|
|
22
|
-
|
|
23
|
-
## Phase 3: Gap Analysis
|
|
24
|
-
|
|
25
|
-
For each requirement:
|
|
26
|
-
- **Done**: Already implemented (cite evidence)
|
|
27
|
-
- **Partial**: Needs modification (cite what exists)
|
|
28
|
-
- **Missing**: Not implemented (cite where it should go)
|
|
29
|
-
- **Blocked**: Depends on external factor
|
|
30
|
-
|
|
31
|
-
## Phase 4: Create Staged Tasks
|
|
32
|
-
|
|
33
|
-
Group tasks into STAGES. Each stage is a logical milestone.
|
|
34
|
-
|
|
35
|
-
Good stage: "Authentication endpoints"
|
|
36
|
-
- Task 1: Add login route handler
|
|
37
|
-
- Task 2: Add password validation
|
|
38
|
-
- Task 3: Add JWT generation
|
|
39
|
-
- Task 4: Add login tests
|
|
40
|
-
|
|
41
|
-
Bad stage: "Backend stuff"
|
|
42
|
-
- Too vague, not a clear milestone
|
|
43
|
-
|
|
44
|
-
### Task Quality
|
|
45
|
-
|
|
46
|
-
Each task should be:
|
|
47
|
-
- **Atomic**: One focused change
|
|
48
|
-
- **Testable**: Clear verification criteria
|
|
49
|
-
- **Small**: 1-3 files typically
|
|
50
|
-
- **Independent**: Minimal dependencies within stage
|
|
51
|
-
|
|
52
|
-
### Stage Commit Message
|
|
53
|
-
|
|
54
|
-
Each stage needs a commit message for when it's squashed:
|
|
55
|
-
```
|
|
56
|
-
{type}({scope}): {description} [{TICKET_ID}]
|
|
57
|
-
```
|
|
58
|
-
|
|
59
|
-
## Phase 5: Write Plan
|
|
60
|
-
|
|
61
|
-
Create `.golem/IMPLEMENTATION_PLAN.md`:
|
|
62
|
-
|
|
63
|
-
```markdown
|
|
64
|
-
# Implementation Plan
|
|
65
|
-
|
|
66
|
-
Ticket: {INC-XXXX}
|
|
67
|
-
Generated: {timestamp}
|
|
68
|
-
|
|
69
|
-
## Status
|
|
70
|
-
- Stages: N
|
|
71
|
-
- Completed: 0
|
|
72
|
-
- Current: Stage 1
|
|
73
|
-
|
|
74
|
-
---
|
|
75
|
-
|
|
76
|
-
## Stage 1: {Clear milestone name}
|
|
77
|
-
Commit: {type}({scope}): {description} [{TICKET_ID}]
|
|
78
|
-
|
|
79
|
-
### [ ] 1.1. {Task title}
|
|
80
|
-
Files: {files to create/modify}
|
|
81
|
-
Notes: {implementation hints}
|
|
82
|
-
Tests: {what verifies this}
|
|
83
|
-
|
|
84
|
-
### [ ] 1.2. {Task title}
|
|
85
|
-
...
|
|
86
|
-
|
|
87
|
-
---
|
|
88
|
-
|
|
89
|
-
## Stage 2: {Milestone}
|
|
90
|
-
Commit: {commit message}
|
|
91
|
-
Depends on: Stage 1
|
|
92
|
-
|
|
93
|
-
...
|
|
94
|
-
```
|
|
95
|
-
|
|
96
|
-
## Critical Rules
|
|
97
|
-
|
|
98
|
-
- Do NOT implement anything
|
|
99
|
-
- Do NOT modify source code
|
|
100
|
-
- ONLY create .golem/IMPLEMENTATION_PLAN.md
|
|
101
|
-
- Be thorough - missing tasks cause problems later
|
|
102
|
-
- Stages represent logical milestones for commits
|