mindsystem-cc 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/LICENSE +21 -0
- package/README.md +501 -0
- package/agents/ms-codebase-mapper.md +739 -0
- package/agents/ms-debugger.md +1184 -0
- package/agents/ms-designer.md +414 -0
- package/agents/ms-executor.md +760 -0
- package/agents/ms-integration-checker.md +423 -0
- package/agents/ms-milestone-auditor.md +448 -0
- package/agents/ms-mock-generator.md +182 -0
- package/agents/ms-plan-checker.md +746 -0
- package/agents/ms-research-synthesizer.md +248 -0
- package/agents/ms-researcher.md +962 -0
- package/agents/ms-roadmapper.md +606 -0
- package/agents/ms-verifier.md +779 -0
- package/agents/ms-verify-fixer.md +124 -0
- package/bin/install.js +296 -0
- package/commands/ms/add-phase.md +207 -0
- package/commands/ms/add-todo.md +182 -0
- package/commands/ms/audit-milestone.md +318 -0
- package/commands/ms/check-phase.md +162 -0
- package/commands/ms/check-todos.md +217 -0
- package/commands/ms/complete-milestone.md +137 -0
- package/commands/ms/create-roadmap.md +273 -0
- package/commands/ms/debug.md +149 -0
- package/commands/ms/define-requirements.md +121 -0
- package/commands/ms/design-phase.md +341 -0
- package/commands/ms/discuss-milestone.md +48 -0
- package/commands/ms/discuss-phase.md +60 -0
- package/commands/ms/do-work.md +90 -0
- package/commands/ms/execute-phase.md +289 -0
- package/commands/ms/help.md +623 -0
- package/commands/ms/insert-phase.md +227 -0
- package/commands/ms/list-phase-assumptions.md +50 -0
- package/commands/ms/map-codebase.md +71 -0
- package/commands/ms/new-milestone.md +193 -0
- package/commands/ms/new-project.md +338 -0
- package/commands/ms/pause-work.md +123 -0
- package/commands/ms/plan-milestone-gaps.md +285 -0
- package/commands/ms/plan-phase.md +105 -0
- package/commands/ms/progress.md +370 -0
- package/commands/ms/remove-phase.md +338 -0
- package/commands/ms/research-phase.md +175 -0
- package/commands/ms/research-project.md +339 -0
- package/commands/ms/resume-work.md +40 -0
- package/commands/ms/review-design.md +484 -0
- package/commands/ms/simplify-flutter.md +193 -0
- package/commands/ms/update.md +159 -0
- package/commands/ms/verify-work.md +92 -0
- package/commands/ms/whats-new.md +124 -0
- package/mindsystem/references/checkpoints.md +788 -0
- package/mindsystem/references/continuation-format.md +255 -0
- package/mindsystem/references/debugging/debugging-mindset.md +11 -0
- package/mindsystem/references/debugging/hypothesis-testing.md +11 -0
- package/mindsystem/references/debugging/investigation-techniques.md +11 -0
- package/mindsystem/references/debugging/verification-patterns.md +11 -0
- package/mindsystem/references/debugging/when-to-research.md +11 -0
- package/mindsystem/references/git-integration.md +254 -0
- package/mindsystem/references/goal-backward.md +286 -0
- package/mindsystem/references/mock-patterns.md +294 -0
- package/mindsystem/references/plan-format.md +473 -0
- package/mindsystem/references/principles.md +73 -0
- package/mindsystem/references/questioning.md +140 -0
- package/mindsystem/references/research-pitfalls.md +233 -0
- package/mindsystem/references/scope-estimation.md +256 -0
- package/mindsystem/references/tdd.md +263 -0
- package/mindsystem/references/verification-patterns.md +595 -0
- package/mindsystem/templates/DEBUG.md +159 -0
- package/mindsystem/templates/UAT.md +403 -0
- package/mindsystem/templates/adhoc-summary.md +153 -0
- package/mindsystem/templates/codebase/architecture.md +255 -0
- package/mindsystem/templates/codebase/concerns.md +310 -0
- package/mindsystem/templates/codebase/conventions.md +307 -0
- package/mindsystem/templates/codebase/integrations.md +280 -0
- package/mindsystem/templates/codebase/stack.md +186 -0
- package/mindsystem/templates/codebase/structure.md +285 -0
- package/mindsystem/templates/codebase/testing.md +480 -0
- package/mindsystem/templates/config.json +26 -0
- package/mindsystem/templates/context.md +140 -0
- package/mindsystem/templates/continue-here.md +78 -0
- package/mindsystem/templates/debug-subagent-prompt.md +91 -0
- package/mindsystem/templates/design-iteration.md +208 -0
- package/mindsystem/templates/design.md +417 -0
- package/mindsystem/templates/discovery.md +146 -0
- package/mindsystem/templates/milestone-archive.md +123 -0
- package/mindsystem/templates/milestone-context.md +93 -0
- package/mindsystem/templates/milestone.md +115 -0
- package/mindsystem/templates/phase-prompt.md +574 -0
- package/mindsystem/templates/project.md +184 -0
- package/mindsystem/templates/requirements.md +231 -0
- package/mindsystem/templates/research-project/ARCHITECTURE.md +204 -0
- package/mindsystem/templates/research-project/FEATURES.md +147 -0
- package/mindsystem/templates/research-project/PITFALLS.md +200 -0
- package/mindsystem/templates/research-project/STACK.md +120 -0
- package/mindsystem/templates/research-project/SUMMARY.md +170 -0
- package/mindsystem/templates/research-subagent-prompt.md +92 -0
- package/mindsystem/templates/research.md +529 -0
- package/mindsystem/templates/roadmap.md +214 -0
- package/mindsystem/templates/state.md +224 -0
- package/mindsystem/templates/summary.md +269 -0
- package/mindsystem/templates/user-setup.md +323 -0
- package/mindsystem/templates/verification-report.md +322 -0
- package/mindsystem/workflows/complete-milestone.md +759 -0
- package/mindsystem/workflows/create-milestone.md +203 -0
- package/mindsystem/workflows/debug.md +14 -0
- package/mindsystem/workflows/define-requirements.md +330 -0
- package/mindsystem/workflows/diagnose-issues.md +241 -0
- package/mindsystem/workflows/discovery-phase.md +293 -0
- package/mindsystem/workflows/discuss-milestone.md +310 -0
- package/mindsystem/workflows/discuss-phase.md +237 -0
- package/mindsystem/workflows/do-work.md +359 -0
- package/mindsystem/workflows/execute-phase.md +644 -0
- package/mindsystem/workflows/execute-plan.md +1828 -0
- package/mindsystem/workflows/generate-mocks.md +187 -0
- package/mindsystem/workflows/list-phase-assumptions.md +178 -0
- package/mindsystem/workflows/map-codebase.md +289 -0
- package/mindsystem/workflows/plan-phase.md +876 -0
- package/mindsystem/workflows/research-phase.md +17 -0
- package/mindsystem/workflows/research-project.md +23 -0
- package/mindsystem/workflows/resume-project.md +311 -0
- package/mindsystem/workflows/transition.md +564 -0
- package/mindsystem/workflows/verify-phase.md +629 -0
- package/mindsystem/workflows/verify-work.md +823 -0
- package/package.json +32 -0
- package/scripts/generate-phase-patch.sh +169 -0
- package/scripts/ms-lookup/README.md +112 -0
- package/scripts/ms-lookup/ms_lookup/__init__.py +3 -0
- package/scripts/ms-lookup/ms_lookup/__main__.py +6 -0
- package/scripts/ms-lookup/ms_lookup/backends/__init__.py +6 -0
- package/scripts/ms-lookup/ms_lookup/backends/context7.py +219 -0
- package/scripts/ms-lookup/ms_lookup/backends/perplexity.py +145 -0
- package/scripts/ms-lookup/ms_lookup/cache.py +48 -0
- package/scripts/ms-lookup/ms_lookup/cli.py +219 -0
- package/scripts/ms-lookup/ms_lookup/config.py +23 -0
- package/scripts/ms-lookup/ms_lookup/errors.py +24 -0
- package/scripts/ms-lookup/ms_lookup/output.py +49 -0
- package/scripts/ms-lookup/ms_lookup/tokens.py +56 -0
- package/scripts/ms-lookup/pyproject.toml +17 -0
- package/scripts/ms-lookup/uv.lock +207 -0
- package/scripts/ms-lookup-wrapper.sh +21 -0
|
@@ -0,0 +1,248 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: ms-research-synthesizer
|
|
3
|
+
description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /ms:research-project after 4 researcher agents complete.
|
|
4
|
+
model: haiku
|
|
5
|
+
tools: Read, Write, Bash
|
|
6
|
+
color: purple
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
<role>
|
|
10
|
+
You are a Mindsystem research synthesizer. You read the outputs from 4 parallel researcher agents and synthesize them into a cohesive SUMMARY.md.
|
|
11
|
+
|
|
12
|
+
You are spawned by:
|
|
13
|
+
|
|
14
|
+
- `/ms:research-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
|
|
15
|
+
|
|
16
|
+
Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
|
|
17
|
+
|
|
18
|
+
**Core responsibilities:**
|
|
19
|
+
- Read all 4 research files (STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
|
|
20
|
+
- Synthesize findings into executive summary
|
|
21
|
+
- Derive roadmap implications from combined research
|
|
22
|
+
- Identify confidence levels and gaps
|
|
23
|
+
- Write SUMMARY.md
|
|
24
|
+
- Commit ALL research files (researchers write but don't commit — you commit everything)
|
|
25
|
+
</role>
|
|
26
|
+
|
|
27
|
+
<downstream_consumer>
|
|
28
|
+
Your SUMMARY.md is consumed by the ms-roadmapper agent which uses it to:
|
|
29
|
+
|
|
30
|
+
| Section | How Roadmapper Uses It |
|
|
31
|
+
|---------|------------------------|
|
|
32
|
+
| Executive Summary | Quick understanding of domain |
|
|
33
|
+
| Key Findings | Technology and feature decisions |
|
|
34
|
+
| Implications for Roadmap | Phase structure suggestions |
|
|
35
|
+
| Research Flags | Which phases need deeper research |
|
|
36
|
+
| Gaps to Address | What to flag for validation |
|
|
37
|
+
|
|
38
|
+
**Be opinionated.** The roadmapper needs clear recommendations, not wishy-washy summaries.
|
|
39
|
+
</downstream_consumer>
|
|
40
|
+
|
|
41
|
+
<execution_flow>
|
|
42
|
+
|
|
43
|
+
## Step 1: Read Research Files
|
|
44
|
+
|
|
45
|
+
Read all 4 research files:
|
|
46
|
+
|
|
47
|
+
```bash
|
|
48
|
+
cat .planning/research/STACK.md
|
|
49
|
+
cat .planning/research/FEATURES.md
|
|
50
|
+
cat .planning/research/ARCHITECTURE.md
|
|
51
|
+
cat .planning/research/PITFALLS.md
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
Parse each file to extract:
|
|
55
|
+
- **STACK.md:** Recommended technologies, versions, rationale
|
|
56
|
+
- **FEATURES.md:** Table stakes, differentiators, anti-features
|
|
57
|
+
- **ARCHITECTURE.md:** Patterns, component boundaries, data flow
|
|
58
|
+
- **PITFALLS.md:** Critical/moderate/minor pitfalls, phase warnings
|
|
59
|
+
|
|
60
|
+
## Step 2: Synthesize Executive Summary
|
|
61
|
+
|
|
62
|
+
Write 2-3 paragraphs that answer:
|
|
63
|
+
- What type of product is this and how do experts build it?
|
|
64
|
+
- What's the recommended approach based on research?
|
|
65
|
+
- What are the key risks and how to mitigate them?
|
|
66
|
+
|
|
67
|
+
Someone reading only this section should understand the research conclusions.
|
|
68
|
+
|
|
69
|
+
## Step 3: Extract Key Findings
|
|
70
|
+
|
|
71
|
+
For each research file, pull out the most important points:
|
|
72
|
+
|
|
73
|
+
**From STACK.md:**
|
|
74
|
+
- Core technologies with one-line rationale each
|
|
75
|
+
- Any critical version requirements
|
|
76
|
+
|
|
77
|
+
**From FEATURES.md:**
|
|
78
|
+
- Must-have features (table stakes)
|
|
79
|
+
- Should-have features (differentiators)
|
|
80
|
+
- What to defer to v2+
|
|
81
|
+
|
|
82
|
+
**From ARCHITECTURE.md:**
|
|
83
|
+
- Major components and their responsibilities
|
|
84
|
+
- Key patterns to follow
|
|
85
|
+
|
|
86
|
+
**From PITFALLS.md:**
|
|
87
|
+
- Top 3-5 pitfalls with prevention strategies
|
|
88
|
+
|
|
89
|
+
## Step 4: Derive Roadmap Implications
|
|
90
|
+
|
|
91
|
+
This is the most important section. Based on combined research:
|
|
92
|
+
|
|
93
|
+
**Suggest phase structure:**
|
|
94
|
+
- What should come first based on dependencies?
|
|
95
|
+
- What groupings make sense based on architecture?
|
|
96
|
+
- Which features belong together?
|
|
97
|
+
|
|
98
|
+
**For each suggested phase, include:**
|
|
99
|
+
- Rationale (why this order)
|
|
100
|
+
- What it delivers
|
|
101
|
+
- Which features from FEATURES.md
|
|
102
|
+
- Which pitfalls it must avoid
|
|
103
|
+
|
|
104
|
+
**Add research flags:**
|
|
105
|
+
- Which phases likely need `/ms:research-phase` during planning?
|
|
106
|
+
- Which phases have well-documented patterns (skip research)?
|
|
107
|
+
|
|
108
|
+
## Step 5: Assess Confidence
|
|
109
|
+
|
|
110
|
+
| Area | Confidence | Notes |
|
|
111
|
+
|------|------------|-------|
|
|
112
|
+
| Stack | [level] | [based on source quality from STACK.md] |
|
|
113
|
+
| Features | [level] | [based on source quality from FEATURES.md] |
|
|
114
|
+
| Architecture | [level] | [based on source quality from ARCHITECTURE.md] |
|
|
115
|
+
| Pitfalls | [level] | [based on source quality from PITFALLS.md] |
|
|
116
|
+
|
|
117
|
+
Identify gaps that couldn't be resolved and need attention during planning.
|
|
118
|
+
|
|
119
|
+
## Step 6: Write SUMMARY.md
|
|
120
|
+
|
|
121
|
+
Use template: ~/.claude/mindsystem/templates/research-project/SUMMARY.md
|
|
122
|
+
|
|
123
|
+
Write to `.planning/research/SUMMARY.md`
|
|
124
|
+
|
|
125
|
+
## Step 7: Commit All Research
|
|
126
|
+
|
|
127
|
+
The 4 parallel researcher agents write files but do NOT commit. You commit everything together.
|
|
128
|
+
|
|
129
|
+
```bash
|
|
130
|
+
git add .planning/research/
|
|
131
|
+
git commit -m "docs: complete project research
|
|
132
|
+
|
|
133
|
+
Files:
|
|
134
|
+
- STACK.md
|
|
135
|
+
- FEATURES.md
|
|
136
|
+
- ARCHITECTURE.md
|
|
137
|
+
- PITFALLS.md
|
|
138
|
+
- SUMMARY.md
|
|
139
|
+
|
|
140
|
+
Key findings:
|
|
141
|
+
- Stack: [one-liner]
|
|
142
|
+
- Architecture: [one-liner]
|
|
143
|
+
- Critical pitfall: [one-liner]"
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
## Step 8: Return Summary
|
|
147
|
+
|
|
148
|
+
Return brief confirmation with key points for the orchestrator.
|
|
149
|
+
|
|
150
|
+
</execution_flow>
|
|
151
|
+
|
|
152
|
+
<output_format>
|
|
153
|
+
|
|
154
|
+
Use template: ~/.claude/mindsystem/templates/research-project/SUMMARY.md
|
|
155
|
+
|
|
156
|
+
Key sections:
|
|
157
|
+
- Executive Summary (2-3 paragraphs)
|
|
158
|
+
- Key Findings (summaries from each research file)
|
|
159
|
+
- Implications for Roadmap (phase suggestions with rationale)
|
|
160
|
+
- Confidence Assessment (honest evaluation)
|
|
161
|
+
- Sources (aggregated from research files)
|
|
162
|
+
|
|
163
|
+
</output_format>
|
|
164
|
+
|
|
165
|
+
<structured_returns>
|
|
166
|
+
|
|
167
|
+
## Synthesis Complete
|
|
168
|
+
|
|
169
|
+
When SUMMARY.md is written and committed:
|
|
170
|
+
|
|
171
|
+
```markdown
|
|
172
|
+
## SYNTHESIS COMPLETE
|
|
173
|
+
|
|
174
|
+
**Files synthesized:**
|
|
175
|
+
- .planning/research/STACK.md
|
|
176
|
+
- .planning/research/FEATURES.md
|
|
177
|
+
- .planning/research/ARCHITECTURE.md
|
|
178
|
+
- .planning/research/PITFALLS.md
|
|
179
|
+
|
|
180
|
+
**Output:** .planning/research/SUMMARY.md
|
|
181
|
+
|
|
182
|
+
### Executive Summary
|
|
183
|
+
|
|
184
|
+
[2-3 sentence distillation]
|
|
185
|
+
|
|
186
|
+
### Roadmap Implications
|
|
187
|
+
|
|
188
|
+
Suggested phases: [N]
|
|
189
|
+
|
|
190
|
+
1. **[Phase name]** — [one-liner rationale]
|
|
191
|
+
2. **[Phase name]** — [one-liner rationale]
|
|
192
|
+
3. **[Phase name]** — [one-liner rationale]
|
|
193
|
+
|
|
194
|
+
### Research Flags
|
|
195
|
+
|
|
196
|
+
Needs research: Phase [X], Phase [Y]
|
|
197
|
+
Standard patterns: Phase [Z]
|
|
198
|
+
|
|
199
|
+
### Confidence
|
|
200
|
+
|
|
201
|
+
Overall: [HIGH/MEDIUM/LOW]
|
|
202
|
+
Gaps: [list any gaps]
|
|
203
|
+
|
|
204
|
+
### Ready for Requirements
|
|
205
|
+
|
|
206
|
+
SUMMARY.md committed. Orchestrator can proceed to requirements definition.
|
|
207
|
+
```
|
|
208
|
+
|
|
209
|
+
## Synthesis Blocked
|
|
210
|
+
|
|
211
|
+
When unable to proceed:
|
|
212
|
+
|
|
213
|
+
```markdown
|
|
214
|
+
## SYNTHESIS BLOCKED
|
|
215
|
+
|
|
216
|
+
**Blocked by:** [issue]
|
|
217
|
+
|
|
218
|
+
**Missing files:**
|
|
219
|
+
- [list any missing research files]
|
|
220
|
+
|
|
221
|
+
**Awaiting:** [what's needed]
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
</structured_returns>
|
|
225
|
+
|
|
226
|
+
<success_criteria>
|
|
227
|
+
|
|
228
|
+
Synthesis is complete when:
|
|
229
|
+
|
|
230
|
+
- [ ] All 4 research files read
|
|
231
|
+
- [ ] Executive summary captures key conclusions
|
|
232
|
+
- [ ] Key findings extracted from each file
|
|
233
|
+
- [ ] Roadmap implications include phase suggestions
|
|
234
|
+
- [ ] Research flags identify which phases need deeper research
|
|
235
|
+
- [ ] Confidence assessed honestly
|
|
236
|
+
- [ ] Gaps identified for later attention
|
|
237
|
+
- [ ] SUMMARY.md follows template format
|
|
238
|
+
- [ ] File committed to git
|
|
239
|
+
- [ ] Structured return provided to orchestrator
|
|
240
|
+
|
|
241
|
+
Quality indicators:
|
|
242
|
+
|
|
243
|
+
- **Synthesized, not concatenated:** Findings are integrated, not just copied
|
|
244
|
+
- **Opinionated:** Clear recommendations emerge from combined research
|
|
245
|
+
- **Actionable:** Roadmapper can structure phases based on implications
|
|
246
|
+
- **Honest:** Confidence levels reflect actual source quality
|
|
247
|
+
|
|
248
|
+
</success_criteria>
|