poly-agent 1.0.5 → 1.0.6
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/package.json
CHANGED
|
@@ -82,3 +82,22 @@ status: [in-progress | completed | blocked | paused]
|
|
|
82
82
|
5. You edit `src/routes/login.ts`
|
|
83
83
|
6. You update `.context/feature-api-auth.md` again
|
|
84
84
|
7. Continue until task complete, then set status to `completed`
|
|
85
|
+
|
|
86
|
+
## Recalling Context
|
|
87
|
+
|
|
88
|
+
When a user asks to recall or resume a context (e.g., "recall feature-auth", "continue from context X", "load context"):
|
|
89
|
+
|
|
90
|
+
1. **Read ONLY the specified context file** from `.context/` - Do NOT scan the entire project
|
|
91
|
+
2. **Trust the context file** - It contains all the information you need
|
|
92
|
+
3. **Summarize the current state** - What was done, what remains
|
|
93
|
+
4. **Confirm understanding** with the user before proceeding
|
|
94
|
+
5. **Only read files listed in "Files Changed"** if you need to check current state
|
|
95
|
+
6. **Continue updating** the same context file as you work
|
|
96
|
+
|
|
97
|
+
**IMPORTANT**: When recalling context, do NOT:
|
|
98
|
+
- Search or scan the entire codebase
|
|
99
|
+
- Read files not mentioned in the context
|
|
100
|
+
- Run broad exploratory searches
|
|
101
|
+
- Assume information beyond what's in the context file
|
|
102
|
+
|
|
103
|
+
If asked to **list contexts**, read the `.context/` directory and show available files with their status.
|
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: Context Recall
|
|
3
|
+
description: Load and resume work from a saved context file.
|
|
4
|
+
---
|
|
5
|
+
# Context Recall
|
|
6
|
+
|
|
7
|
+
You are being asked to **resume work** from a previously saved context.
|
|
8
|
+
|
|
9
|
+
## Instructions
|
|
10
|
+
|
|
11
|
+
1. **Read the context file** specified by the user (from `.context/` directory)
|
|
12
|
+
2. **Understand the state** - Review the summary, files changed, goals, and progress
|
|
13
|
+
3. **Identify next steps** - Look at what was marked as pending or in "Next Steps"
|
|
14
|
+
4. **Resume seamlessly** - Continue the work as if you never left
|
|
15
|
+
|
|
16
|
+
## How to Use
|
|
17
|
+
|
|
18
|
+
The user will provide one of:
|
|
19
|
+
- A context file name: `feature-auth` or `feature-auth.md`
|
|
20
|
+
- A full path: `.context/feature-auth.md`
|
|
21
|
+
- Or ask you to list available contexts
|
|
22
|
+
|
|
23
|
+
## If Asked to List Contexts
|
|
24
|
+
|
|
25
|
+
Read the `.context/` directory and present available context files:
|
|
26
|
+
|
|
27
|
+
```
|
|
28
|
+
Available contexts:
|
|
29
|
+
- feature-auth.md (updated: 2026-01-12)
|
|
30
|
+
- bugfix-api-timeout.md (updated: 2026-01-11)
|
|
31
|
+
- refactor-database.md (updated: 2026-01-10)
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
## After Loading Context
|
|
35
|
+
|
|
36
|
+
1. **Summarize** what you understand about the task
|
|
37
|
+
2. **Confirm** the current state and what remains to be done
|
|
38
|
+
3. **Ask** if the user wants to continue from where it left off, or modify the approach
|
|
39
|
+
4. **Continue updating** the same context file as you make changes
|
|
40
|
+
|
|
41
|
+
## Example Interaction
|
|
42
|
+
|
|
43
|
+
**User**: "Recall context feature-auth"
|
|
44
|
+
|
|
45
|
+
**You**:
|
|
46
|
+
> I've loaded the context for **feature-auth**:
|
|
47
|
+
>
|
|
48
|
+
> **Summary**: Implementing JWT-based authentication for the API
|
|
49
|
+
>
|
|
50
|
+
> **Progress**:
|
|
51
|
+
> - ✅ Created auth middleware
|
|
52
|
+
> - ✅ Set up login route
|
|
53
|
+
> - ⏳ Token refresh logic (in progress)
|
|
54
|
+
> - ⬜ Rate limiting
|
|
55
|
+
>
|
|
56
|
+
> **Last worked on**: `src/auth/refresh.ts`
|
|
57
|
+
>
|
|
58
|
+
> Would you like me to continue with the token refresh logic, or would you prefer to work on something else?
|
|
59
|
+
|
|
60
|
+
## Critical Rules
|
|
61
|
+
|
|
62
|
+
1. **ONLY read the context file** - Do NOT scan the entire project or codebase
|
|
63
|
+
2. **Trust the context file** - It contains everything you need to understand the task
|
|
64
|
+
3. **Read files listed in "Files Changed"** - Only if you need to understand current state
|
|
65
|
+
4. **Don't guess or make up content** - Only use information from the context file
|
|
66
|
+
5. **If context file doesn't exist** - Inform the user and offer to create one
|
|
67
|
+
6. **Keep the context file updated** - As you continue working
|
|
68
|
+
|
|
69
|
+
## What NOT To Do
|
|
70
|
+
|
|
71
|
+
- ❌ Do NOT search the entire codebase to "understand the project"
|
|
72
|
+
- ❌ Do NOT read files that aren't mentioned in the context
|
|
73
|
+
- ❌ Do NOT run broad searches or scans
|
|
74
|
+
- ❌ Do NOT assume context beyond what's in the file
|
|
75
|
+
|
|
76
|
+
## What TO Do
|
|
77
|
+
|
|
78
|
+
- ✅ Read ONLY `.context/[name].md` first
|
|
79
|
+
- ✅ Use the "Files Changed" section to know which files are relevant
|
|
80
|
+
- ✅ Read specific files from "Files Changed" if needed for current state
|
|
81
|
+
- ✅ Follow "Next Steps" from the context file
|
|
82
|
+
- ✅ Ask the user if anything is unclear
|