agileflow 2.73.0 → 2.75.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 +3 -3
- package/package.json +1 -1
- package/scripts/agileflow-configure.js +315 -0
- package/src/core/agents/accessibility.md +1 -1
- package/src/core/agents/adr-writer.md +6 -6
- package/src/core/agents/analytics.md +1 -1
- package/src/core/agents/api.md +130 -41
- package/src/core/agents/ci.md +3 -3
- package/src/core/agents/compliance.md +1 -1
- package/src/core/agents/database.md +121 -36
- package/src/core/agents/datamigration.md +1 -1
- package/src/core/agents/design.md +1 -1
- package/src/core/agents/devops.md +2 -2
- package/src/core/agents/documentation.md +1 -1
- package/src/core/agents/epic-planner.md +4 -4
- package/src/core/agents/integrations.md +3 -3
- package/src/core/agents/mentor.md +6 -6
- package/src/core/agents/mobile.md +1 -1
- package/src/core/agents/monitoring.md +1 -1
- package/src/core/agents/performance.md +1 -1
- package/src/core/agents/product.md +3 -3
- package/src/core/agents/qa.md +1 -1
- package/src/core/agents/refactor.md +1 -1
- package/src/core/agents/security.md +4 -4
- package/src/core/agents/testing.md +2 -2
- package/src/core/agents/ui.md +129 -44
- package/src/core/commands/babysit.md +137 -0
- package/src/core/commands/blockers.md +3 -3
- package/src/core/commands/configure.md +88 -1
- package/src/core/commands/context/export.md +99 -0
- package/src/core/commands/context/full.md +172 -0
- package/src/core/commands/context/note.md +128 -0
- package/src/core/commands/research/ask.md +453 -0
- package/src/core/commands/research/import.md +287 -0
- package/src/core/commands/research/list.md +93 -0
- package/src/core/commands/research/view.md +113 -0
- package/src/core/experts/research/expertise.yaml +2 -2
- package/src/core/commands/context.md +0 -417
- package/src/core/commands/research.md +0 -124
|
@@ -1,417 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Generate context export for web AI tools
|
|
3
|
-
argument-hint: [MODE=full|export|note|research|import] [NOTE=<text>] [TOPIC=<text>] [DETAILS=<text>] [CONTENT=<text>] [SOURCE=<url>]
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
<!-- COMPACT_SUMMARY_START
|
|
7
|
-
This section is extracted by the PreCompact hook to preserve essential context across conversation compacts.
|
|
8
|
-
-->
|
|
9
|
-
|
|
10
|
-
## Compact Summary
|
|
11
|
-
|
|
12
|
-
Web AI Context Manager - Generates/exports/manages project context briefs for web AI tools (ChatGPT, Perplexity, Gemini, Claude web).
|
|
13
|
-
|
|
14
|
-
### Critical Behavioral Rules
|
|
15
|
-
- **ALWAYS create TodoWrite list** for MODE=full, MODE=research, and MODE=import to track multi-step workflows
|
|
16
|
-
- **Diff-first approach**: Show changes and wait for YES/NO confirmation before ANY file writes
|
|
17
|
-
- **Preserve user-written content**: Only update managed sections in docs/context.md
|
|
18
|
-
- **No writes in export mode**: MODE=export outputs text only, never writes files
|
|
19
|
-
- **Research is two-step**: STEP 1 generates prompt, STEP 2 stores results when user returns
|
|
20
|
-
- **Import is one-step**: Process CONTENT immediately and create research file
|
|
21
|
-
- **Link research files**: Always reference research from ADRs/Epics/Stories that use it
|
|
22
|
-
|
|
23
|
-
### Tool Usage Examples
|
|
24
|
-
|
|
25
|
-
**TodoWrite** (for all modes requiring multi-step tracking):
|
|
26
|
-
```xml
|
|
27
|
-
<invoke name="TodoWrite">
|
|
28
|
-
<parameter name="content">1. Read existing docs/context.md
|
|
29
|
-
2. Gather sources (status.json, bus/log.jsonl, epics)
|
|
30
|
-
3. Extract key information
|
|
31
|
-
4. Generate managed sections
|
|
32
|
-
5. Show diff for review
|
|
33
|
-
6. Apply changes after YES</parameter>
|
|
34
|
-
<parameter name="status">in-progress</parameter>
|
|
35
|
-
<parameter name="activeForm">1</parameter>
|
|
36
|
-
</invoke>
|
|
37
|
-
```
|
|
38
|
-
|
|
39
|
-
**Edit** (when writing context or research files):
|
|
40
|
-
```xml
|
|
41
|
-
<invoke name="Edit">
|
|
42
|
-
<parameter name="file_path">/full/path/to/docs/context.md</parameter>
|
|
43
|
-
<parameter name="old_string"><!-- MANAGED_SECTION -->\n[old content]\n<!-- END_MANAGED --></parameter>
|
|
44
|
-
<parameter name="new_string"><!-- MANAGED_SECTION -->\n[new content]\n<!-- END_MANAGED --></parameter>
|
|
45
|
-
</invoke>
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
**AskUserQuestion** (when needing confirmation):
|
|
49
|
-
```xml
|
|
50
|
-
<invoke name="AskUserQuestion">
|
|
51
|
-
<parameter name="questions">[{"question": "Apply these changes?", "header": "Diff Preview", "multiSelect": false, "options": [{"label": "Yes, update", "description": "Write changes"}, {"label": "No, abort", "description": "Cancel"}]}]</parameter>
|
|
52
|
-
</invoke>
|
|
53
|
-
```
|
|
54
|
-
|
|
55
|
-
### Core Workflow
|
|
56
|
-
|
|
57
|
-
**MODE=full**: Create todo list → Read docs/context.md → Gather sources → Generate sections → Show diff → Apply after YES
|
|
58
|
-
|
|
59
|
-
**MODE=export**: Read docs/context.md → Output ≤300 line excerpt → No file writes
|
|
60
|
-
|
|
61
|
-
**MODE=note**: Create todo list → Append timestamped note → Show diff → Apply after YES
|
|
62
|
-
|
|
63
|
-
**MODE=research**: Create todo list → STEP 1: Generate prompt → STEP 2: Format & save to docs/10-research/
|
|
64
|
-
|
|
65
|
-
**MODE=import**: Create todo list → Validate inputs → Process content → Save to docs/10-research/
|
|
66
|
-
|
|
67
|
-
### Key Files
|
|
68
|
-
- docs/context.md - Main context brief
|
|
69
|
-
- docs/10-research/YYYYMMDD-topic-slug.md - Research storage
|
|
70
|
-
- docs/10-research/README.md - Research index
|
|
71
|
-
- status.json - Current work tracking
|
|
72
|
-
- bus/log.jsonl - Recent progress messages
|
|
73
|
-
|
|
74
|
-
<!-- COMPACT_SUMMARY_END -->
|
|
75
|
-
|
|
76
|
-
# context
|
|
77
|
-
|
|
78
|
-
Generate, export, or manage the web AI context brief.
|
|
79
|
-
|
|
80
|
-
## Prompt
|
|
81
|
-
|
|
82
|
-
ROLE: Web AI Context Manager
|
|
83
|
-
|
|
84
|
-
INPUTS (optional)
|
|
85
|
-
- MODE=full|export|note|research|import (default: full)
|
|
86
|
-
- NOTE=<text> (required if MODE=note)
|
|
87
|
-
- TOPIC=<text> (required if MODE=research or MODE=import)
|
|
88
|
-
- CONTENT=<text> (required if MODE=import - raw content to process)
|
|
89
|
-
- SOURCE=<url> (optional for MODE=import - original source URL)
|
|
90
|
-
|
|
91
|
-
---
|
|
92
|
-
|
|
93
|
-
## MODE=full (default)
|
|
94
|
-
Create/refresh docs/context.md with managed sections.
|
|
95
|
-
|
|
96
|
-
### Objective
|
|
97
|
-
Generate comprehensive context brief for web AI tools (ChatGPT, Perplexity, Gemini, Claude web, etc.) with:
|
|
98
|
-
- What we're building • Current focus • Feature map • Tech/tooling summary
|
|
99
|
-
- Key decisions (ADRs) • Architecture snapshot • Testing & CI
|
|
100
|
-
- Recent progress (last 10 bus messages) • Risks • Next steps
|
|
101
|
-
|
|
102
|
-
### Sources
|
|
103
|
-
If present: status.json, bus/log.jsonl, epics/stories, ADRs, practices, architecture, roadmap/backlog/risks, research index, project manifests, CI, CHANGELOG.
|
|
104
|
-
|
|
105
|
-
### TODO LIST TRACKING
|
|
106
|
-
**CRITICAL**: Immediately create a todo list using TodoWrite tool to track context generation:
|
|
107
|
-
```
|
|
108
|
-
1. Read existing docs/context.md (if exists)
|
|
109
|
-
2. Gather sources (status.json, bus/log.jsonl, epics, stories, ADRs)
|
|
110
|
-
3. Extract key information from each source
|
|
111
|
-
4. Generate/update managed sections
|
|
112
|
-
5. Preserve user-written content
|
|
113
|
-
6. Show diff for review
|
|
114
|
-
7. Apply changes after YES confirmation
|
|
115
|
-
```
|
|
116
|
-
|
|
117
|
-
Mark each step complete as you finish it. This ensures nothing is forgotten.
|
|
118
|
-
|
|
119
|
-
### Rules
|
|
120
|
-
- Update only managed sections
|
|
121
|
-
- Preserve user-written content
|
|
122
|
-
- Diff-first; YES/NO before changes
|
|
123
|
-
|
|
124
|
-
---
|
|
125
|
-
|
|
126
|
-
## MODE=export
|
|
127
|
-
Export a concise context excerpt for web AI tools.
|
|
128
|
-
|
|
129
|
-
### Task
|
|
130
|
-
Read docs/context.md and output only:
|
|
131
|
-
- Last updated • What we're building • Current focus
|
|
132
|
-
- Tech/tooling summary • Key decisions (ADRs)
|
|
133
|
-
- Feature map (one line per epic) • Next steps
|
|
134
|
-
|
|
135
|
-
### Constraints
|
|
136
|
-
- LIMIT ≤ 300 lines
|
|
137
|
-
- No file writes
|
|
138
|
-
- End with "Paste this excerpt into your web AI tool (ChatGPT, Perplexity, Gemini, etc.) to load context."
|
|
139
|
-
|
|
140
|
-
---
|
|
141
|
-
|
|
142
|
-
## MODE=note
|
|
143
|
-
Append a timestamped note to the context file.
|
|
144
|
-
|
|
145
|
-
### Input
|
|
146
|
-
NOTE=<1–5 line note>
|
|
147
|
-
|
|
148
|
-
### Action
|
|
149
|
-
Append under "Notes" section with ISO timestamp.
|
|
150
|
-
Create section if missing.
|
|
151
|
-
|
|
152
|
-
### Rules
|
|
153
|
-
Diff-first; YES/NO before changes.
|
|
154
|
-
|
|
155
|
-
---
|
|
156
|
-
|
|
157
|
-
## MODE=research
|
|
158
|
-
Build a comprehensive research prompt for web AI tools, then store results when user returns.
|
|
159
|
-
|
|
160
|
-
### Input
|
|
161
|
-
- TOPIC=<free text> (required)
|
|
162
|
-
- DETAILS=<constraints/deadlines> (optional)
|
|
163
|
-
|
|
164
|
-
### Sources
|
|
165
|
-
context.md; status.json; epics/stories; ADRs; project manifests; CI config.
|
|
166
|
-
|
|
167
|
-
### TODO LIST TRACKING
|
|
168
|
-
**CRITICAL**: Immediately create a todo list using TodoWrite tool to track research workflow:
|
|
169
|
-
```
|
|
170
|
-
1. Generate research prompt for user to paste into ChatGPT
|
|
171
|
-
2. Wait for user to return with research results
|
|
172
|
-
3. Format research into structured markdown
|
|
173
|
-
4. Save research to docs/10-research/YYYYMMDD-topic-slug.md
|
|
174
|
-
5. Update docs/10-research/README.md index
|
|
175
|
-
6. Ask user about creating ADR/Epic/Story from research
|
|
176
|
-
7. Link research file from created ADR/Epic/Story (if applicable)
|
|
177
|
-
```
|
|
178
|
-
|
|
179
|
-
Mark each step complete as you finish it. This ensures nothing is forgotten.
|
|
180
|
-
|
|
181
|
-
### Workflow
|
|
182
|
-
|
|
183
|
-
**STEP 1: Generate Research Prompt**
|
|
184
|
-
Output a SINGLE code block prompt for web AI tools (ChatGPT, Perplexity, Gemini, Claude web, etc.) that requests:
|
|
185
|
-
- TL;DR; Step-by-step plan w/ file paths; minimal runnable snippets
|
|
186
|
-
- Config/keys; error handling; analytics hooks
|
|
187
|
-
- Tests (unit/integration/e2e); manual checklist
|
|
188
|
-
- Security/privacy checklist
|
|
189
|
-
- ADR draft (options, decision, consequences)
|
|
190
|
-
- Story breakdown (3–6 stories + AC bullets)
|
|
191
|
-
- Rollback plan; Risks & gotchas
|
|
192
|
-
- PR body template
|
|
193
|
-
- Sourcing rules (official docs/repos; cite title/URL/date)
|
|
194
|
-
- Final "Paste back to Claude Code" checklist
|
|
195
|
-
|
|
196
|
-
Tell user: "Copy this prompt and paste it into ChatGPT/Perplexity. When you return with the results, paste them here and I'll save them to docs/10-research/."
|
|
197
|
-
|
|
198
|
-
**STEP 2: Store Research Results (when user returns)**
|
|
199
|
-
|
|
200
|
-
When user pastes research results back:
|
|
201
|
-
|
|
202
|
-
1. **Format the research** into structured markdown:
|
|
203
|
-
```markdown
|
|
204
|
-
# [Topic Title]
|
|
205
|
-
|
|
206
|
-
**Research Date**: YYYY-MM-DD
|
|
207
|
-
**Topic**: [original topic]
|
|
208
|
-
**Sources**: [List key sources cited]
|
|
209
|
-
|
|
210
|
-
## Summary
|
|
211
|
-
[2-3 paragraph executive summary of findings]
|
|
212
|
-
|
|
213
|
-
## Key Findings
|
|
214
|
-
- [Main point 1 with details]
|
|
215
|
-
- [Main point 2 with details]
|
|
216
|
-
- [Main point 3 with details]
|
|
217
|
-
|
|
218
|
-
## Implementation Approach
|
|
219
|
-
[Step-by-step plan from research]
|
|
220
|
-
|
|
221
|
-
## Code Snippets
|
|
222
|
-
```language
|
|
223
|
-
[Preserve all code snippets exactly as provided]
|
|
224
|
-
```
|
|
225
|
-
|
|
226
|
-
## Security Considerations
|
|
227
|
-
[Security/privacy checklist items]
|
|
228
|
-
|
|
229
|
-
## Testing Strategy
|
|
230
|
-
[Test approach from research]
|
|
231
|
-
|
|
232
|
-
## Risks & Gotchas
|
|
233
|
-
[Potential issues and mitigation]
|
|
234
|
-
|
|
235
|
-
## ADR Recommendation
|
|
236
|
-
[If research suggests architectural decision]
|
|
237
|
-
|
|
238
|
-
## Story Breakdown
|
|
239
|
-
[If research included story suggestions]
|
|
240
|
-
|
|
241
|
-
## References
|
|
242
|
-
- [Source 1: Title, URL, Date]
|
|
243
|
-
- [Source 2: Title, URL, Date]
|
|
244
|
-
```
|
|
245
|
-
|
|
246
|
-
2. **Save to** `docs/10-research/YYYYMMDD-<topic-slug>.md`
|
|
247
|
-
|
|
248
|
-
3. **Update** `docs/10-research/README.md` with new entry (create if missing)
|
|
249
|
-
|
|
250
|
-
4. **Ask user**: "Would you like me to:
|
|
251
|
-
- Create an ADR referencing this research?
|
|
252
|
-
- Create an Epic/Stories based on this research?
|
|
253
|
-
- Link this research to existing Epic/Story?"
|
|
254
|
-
|
|
255
|
-
5. **If creating ADR/Epic/Story**: Add research reference at the top:
|
|
256
|
-
```markdown
|
|
257
|
-
**Research**: See [Topic Research](../10-research/YYYYMMDD-topic-slug.md)
|
|
258
|
-
```
|
|
259
|
-
|
|
260
|
-
### Rules
|
|
261
|
-
- STEP 1: No file writes, copy-paste ready prompt only
|
|
262
|
-
- STEP 2: Format and preserve ALL content (summaries retain context, code snippets, main points)
|
|
263
|
-
- STEP 2: Diff-first; YES/NO before writing research file
|
|
264
|
-
- STEP 2: Always link research file from ADRs/Epics/Stories that use it
|
|
265
|
-
|
|
266
|
-
---
|
|
267
|
-
|
|
268
|
-
## MODE=import
|
|
269
|
-
Import raw content (transcripts, articles, notes) and convert to structured research file.
|
|
270
|
-
|
|
271
|
-
### Input
|
|
272
|
-
- TOPIC=<text> (required - name for the research file)
|
|
273
|
-
- CONTENT=<text> (required - raw content to process: transcript, article, notes, etc.)
|
|
274
|
-
- SOURCE=<url> (optional - original source URL for reference)
|
|
275
|
-
|
|
276
|
-
### Use Cases
|
|
277
|
-
- YouTube video transcripts
|
|
278
|
-
- Conference talk notes
|
|
279
|
-
- Podcast transcripts
|
|
280
|
-
- Blog posts / articles
|
|
281
|
-
- Documentation pages
|
|
282
|
-
- Forum discussions / Stack Overflow threads
|
|
283
|
-
- Meeting notes
|
|
284
|
-
|
|
285
|
-
### TODO LIST TRACKING
|
|
286
|
-
**CRITICAL**: Immediately create a todo list using TodoWrite tool to track import workflow:
|
|
287
|
-
```
|
|
288
|
-
1. Validate TOPIC and CONTENT are provided
|
|
289
|
-
2. Analyze and summarize key points from content
|
|
290
|
-
3. Extract any code snippets
|
|
291
|
-
4. Generate action items based on content
|
|
292
|
-
5. Create user story suggestions (if applicable)
|
|
293
|
-
6. Format into structured research markdown
|
|
294
|
-
7. Show diff for review
|
|
295
|
-
8. Save to docs/10-research/YYYYMMDD-topic-slug.md
|
|
296
|
-
9. Update docs/10-research/README.md index
|
|
297
|
-
10. Ask about creating ADR/Epic/Story from research
|
|
298
|
-
```
|
|
299
|
-
|
|
300
|
-
Mark each step complete as you finish it.
|
|
301
|
-
|
|
302
|
-
### Processing Steps
|
|
303
|
-
|
|
304
|
-
1. **Validate Inputs**
|
|
305
|
-
- Verify TOPIC is provided (error if missing)
|
|
306
|
-
- Verify CONTENT is provided (error if missing)
|
|
307
|
-
- SOURCE is optional but recommended for attribution
|
|
308
|
-
|
|
309
|
-
2. **Analyze Content**
|
|
310
|
-
Extract from the raw content:
|
|
311
|
-
- **Summary**: 2-3 paragraph TL;DR of the main points
|
|
312
|
-
- **Key Findings**: Bullet list of important takeaways
|
|
313
|
-
- **Code Snippets**: Any code blocks, commands, or configuration (preserve exactly)
|
|
314
|
-
- **Action Items**: Concrete next steps mentioned or implied
|
|
315
|
-
- **Story Suggestions**: Potential user stories/epics based on content
|
|
316
|
-
|
|
317
|
-
3. **Format Research File**
|
|
318
|
-
```markdown
|
|
319
|
-
# [Topic Title]
|
|
320
|
-
|
|
321
|
-
**Import Date**: YYYY-MM-DD
|
|
322
|
-
**Topic**: [original topic]
|
|
323
|
-
**Source**: [URL if provided, or "Direct import"]
|
|
324
|
-
**Content Type**: [transcript/article/notes/etc.]
|
|
325
|
-
|
|
326
|
-
## Summary
|
|
327
|
-
[2-3 paragraph executive summary of the content]
|
|
328
|
-
|
|
329
|
-
## Key Findings
|
|
330
|
-
- [Main point 1 with details]
|
|
331
|
-
- [Main point 2 with details]
|
|
332
|
-
- [Main point 3 with details]
|
|
333
|
-
- ...
|
|
334
|
-
|
|
335
|
-
## Code Snippets
|
|
336
|
-
[Preserve all code snippets exactly as they appeared]
|
|
337
|
-
```language
|
|
338
|
-
[code here]
|
|
339
|
-
```
|
|
340
|
-
|
|
341
|
-
## Action Items
|
|
342
|
-
- [ ] [Action 1 - concrete next step]
|
|
343
|
-
- [ ] [Action 2 - concrete next step]
|
|
344
|
-
- [ ] [Action 3 - concrete next step]
|
|
345
|
-
|
|
346
|
-
## Story Suggestions
|
|
347
|
-
[If content suggests feature work, list potential stories]
|
|
348
|
-
|
|
349
|
-
### Potential Epic: [Epic Title]
|
|
350
|
-
- **US-XXXX**: [Story 1 title]
|
|
351
|
-
- AC: [acceptance criteria bullet]
|
|
352
|
-
- **US-XXXX**: [Story 2 title]
|
|
353
|
-
- AC: [acceptance criteria bullet]
|
|
354
|
-
|
|
355
|
-
## Raw Content Reference
|
|
356
|
-
<details>
|
|
357
|
-
<summary>Original content (click to expand)</summary>
|
|
358
|
-
|
|
359
|
-
[First 500 chars of original content for reference...]
|
|
360
|
-
</details>
|
|
361
|
-
|
|
362
|
-
## References
|
|
363
|
-
- Source: [URL or "Direct import"]
|
|
364
|
-
- Import date: [YYYY-MM-DD]
|
|
365
|
-
```
|
|
366
|
-
|
|
367
|
-
4. **Save and Index**
|
|
368
|
-
- Save to `docs/10-research/YYYYMMDD-<topic-slug>.md`
|
|
369
|
-
- Update `docs/10-research/README.md` with new entry
|
|
370
|
-
|
|
371
|
-
5. **Offer Next Steps**
|
|
372
|
-
Ask user via AskUserQuestion:
|
|
373
|
-
- Create an ADR referencing this research?
|
|
374
|
-
- Create an Epic/Stories based on the story suggestions?
|
|
375
|
-
- Link this research to an existing Epic/Story?
|
|
376
|
-
|
|
377
|
-
### Rules
|
|
378
|
-
- Diff-first; YES/NO before writing research file
|
|
379
|
-
- Preserve ALL code snippets exactly as provided
|
|
380
|
-
- Generate actionable items (not vague suggestions)
|
|
381
|
-
- Keep raw content reference collapsed to save space
|
|
382
|
-
- Always update the research index
|
|
383
|
-
|
|
384
|
-
---
|
|
385
|
-
|
|
386
|
-
## Usage Examples
|
|
387
|
-
|
|
388
|
-
```bash
|
|
389
|
-
# Generate/refresh full context brief (default)
|
|
390
|
-
/agileflow:context
|
|
391
|
-
/agileflow:context MODE=full
|
|
392
|
-
|
|
393
|
-
# Export concise excerpt for pasting
|
|
394
|
-
/agileflow:context MODE=export
|
|
395
|
-
|
|
396
|
-
# Add a quick note
|
|
397
|
-
/agileflow:context MODE=note NOTE="User reported auth bug in production"
|
|
398
|
-
|
|
399
|
-
# Build research prompt for web AI
|
|
400
|
-
/agileflow:context MODE=research TOPIC="Implement OAuth 2.0 with Google"
|
|
401
|
-
/agileflow:context MODE=research TOPIC="Add Stripe payments" DETAILS="Launch by end of sprint"
|
|
402
|
-
|
|
403
|
-
# Import external content (transcripts, articles, notes)
|
|
404
|
-
/agileflow:context MODE=import TOPIC="React Server Components" CONTENT="[paste transcript here]"
|
|
405
|
-
/agileflow:context MODE=import TOPIC="Stripe Webhooks Tutorial" SOURCE="https://youtube.com/..." CONTENT="[paste transcript here]"
|
|
406
|
-
```
|
|
407
|
-
|
|
408
|
-
---
|
|
409
|
-
|
|
410
|
-
## Output
|
|
411
|
-
|
|
412
|
-
Depending on MODE:
|
|
413
|
-
- **full**: Updated docs/context.md (after YES confirmation)
|
|
414
|
-
- **export**: Text output ready to paste into web AI tool
|
|
415
|
-
- **note**: Appended note to docs/context.md (after YES confirmation)
|
|
416
|
-
- **research**: Research prompt in code block ready to paste into web AI tool
|
|
417
|
-
- **import**: Processed research file saved to docs/10-research/ (after YES confirmation)
|
|
@@ -1,124 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Initialize research note with structured template
|
|
3
|
-
argument-hint: (no arguments)
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# research-init
|
|
7
|
-
|
|
8
|
-
Initialize or save research notes to the research folder.
|
|
9
|
-
|
|
10
|
-
---
|
|
11
|
-
|
|
12
|
-
## STEP 0: Gather Context
|
|
13
|
-
|
|
14
|
-
```bash
|
|
15
|
-
node .agileflow/scripts/obtain-context.js research
|
|
16
|
-
```
|
|
17
|
-
|
|
18
|
-
---
|
|
19
|
-
|
|
20
|
-
## Context Loading (Documentation)
|
|
21
|
-
|
|
22
|
-
**PURPOSE**: Immediately load full context before executing any logic.
|
|
23
|
-
|
|
24
|
-
**ACTIONS**:
|
|
25
|
-
1. Read this command file (`.agileflow/commands/research.md`) in its entirety
|
|
26
|
-
2. Absorb all instructions, rules, and examples
|
|
27
|
-
3. Proceed to execution phase with complete context
|
|
28
|
-
|
|
29
|
-
**WHY**: Prevents incomplete instruction loading and ensures consistent behavior.
|
|
30
|
-
|
|
31
|
-
---
|
|
32
|
-
|
|
33
|
-
<!-- COMPACT_SUMMARY_START -->
|
|
34
|
-
## Compact Summary
|
|
35
|
-
- **Command**: /agileflow:research-init
|
|
36
|
-
- **Purpose**: Initialize or save research notes with structured analysis
|
|
37
|
-
- **Key Actions**: Ensure docs/10-research/ exists → Create/update index → Save research file → Add index entry → Confirm
|
|
38
|
-
|
|
39
|
-
### Tool Usage Examples
|
|
40
|
-
|
|
41
|
-
**TodoWrite** (to track research initialization workflow):
|
|
42
|
-
```xml
|
|
43
|
-
<invoke name="TodoWrite">
|
|
44
|
-
<parameter name="content">1. Ensure docs/10-research/ exists
|
|
45
|
-
2. Create/update docs/10-research/README.md (if missing)
|
|
46
|
-
3. If pasted research content provided: save to docs/10-research/<YYYYMMDD>-<slug>.md
|
|
47
|
-
4. Add entry to README.md index table
|
|
48
|
-
5. Show preview and wait for YES/NO confirmation</parameter>
|
|
49
|
-
<parameter name="status">in-progress</parameter>
|
|
50
|
-
<parameter name="activeForm">1</parameter>
|
|
51
|
-
</invoke>
|
|
52
|
-
```
|
|
53
|
-
|
|
54
|
-
**Write** (to create research file):
|
|
55
|
-
```xml
|
|
56
|
-
<invoke name="Write">
|
|
57
|
-
<parameter name="file_path">/full/path/to/docs/10-research/20251222-session-tracking.md</parameter>
|
|
58
|
-
<parameter name="content"># Session Tracking
|
|
59
|
-
|
|
60
|
-
**Research Date**: 2025-12-22
|
|
61
|
-
**Topic**: Session tracking implementation
|
|
62
|
-
**Sources**: [source citations]
|
|
63
|
-
|
|
64
|
-
## Summary
|
|
65
|
-
[2-3 paragraph executive summary]
|
|
66
|
-
|
|
67
|
-
## Key Findings
|
|
68
|
-
- [Main point 1]
|
|
69
|
-
- [Main point 2]
|
|
70
|
-
|
|
71
|
-
## References
|
|
72
|
-
- [Source 1]
|
|
73
|
-
- [Source 2]</parameter>
|
|
74
|
-
</invoke>
|
|
75
|
-
```
|
|
76
|
-
|
|
77
|
-
**Edit** (to update README.md index):
|
|
78
|
-
```xml
|
|
79
|
-
<invoke name="Edit">
|
|
80
|
-
<parameter name="file_path">/full/path/to/docs/10-research/README.md</parameter>
|
|
81
|
-
<parameter name="old_string">| 2025-12-20 | Old Topic | 20251220-old-topic.md | Summary |</parameter>
|
|
82
|
-
<parameter name="new_string">| 2025-12-22 | Session Tracking | 20251222-session-tracking.md | Research findings about tracking sessions |
|
|
83
|
-
| 2025-12-20 | Old Topic | 20251220-old-topic.md | Summary |</parameter>
|
|
84
|
-
</invoke>
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-
**AskUserQuestion** (for confirmation):
|
|
88
|
-
```xml
|
|
89
|
-
<invoke name="AskUserQuestion">
|
|
90
|
-
<parameter name="questions">[{"question": "Save this research file?", "header": "Preview", "multiSelect": false, "options": [{"label": "Yes, save to docs/10-research/", "description": "Write the research file and update index"}, {"label": "No, abort", "description": "Cancel without saving"}]}]</parameter>
|
|
91
|
-
</invoke>
|
|
92
|
-
```
|
|
93
|
-
|
|
94
|
-
- **File Format**: <YYYYMMDD>-<slug>.md
|
|
95
|
-
- **Index Table**: Date | Topic | Path | Summary in README.md
|
|
96
|
-
- **Workflow**: Diff-first, then YES/NO confirmation
|
|
97
|
-
<!-- COMPACT_SUMMARY_END -->
|
|
98
|
-
|
|
99
|
-
---
|
|
100
|
-
|
|
101
|
-
## Prompt
|
|
102
|
-
|
|
103
|
-
ROLE: Research Initializer
|
|
104
|
-
|
|
105
|
-
OBJECTIVE
|
|
106
|
-
Evaluate and organize research findings with structured analysis. Assess relevance, consider key insights, and examine sources to create comprehensive research documentation.
|
|
107
|
-
|
|
108
|
-
TODO LIST TRACKING
|
|
109
|
-
**CRITICAL**: Immediately create a todo list using TodoWrite tool to track research initialization:
|
|
110
|
-
```
|
|
111
|
-
1. Ensure docs/10-research/ exists
|
|
112
|
-
2. Create/update docs/10-research/README.md (if missing)
|
|
113
|
-
3. If pasted research content provided: save to docs/10-research/<YYYYMMDD>-<slug>.md
|
|
114
|
-
4. Add entry to README.md index table
|
|
115
|
-
5. Show preview and wait for YES/NO confirmation
|
|
116
|
-
```
|
|
117
|
-
|
|
118
|
-
Mark each step complete as you finish it. This ensures nothing is forgotten.
|
|
119
|
-
|
|
120
|
-
ACTIONS
|
|
121
|
-
1) Ensure docs/10-research/ exists with README.md (index table: Date | Topic | Path | Summary).
|
|
122
|
-
2) If pasted research content is provided, save to docs/10-research/<YYYYMMDD>-<slug>.md and add a row to README.md (newest first).
|
|
123
|
-
|
|
124
|
-
Diff-first; YES/NO.
|