@devobsessed/code-captain 0.0.3
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 +214 -0
- package/bin/install.js +1048 -0
- package/claude-code/README.md +276 -0
- package/claude-code/agents/code-captain.md +121 -0
- package/claude-code/agents/spec-generator.md +271 -0
- package/claude-code/agents/story-creator.md +309 -0
- package/claude-code/agents/tech-spec.md +440 -0
- package/claude-code/commands/cc-initialize.md +520 -0
- package/copilot/README.md +210 -0
- package/copilot/chatmodes/Code Captain.chatmode.md +60 -0
- package/copilot/docs/best-practices.md +74 -0
- package/copilot/prompts/create-adr.prompt.md +468 -0
- package/copilot/prompts/create-spec.prompt.md +430 -0
- package/copilot/prompts/edit-spec.prompt.md +396 -0
- package/copilot/prompts/execute-task.prompt.md +144 -0
- package/copilot/prompts/explain-code.prompt.md +292 -0
- package/copilot/prompts/initialize.prompt.md +65 -0
- package/copilot/prompts/new-command.prompt.md +310 -0
- package/copilot/prompts/plan-product.prompt.md +450 -0
- package/copilot/prompts/research.prompt.md +329 -0
- package/copilot/prompts/status.prompt.md +424 -0
- package/copilot/prompts/swab.prompt.md +217 -0
- package/cursor/README.md +224 -0
- package/cursor/cc.md +183 -0
- package/cursor/cc.mdc +69 -0
- package/cursor/commands/create-adr.md +504 -0
- package/cursor/commands/create-spec.md +430 -0
- package/cursor/commands/edit-spec.md +405 -0
- package/cursor/commands/execute-task.md +514 -0
- package/cursor/commands/explain-code.md +289 -0
- package/cursor/commands/initialize.md +397 -0
- package/cursor/commands/new-command.md +312 -0
- package/cursor/commands/plan-product.md +466 -0
- package/cursor/commands/research.md +317 -0
- package/cursor/commands/status.md +413 -0
- package/cursor/commands/swab.md +209 -0
- package/cursor/docs/best-practices.md +74 -0
- package/cursor/integrations/azure-devops/create-azure-work-items.md +403 -0
- package/cursor/integrations/azure-devops/sync-azure-work-items.md +486 -0
- package/cursor/integrations/github/create-github-issues.md +765 -0
- package/cursor/integrations/github/scripts/create-issues-batch.sh +272 -0
- package/cursor/integrations/github/sync-github-issues.md +237 -0
- package/cursor/integrations/github/sync.md +305 -0
- package/manifest.json +381 -0
- package/package.json +58 -0
- package/windsurf/README.md +254 -0
- package/windsurf/rules/cc.md +5 -0
- package/windsurf/workflows/create-adr.md +331 -0
- package/windsurf/workflows/create-spec.md +280 -0
- package/windsurf/workflows/edit-spec.md +273 -0
- package/windsurf/workflows/execute-task.md +276 -0
- package/windsurf/workflows/explain-code.md +292 -0
- package/windsurf/workflows/initialize.md +298 -0
- package/windsurf/workflows/new-command.md +321 -0
- package/windsurf/workflows/status.md +213 -0
|
@@ -0,0 +1,317 @@
|
|
|
1
|
+
# Research Command
|
|
2
|
+
|
|
3
|
+
## Purpose
|
|
4
|
+
|
|
5
|
+
Conduct systematic research on a topic using structured phases that build upon each other, creating actionable todos and leveraging web search capabilities.
|
|
6
|
+
|
|
7
|
+
## When to Use
|
|
8
|
+
|
|
9
|
+
- Investigating new technologies, frameworks, or tools
|
|
10
|
+
- Understanding problem domains before solution design
|
|
11
|
+
- Competitive analysis and market research
|
|
12
|
+
- Technical feasibility studies
|
|
13
|
+
- Learning about best practices in unfamiliar areas
|
|
14
|
+
|
|
15
|
+
## Process
|
|
16
|
+
|
|
17
|
+
### Phase 1: Define Research Scope
|
|
18
|
+
|
|
19
|
+
**Objective:** Establish clear research boundaries and questions
|
|
20
|
+
|
|
21
|
+
**Actions:**
|
|
22
|
+
|
|
23
|
+
1. Create todos for the research phases using `todo_write`
|
|
24
|
+
2. Define primary research question(s)
|
|
25
|
+
3. Identify key stakeholders and their information needs
|
|
26
|
+
4. Set success criteria for the research
|
|
27
|
+
|
|
28
|
+
**Todo Structure:**
|
|
29
|
+
|
|
30
|
+
```
|
|
31
|
+
- Phase 1: Define scope and questions [in_progress]
|
|
32
|
+
- Phase 2: Initial discovery [pending]
|
|
33
|
+
- Phase 3: Deep dive analysis [pending]
|
|
34
|
+
- Phase 4: Synthesis and recommendations [pending]
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
### Phase 2: Initial Discovery
|
|
38
|
+
|
|
39
|
+
**Objective:** Gather broad understanding of the topic landscape
|
|
40
|
+
|
|
41
|
+
**Actions:**
|
|
42
|
+
|
|
43
|
+
1. Use `web_search` with broad search terms related to your topic
|
|
44
|
+
2. Search for:
|
|
45
|
+
- Overview articles and introductory content
|
|
46
|
+
- Current trends and recent developments
|
|
47
|
+
- Key players and thought leaders
|
|
48
|
+
- Common terminology and concepts
|
|
49
|
+
3. Document initial findings and emerging themes
|
|
50
|
+
4. Identify knowledge gaps that need deeper investigation
|
|
51
|
+
|
|
52
|
+
**Search Strategy:**
|
|
53
|
+
|
|
54
|
+
- Start with general terms: "[topic] overview", "[topic] 2024", "[topic] trends"
|
|
55
|
+
- Look for authoritative sources: documentation, whitepapers, industry reports
|
|
56
|
+
- Note recurring themes and terminology for Phase 3
|
|
57
|
+
|
|
58
|
+
### Phase 3: Deep Dive Analysis
|
|
59
|
+
|
|
60
|
+
**Objective:** Investigate specific aspects identified in Phase 2
|
|
61
|
+
|
|
62
|
+
**Actions:**
|
|
63
|
+
|
|
64
|
+
1. Use `web_search` with specific, targeted queries based on Phase 2 findings
|
|
65
|
+
2. Research specific sub-topics:
|
|
66
|
+
- Technical implementation details
|
|
67
|
+
- Pros and cons of different approaches
|
|
68
|
+
- Real-world case studies and examples
|
|
69
|
+
- Performance metrics and benchmarks
|
|
70
|
+
3. Compare alternatives and trade-offs
|
|
71
|
+
4. Validate claims from multiple sources
|
|
72
|
+
|
|
73
|
+
**Search Strategy:**
|
|
74
|
+
|
|
75
|
+
- Use specific terminology discovered in Phase 2
|
|
76
|
+
- Search for: "[specific approach] vs [alternative]", "[topic] case study", "[topic] performance"
|
|
77
|
+
- Look for criticism and limitations, not just benefits
|
|
78
|
+
|
|
79
|
+
### Phase 4: Synthesis and Recommendations
|
|
80
|
+
|
|
81
|
+
**Objective:** Transform research into actionable insights and document findings
|
|
82
|
+
|
|
83
|
+
**Actions:**
|
|
84
|
+
|
|
85
|
+
1. Synthesize findings into key insights
|
|
86
|
+
2. Create recommendations based on research
|
|
87
|
+
3. Identify next steps or areas requiring further investigation
|
|
88
|
+
4. Document sources and evidence for claims
|
|
89
|
+
5. Determine current date using robust file system method (see Date Determination Process below)
|
|
90
|
+
6. Create research document in `.code-captain/research/` folder using the standardized format below
|
|
91
|
+
7. Present findings in appropriate format (ADR, proposal, summary document)
|
|
92
|
+
|
|
93
|
+
**Deliverables:**
|
|
94
|
+
|
|
95
|
+
- Executive summary of key findings
|
|
96
|
+
- Pros/cons analysis of options
|
|
97
|
+
- Specific recommendations with rationale
|
|
98
|
+
- Risk assessment and mitigation strategies
|
|
99
|
+
- Further research needs
|
|
100
|
+
- **Research document:** `.code-captain/research/[DATE]-[topic-name]-research.md` (get DATE using file system method below)
|
|
101
|
+
|
|
102
|
+
## Output Structure
|
|
103
|
+
|
|
104
|
+
### Research Summary
|
|
105
|
+
|
|
106
|
+
- **Research Question(s):** [What you set out to learn]
|
|
107
|
+
- **Key Findings:** [3-5 bullet points of most important discoveries]
|
|
108
|
+
- **Recommendations:** [Actionable next steps based on research]
|
|
109
|
+
|
|
110
|
+
### Detailed Findings
|
|
111
|
+
|
|
112
|
+
- **Background/Context:** [Setting the stage]
|
|
113
|
+
- **Current State:** [What exists today]
|
|
114
|
+
- **Options Analysis:** [Comparison of alternatives]
|
|
115
|
+
- **Evidence:** [Supporting data, quotes, sources]
|
|
116
|
+
|
|
117
|
+
### Next Steps
|
|
118
|
+
|
|
119
|
+
- **Immediate Actions:** [What to do next]
|
|
120
|
+
- **Further Research:** [What questions remain]
|
|
121
|
+
- **Decision Points:** [Key choices that need to be made]
|
|
122
|
+
|
|
123
|
+
## Date Determination Process
|
|
124
|
+
|
|
125
|
+
### Primary Method: File System Timestamp
|
|
126
|
+
|
|
127
|
+
1. **CREATE** directory if not exists: `.code-captain/research/`
|
|
128
|
+
2. **CREATE** temporary file: `.code-captain/research/.date-check`
|
|
129
|
+
3. **READ** file creation timestamp from filesystem
|
|
130
|
+
4. **EXTRACT** date in YYYY-MM-DD format
|
|
131
|
+
5. **DELETE** temporary file
|
|
132
|
+
6. **STORE** date in variable for folder naming
|
|
133
|
+
|
|
134
|
+
### Fallback Method: User Confirmation
|
|
135
|
+
|
|
136
|
+
If file system method fails:
|
|
137
|
+
|
|
138
|
+
1. **STATE**: "I need to confirm today's date for the research folder"
|
|
139
|
+
2. **ASK**: "What is today's date? (YYYY-MM-DD format)"
|
|
140
|
+
3. **WAIT** for user response
|
|
141
|
+
4. **VALIDATE** format matches `^\d{4}-\d{2}-\d{2}$`
|
|
142
|
+
- year: 2024-2030
|
|
143
|
+
- month: 01-12
|
|
144
|
+
- day: 01-31
|
|
145
|
+
5. **STORE** date for folder naming
|
|
146
|
+
|
|
147
|
+
### Error Handling
|
|
148
|
+
|
|
149
|
+
- **IF** date_invalid: USE fallback_method
|
|
150
|
+
- **IF** both_methods_fail: ERROR "Unable to determine current date"
|
|
151
|
+
|
|
152
|
+
## Research Document Template
|
|
153
|
+
|
|
154
|
+
**First, determine the current date using the process above.**
|
|
155
|
+
|
|
156
|
+
Create a markdown file in `.code-captain/research/[DATE]-[topic-name]-research.md` where `[DATE]` is determined using the robust date process.
|
|
157
|
+
|
|
158
|
+
**Example:** `.code-captain/research/2024-01-15-blockchain-supply-chain-research.md`
|
|
159
|
+
|
|
160
|
+
Use the following structure:
|
|
161
|
+
|
|
162
|
+
```markdown
|
|
163
|
+
# [Topic Name] Research
|
|
164
|
+
|
|
165
|
+
**Date:** [Use date from file system determination process]
|
|
166
|
+
**Researcher:** [Name]
|
|
167
|
+
**Status:** [In Progress/Complete]
|
|
168
|
+
|
|
169
|
+
## Research Question(s)
|
|
170
|
+
|
|
171
|
+
[Primary questions this research aimed to answer]
|
|
172
|
+
|
|
173
|
+
## Executive Summary
|
|
174
|
+
|
|
175
|
+
[2-3 paragraph overview of key findings and recommendations]
|
|
176
|
+
|
|
177
|
+
## Background & Context
|
|
178
|
+
|
|
179
|
+
[Why this research was needed, current situation, stakeholders involved]
|
|
180
|
+
|
|
181
|
+
## Methodology
|
|
182
|
+
|
|
183
|
+
[How the research was conducted, sources used, timeframe]
|
|
184
|
+
|
|
185
|
+
## Key Findings
|
|
186
|
+
|
|
187
|
+
### Finding 1: [Title]
|
|
188
|
+
|
|
189
|
+
- **Evidence:** [Supporting data/sources]
|
|
190
|
+
- **Implications:** [What this means for the project/decision]
|
|
191
|
+
|
|
192
|
+
### Finding 2: [Title]
|
|
193
|
+
|
|
194
|
+
- **Evidence:** [Supporting data/sources]
|
|
195
|
+
- **Implications:** [What this means for the project/decision]
|
|
196
|
+
|
|
197
|
+
[Continue for each major finding...]
|
|
198
|
+
|
|
199
|
+
## Options Analysis
|
|
200
|
+
|
|
201
|
+
### Option 1: [Name]
|
|
202
|
+
|
|
203
|
+
- **Pros:** [Benefits and advantages]
|
|
204
|
+
- **Cons:** [Drawbacks and limitations]
|
|
205
|
+
- **Cost/Effort:** [Implementation requirements]
|
|
206
|
+
- **Risk Level:** [High/Medium/Low with explanation]
|
|
207
|
+
|
|
208
|
+
### Option 2: [Name]
|
|
209
|
+
|
|
210
|
+
- **Pros:** [Benefits and advantages]
|
|
211
|
+
- **Cons:** [Drawbacks and limitations]
|
|
212
|
+
- **Cost/Effort:** [Implementation requirements]
|
|
213
|
+
- **Risk Level:** [High/Medium/Low with explanation]
|
|
214
|
+
|
|
215
|
+
[Continue for each option...]
|
|
216
|
+
|
|
217
|
+
## Recommendations
|
|
218
|
+
|
|
219
|
+
### Primary Recommendation
|
|
220
|
+
|
|
221
|
+
[Specific recommended course of action with rationale]
|
|
222
|
+
|
|
223
|
+
### Alternative Approaches
|
|
224
|
+
|
|
225
|
+
[Secondary options if primary recommendation isn't feasible]
|
|
226
|
+
|
|
227
|
+
### Implementation Considerations
|
|
228
|
+
|
|
229
|
+
[Key factors to consider when moving forward]
|
|
230
|
+
|
|
231
|
+
## Risks & Mitigation
|
|
232
|
+
|
|
233
|
+
- **Risk 1:** [Description] → **Mitigation:** [How to address]
|
|
234
|
+
- **Risk 2:** [Description] → **Mitigation:** [How to address]
|
|
235
|
+
|
|
236
|
+
## Further Research Needed
|
|
237
|
+
|
|
238
|
+
- [Question/area that needs additional investigation]
|
|
239
|
+
- [Question/area that needs additional investigation]
|
|
240
|
+
|
|
241
|
+
## Sources
|
|
242
|
+
|
|
243
|
+
- [Source 1 with URL and access date]
|
|
244
|
+
- [Source 2 with URL and access date]
|
|
245
|
+
- [Continue listing all sources used...]
|
|
246
|
+
|
|
247
|
+
## Appendix
|
|
248
|
+
|
|
249
|
+
[Additional detailed information, raw data, extended quotes, etc.]
|
|
250
|
+
```
|
|
251
|
+
|
|
252
|
+
## Best Practices
|
|
253
|
+
|
|
254
|
+
### Search Strategy
|
|
255
|
+
|
|
256
|
+
- Start broad, then narrow down
|
|
257
|
+
- Use multiple search terms and phrasings
|
|
258
|
+
- Look for recent content (last 1-2 years) for rapidly evolving topics
|
|
259
|
+
- Cross-reference information from multiple sources
|
|
260
|
+
- Search for both benefits AND criticisms
|
|
261
|
+
|
|
262
|
+
### Critical Thinking
|
|
263
|
+
|
|
264
|
+
- Question assumptions and biases in sources
|
|
265
|
+
- Look for evidence, not just opinions
|
|
266
|
+
- Consider the source's credibility and potential conflicts of interest
|
|
267
|
+
- Distinguish between correlation and causation
|
|
268
|
+
- Identify what information is missing
|
|
269
|
+
|
|
270
|
+
### Documentation
|
|
271
|
+
|
|
272
|
+
- Keep track of sources for all claims
|
|
273
|
+
- Note the date of information (especially for fast-moving topics)
|
|
274
|
+
- Document your search process for reproducibility
|
|
275
|
+
- Save important quotes with proper attribution
|
|
276
|
+
|
|
277
|
+
## Common Pitfalls to Avoid
|
|
278
|
+
|
|
279
|
+
- Confirmation bias (only seeking information that supports preconceived notions)
|
|
280
|
+
- Stopping research too early when findings seem obvious
|
|
281
|
+
- Not considering implementation challenges
|
|
282
|
+
- Ignoring edge cases or limitations
|
|
283
|
+
- Failing to consider stakeholder perspectives beyond your own
|
|
284
|
+
|
|
285
|
+
## Example Todo Progression
|
|
286
|
+
|
|
287
|
+
**Initial:**
|
|
288
|
+
|
|
289
|
+
```
|
|
290
|
+
- Research blockchain solutions for supply chain [in_progress]
|
|
291
|
+
- Analyze implementation approaches [pending]
|
|
292
|
+
- Evaluate vendor options [pending]
|
|
293
|
+
- Create research document in .code-captain/research/ [pending]
|
|
294
|
+
- Create recommendation report [pending]
|
|
295
|
+
```
|
|
296
|
+
|
|
297
|
+
**After Phase 2:**
|
|
298
|
+
|
|
299
|
+
```
|
|
300
|
+
- Research blockchain solutions for supply chain [completed]
|
|
301
|
+
- Analyze implementation approaches [in_progress]
|
|
302
|
+
- Evaluate vendor options [pending]
|
|
303
|
+
- Determine date using file system method [pending]
|
|
304
|
+
- Create research document in .code-captain/research/ [pending]
|
|
305
|
+
- Create recommendation report [pending]
|
|
306
|
+
```
|
|
307
|
+
|
|
308
|
+
**Final:**
|
|
309
|
+
|
|
310
|
+
```
|
|
311
|
+
- Research blockchain solutions for supply chain [completed]
|
|
312
|
+
- Analyze implementation approaches [completed]
|
|
313
|
+
- Evaluate vendor options [completed]
|
|
314
|
+
- Determine date using file system method [completed]
|
|
315
|
+
- Create research document in .code-captain/research/ [completed]
|
|
316
|
+
- Create recommendation report [completed]
|
|
317
|
+
```
|