maxsimcli 4.10.0 → 4.11.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/dist/assets/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,12 @@
|
|
|
1
|
+
# [4.10.0](https://github.com/maystudios/maxsimcli/compare/v4.9.0...v4.10.0) (2026-03-11)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Features
|
|
5
|
+
|
|
6
|
+
* add realignment phases 7-10 from drift report ([e3e87e1](https://github.com/maystudios/maxsimcli/commit/e3e87e18249dcf971700c8cf413aa96d42e054c3))
|
|
7
|
+
* **init:** add GitHub mapping data to workflow init contexts ([ccc25ed](https://github.com/maystudios/maxsimcli/commit/ccc25ed300a82ced53d1338614b64910cba98da3))
|
|
8
|
+
* **mcp:** enhance GitHub tools and add batch-create, external-edit-detection, sync-check tools ([b3edaf9](https://github.com/maystudios/maxsimcli/commit/b3edaf9479f39b7a183013c98c83007c247ae82e))
|
|
9
|
+
|
|
1
10
|
# [4.9.0](https://github.com/maystudios/maxsimcli/compare/v4.8.0...v4.9.0) (2026-03-11)
|
|
2
11
|
|
|
3
12
|
|
|
@@ -73,6 +73,53 @@ Use AskUserQuestion:
|
|
|
73
73
|
git init
|
|
74
74
|
```
|
|
75
75
|
|
|
76
|
+
## Step 1b: GitHub Prerequisites Gate
|
|
77
|
+
|
|
78
|
+
**This gate is MANDATORY. Do not proceed if it fails.**
|
|
79
|
+
|
|
80
|
+
Parse init context for `has_github_remote` and `gh_authenticated`:
|
|
81
|
+
|
|
82
|
+
1. If `has_github_remote` is false:
|
|
83
|
+
- STOP. Tell user:
|
|
84
|
+
```
|
|
85
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
86
|
+
MAXSIM ► NO GITHUB REMOTE FOUND
|
|
87
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
88
|
+
|
|
89
|
+
MAXSIM requires a GitHub remote to track phases as Issues.
|
|
90
|
+
|
|
91
|
+
To fix: git remote add origin <your-repo-url>
|
|
92
|
+
|
|
93
|
+
Then re-run /maxsim:init.
|
|
94
|
+
```
|
|
95
|
+
- Do NOT proceed with initialization.
|
|
96
|
+
|
|
97
|
+
2. If `gh_authenticated` is false:
|
|
98
|
+
- STOP. Tell user:
|
|
99
|
+
```
|
|
100
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
101
|
+
MAXSIM ► GITHUB CLI NOT AUTHENTICATED
|
|
102
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
103
|
+
|
|
104
|
+
MAXSIM requires GitHub CLI authentication to create phase issues.
|
|
105
|
+
|
|
106
|
+
To fix: gh auth login
|
|
107
|
+
|
|
108
|
+
Then re-run /maxsim:init.
|
|
109
|
+
```
|
|
110
|
+
- Do NOT proceed with initialization.
|
|
111
|
+
|
|
112
|
+
3. Both checks passed — call `mcp_github_setup` with the project name as the milestone title:
|
|
113
|
+
```
|
|
114
|
+
mcp_github_setup({ milestone_title: "[project name]" })
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
4. If `mcp_github_setup` fails:
|
|
118
|
+
- STOP with the error message returned by the tool.
|
|
119
|
+
- Do not fall back to local-only mode.
|
|
120
|
+
|
|
121
|
+
5. Record the `project_number` and board details returned by `mcp_github_setup` for use in the Phase Issue Creation step.
|
|
122
|
+
|
|
76
123
|
## Step 2: Conflict Resolution
|
|
77
124
|
|
|
78
125
|
**If auto mode:** Skip dialog. If `conflict_detected`, use merge behavior automatically (keep existing files, fill gaps, always re-scan codebase). Proceed to Step 3.
|
|
@@ -1110,6 +1157,47 @@ If "Approve": continue.
|
|
|
1110
1157
|
If "Adjust phases": get feedback, re-spawn roadmapper with revision context, re-present. Loop until approved.
|
|
1111
1158
|
If "Review full file": display raw `cat .planning/ROADMAP.md`, then re-ask.
|
|
1112
1159
|
|
|
1160
|
+
### 9c-ii: Create Phase Issues on GitHub
|
|
1161
|
+
|
|
1162
|
+
After the roadmap is finalized (approved or auto-mode), create a GitHub Issue for each phase. This is a mandatory step — phase tracking lives in GitHub, not in local `.planning/phases/` files (per WIRE-02).
|
|
1163
|
+
|
|
1164
|
+
Display banner:
|
|
1165
|
+
```
|
|
1166
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
1167
|
+
MAXSIM ► CREATING GITHUB PHASE ISSUES
|
|
1168
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
1169
|
+
```
|
|
1170
|
+
|
|
1171
|
+
1. Parse `.planning/ROADMAP.md` to extract all phases. For each phase, collect:
|
|
1172
|
+
- `phase_number` (e.g., `01`, `02`)
|
|
1173
|
+
- `phase_name` (e.g., "Foundation")
|
|
1174
|
+
- `goal` (the phase goal statement)
|
|
1175
|
+
- `requirements` (list of REQ-IDs mapped to this phase)
|
|
1176
|
+
- `success_criteria` (list of observable outcomes)
|
|
1177
|
+
|
|
1178
|
+
2. For each phase, call `mcp_create_phase_issue`:
|
|
1179
|
+
```
|
|
1180
|
+
mcp_create_phase_issue({
|
|
1181
|
+
phase_number: "[phase_number]",
|
|
1182
|
+
phase_name: "[phase_name]",
|
|
1183
|
+
goal: "[goal]",
|
|
1184
|
+
requirements: ["REQ-01", "REQ-02", ...],
|
|
1185
|
+
success_criteria: ["criterion 1", "criterion 2", ...]
|
|
1186
|
+
})
|
|
1187
|
+
```
|
|
1188
|
+
The tool auto-adds each issue to the project board with "To Do" status.
|
|
1189
|
+
|
|
1190
|
+
3. Track results per phase. If any phase issue creation fails:
|
|
1191
|
+
- Log which phases succeeded and which failed.
|
|
1192
|
+
- Offer targeted retry for failed phases only (do not re-create successful ones).
|
|
1193
|
+
|
|
1194
|
+
4. Report completion:
|
|
1195
|
+
```
|
|
1196
|
+
✓ Created {N} phase issues on GitHub Project Board #{project_number}
|
|
1197
|
+
```
|
|
1198
|
+
|
|
1199
|
+
**Note:** Per WIRE-02, phase-level artifact files (PLAN.md, SUMMARY.md, RESEARCH.md, CONTEXT.md) are NOT created in `.planning/phases/` during init. These live exclusively as GitHub Issue comments and bodies. The following local files are still created and committed: PROJECT.md, REQUIREMENTS.md, config.json, STATE.md, ROADMAP.md.
|
|
1200
|
+
|
|
1113
1201
|
### 9d: STATE.md
|
|
1114
1202
|
|
|
1115
1203
|
**Skip if merge mode and file exists with all required headers.**
|
|
@@ -1311,6 +1399,7 @@ Created:
|
|
|
1311
1399
|
✓ .planning/ROADMAP.md -- [Milestone name] + [N] phases
|
|
1312
1400
|
✓ .planning/STATE.md -- Pre-populated project memory
|
|
1313
1401
|
✓ .planning/codebase/ -- Full codebase analysis (4 docs + structure)
|
|
1402
|
+
✓ GitHub Project Board #{project_number} -- [N] phase issues created with "To Do" status
|
|
1314
1403
|
```
|
|
1315
1404
|
|
|
1316
1405
|
If auto mode, append:
|
|
@@ -1367,6 +1456,9 @@ Print next steps:
|
|
|
1367
1456
|
|
|
1368
1457
|
- [ ] .planning/ directory created (or merged)
|
|
1369
1458
|
- [ ] Git repo initialized (if not already)
|
|
1459
|
+
- [ ] GitHub remote detected (gate passed)
|
|
1460
|
+
- [ ] GitHub CLI authenticated (gate passed)
|
|
1461
|
+
- [ ] `mcp_github_setup` called successfully — project_number recorded
|
|
1370
1462
|
- [ ] Conflict detection completed (merge/overwrite/cancel dialog)
|
|
1371
1463
|
- [ ] Codebase scan completed (4 mapper agents spawned)
|
|
1372
1464
|
- [ ] README validated against scan findings
|
|
@@ -1378,6 +1470,7 @@ Print next steps:
|
|
|
1378
1470
|
- [ ] PROJECT.md created with brownfield extra sections
|
|
1379
1471
|
- [ ] REQUIREMENTS.md created with stage-aware format
|
|
1380
1472
|
- [ ] ROADMAP.md created with 3-5 concrete phases (no TBD)
|
|
1473
|
+
- [ ] `mcp_create_phase_issue` called for every phase — all issues on board with "To Do" status
|
|
1381
1474
|
- [ ] STATE.md created with pre-populated decisions and blockers
|
|
1382
1475
|
- [ ] config.json created with workflow settings
|
|
1383
1476
|
- [ ] .planning/codebase/ populated with scan documents
|
|
@@ -65,6 +65,53 @@ Parse JSON for: `researcher_model`, `synthesizer_model`, `roadmapper_model`, `co
|
|
|
65
65
|
git init
|
|
66
66
|
```
|
|
67
67
|
|
|
68
|
+
## 1b. GitHub Prerequisites Gate
|
|
69
|
+
|
|
70
|
+
**This gate is MANDATORY. Do not proceed if it fails.**
|
|
71
|
+
|
|
72
|
+
Parse init context for `has_github_remote` and `gh_authenticated`:
|
|
73
|
+
|
|
74
|
+
1. If `has_github_remote` is false:
|
|
75
|
+
- STOP. Tell user:
|
|
76
|
+
```
|
|
77
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
78
|
+
MAXSIM ► NO GITHUB REMOTE FOUND
|
|
79
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
80
|
+
|
|
81
|
+
MAXSIM requires a GitHub remote to track phases as Issues.
|
|
82
|
+
|
|
83
|
+
To fix: git remote add origin <your-repo-url>
|
|
84
|
+
|
|
85
|
+
Then re-run /maxsim:init.
|
|
86
|
+
```
|
|
87
|
+
- Do NOT proceed with project setup.
|
|
88
|
+
|
|
89
|
+
2. If `gh_authenticated` is false:
|
|
90
|
+
- STOP. Tell user:
|
|
91
|
+
```
|
|
92
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
93
|
+
MAXSIM ► GITHUB CLI NOT AUTHENTICATED
|
|
94
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
95
|
+
|
|
96
|
+
MAXSIM requires GitHub CLI authentication to create phase issues.
|
|
97
|
+
|
|
98
|
+
To fix: gh auth login
|
|
99
|
+
|
|
100
|
+
Then re-run /maxsim:init.
|
|
101
|
+
```
|
|
102
|
+
- Do NOT proceed with project setup.
|
|
103
|
+
|
|
104
|
+
3. Both checks passed — call `mcp_github_setup` with the project name as the milestone title:
|
|
105
|
+
```
|
|
106
|
+
mcp_github_setup({ milestone_title: "[project name]" })
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
4. If `mcp_github_setup` fails:
|
|
110
|
+
- STOP with the error message returned by the tool.
|
|
111
|
+
- Do not fall back to local-only mode.
|
|
112
|
+
|
|
113
|
+
5. Record the `project_number` and board details returned by `mcp_github_setup` for use in the Phase Issue Creation step.
|
|
114
|
+
|
|
68
115
|
## 2. Brownfield Offer
|
|
69
116
|
|
|
70
117
|
**If auto mode:** Skip to Step 4 (assume greenfield, synthesize PROJECT.md from provided document).
|
|
@@ -1254,7 +1301,48 @@ Use AskUserQuestion:
|
|
|
1254
1301
|
node ~/.claude/maxsim/bin/maxsim-tools.cjs commit "docs: create roadmap ([N] phases)" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md
|
|
1255
1302
|
```
|
|
1256
1303
|
|
|
1257
|
-
## 8b.
|
|
1304
|
+
## 8b. Create Phase Issues on GitHub
|
|
1305
|
+
|
|
1306
|
+
After the roadmap is finalized and committed, create a GitHub Issue for each phase. This is a mandatory step — phase tracking lives in GitHub, not in local `.planning/phases/` files (per WIRE-02).
|
|
1307
|
+
|
|
1308
|
+
Display banner:
|
|
1309
|
+
```
|
|
1310
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
1311
|
+
MAXSIM ► CREATING GITHUB PHASE ISSUES
|
|
1312
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
1313
|
+
```
|
|
1314
|
+
|
|
1315
|
+
1. Parse `.planning/ROADMAP.md` to extract all phases. For each phase, collect:
|
|
1316
|
+
- `phase_number` (e.g., `01`, `02`)
|
|
1317
|
+
- `phase_name` (e.g., "Foundation")
|
|
1318
|
+
- `goal` (the phase goal statement)
|
|
1319
|
+
- `requirements` (list of REQ-IDs mapped to this phase)
|
|
1320
|
+
- `success_criteria` (list of observable outcomes)
|
|
1321
|
+
|
|
1322
|
+
2. For each phase, call `mcp_create_phase_issue`:
|
|
1323
|
+
```
|
|
1324
|
+
mcp_create_phase_issue({
|
|
1325
|
+
phase_number: "[phase_number]",
|
|
1326
|
+
phase_name: "[phase_name]",
|
|
1327
|
+
goal: "[goal]",
|
|
1328
|
+
requirements: ["REQ-01", "REQ-02", ...],
|
|
1329
|
+
success_criteria: ["criterion 1", "criterion 2", ...]
|
|
1330
|
+
})
|
|
1331
|
+
```
|
|
1332
|
+
The tool auto-adds each issue to the project board with "To Do" status.
|
|
1333
|
+
|
|
1334
|
+
3. Track results per phase. If any phase issue creation fails:
|
|
1335
|
+
- Log which phases succeeded and which failed.
|
|
1336
|
+
- Offer targeted retry for failed phases only (do not re-create successful ones).
|
|
1337
|
+
|
|
1338
|
+
4. Report completion:
|
|
1339
|
+
```
|
|
1340
|
+
✓ Created {N} phase issues on GitHub Project Board #{project_number}
|
|
1341
|
+
```
|
|
1342
|
+
|
|
1343
|
+
**Note:** Per WIRE-02, phase-level artifact files (PLAN.md, SUMMARY.md, RESEARCH.md, CONTEXT.md) are NOT created in `.planning/phases/` during init. These live exclusively as GitHub Issue comments and bodies. The following local files are still created and committed: PROJECT.md, REQUIREMENTS.md, config.json, STATE.md, ROADMAP.md.
|
|
1344
|
+
|
|
1345
|
+
## 8c. Agent Dry-Run Validation
|
|
1258
1346
|
|
|
1259
1347
|
**Always runs after all documents are generated — this is the quality gate for init output.**
|
|
1260
1348
|
|
|
@@ -1328,8 +1416,9 @@ Present completion summary:
|
|
|
1328
1416
|
| Research | `.planning/research/` |
|
|
1329
1417
|
| Requirements | `.planning/REQUIREMENTS.md` |
|
|
1330
1418
|
| Roadmap | `.planning/ROADMAP.md` |
|
|
1419
|
+
| Phase Issues | GitHub Project Board #{project_number} |
|
|
1331
1420
|
|
|
1332
|
-
**[N] phases** | **[X] requirements** | Ready to build ✓
|
|
1421
|
+
**[N] phases** | **[X] requirements** | **[N] GitHub issues created** | Ready to build ✓
|
|
1333
1422
|
```
|
|
1334
1423
|
|
|
1335
1424
|
**If auto mode:**
|
|
@@ -1397,6 +1486,9 @@ Exit skill and invoke SlashCommand("/maxsim:plan 1 --auto")
|
|
|
1397
1486
|
- [ ] Requirements gathered (from research or conversation)
|
|
1398
1487
|
- [ ] User scoped each category (v1/v2/out of scope)
|
|
1399
1488
|
- [ ] REQUIREMENTS.md created with REQ-IDs → **committed**
|
|
1489
|
+
- [ ] GitHub remote detected (gate passed)
|
|
1490
|
+
- [ ] GitHub CLI authenticated (gate passed)
|
|
1491
|
+
- [ ] `mcp_github_setup` called successfully — project_number recorded
|
|
1400
1492
|
- [ ] planner (roadmap mode) spawned with context
|
|
1401
1493
|
- [ ] Roadmap files written immediately (not draft)
|
|
1402
1494
|
- [ ] User feedback incorporated (if any)
|
|
@@ -1405,6 +1497,7 @@ Exit skill and invoke SlashCommand("/maxsim:plan 1 --auto")
|
|
|
1405
1497
|
- [ ] REQUIREMENTS.md traceability updated
|
|
1406
1498
|
- [ ] CONVENTIONS.md generated with 4 must-have sections (Tech Stack, File Layout, Error Handling, Testing)
|
|
1407
1499
|
- [ ] NO-GOS.md populated from confirmed no-gos during questioning
|
|
1500
|
+
- [ ] `mcp_create_phase_issue` called for every phase — all issues on board with "To Do" status
|
|
1408
1501
|
- [ ] Agent dry-run validation passed (Quality Score >= 7)
|
|
1409
1502
|
- [ ] User knows next step is `/maxsim:plan 1`
|
|
1410
1503
|
|
package/package.json
CHANGED