@allthingsclaude/blueprints 0.3.0-beta.13 → 0.3.0-beta.14

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.
@@ -18,12 +18,22 @@ Generate a comprehensive PLAN_{NAME}.md file at `{{PLANS_DIR}}/PLAN_{NAME}.md` t
18
18
  - Parse the plan name from the arguments (first word after /plan)
19
19
  - If no name provided, use "UNTITLED"
20
20
 
21
- 2. **Review Context**
21
+ 2. **Collect Reference Files**
22
+ - Check if the conversation includes any reference files (images, videos, screenshots, mockups, PDFs, etc.)
23
+ - If references exist, create the references directory and copy them there:
24
+ ```bash
25
+ mkdir -p {{TASKS_DIR}}/references
26
+ ```
27
+ - Copy each reference file to `{{TASKS_DIR}}/references/`, preserving the original filename
28
+ - In the plan document, reference these files using their new path (e.g., `{{TASKS_DIR}}/references/mockup.png`)
29
+ - This ensures implementing agents can access the references directly from the plan
30
+
31
+ 3. **Review Context**
22
32
  - Check git status for current state
23
33
  - Review recent commits if relevant to the discussion
24
34
  - Read any files that were discussed
25
35
 
26
- 3. **Synthesize Findings**
36
+ 4. **Synthesize Findings**
27
37
  - What problem or opportunity was identified?
28
38
  - What approach was discussed or decided?
29
39
  - What technical considerations were raised?
@@ -201,6 +211,10 @@ Generate `{{PLANS_DIR}}/PLAN_{NAME}.md` with this exact structure:
201
211
 
202
212
  ## 📚 References
203
213
 
214
+ ### Reference Files
215
+ [If reference images, videos, mockups, or other files were provided, list them here with descriptions]
216
+ - `{{TASKS_DIR}}/references/[filename]` - [What this reference shows and how it relates to the plan]
217
+
204
218
  ### Documentation
205
219
  - [Link to CLAUDE.md sections]
206
220
  - [Link to external docs/resources]
@@ -280,6 +294,7 @@ Generate `{{PLANS_DIR}}/PLAN_{NAME}.md` with this exact structure:
280
294
  - Testing and validation approach
281
295
  - Open questions and risks
282
296
  - Success criteria
297
+ - Reference files (images, videos, mockups, PDFs) — copy to `{{TASKS_DIR}}/references/` and link from the plan
283
298
 
284
299
  ❌ **Don't Capture**:
285
300
  - Full conversation transcript
@@ -34,5 +34,6 @@ The agent will:
34
34
  - ✅ Break down tasks into actionable steps
35
35
  - ✅ Note technical considerations and constraints
36
36
  - ✅ List relevant files and references
37
+ - ✅ Copy any reference files (images, videos, mockups) to `{{TASKS_DIR}}/references/` and link them in the plan so implementing agents can consume them
37
38
 
38
39
  Use the Task tool to launch the plan agent (subagent_type="plan") which will autonomously generate the plan document.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@allthingsclaude/blueprints",
3
- "version": "0.3.0-beta.13",
3
+ "version": "0.3.0-beta.14",
4
4
  "description": "Claude Code commands and agents for enhanced AI-assisted development workflows",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",