You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/knowledge-keeper.ts
+15-15Lines changed: 15 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -45,21 +45,21 @@ const config: AgentConfig = {
45
45
46
46
subagents: ['file_picker','researcher'],
47
47
48
-
parentInstructions: {
49
-
researcher:
50
-
"Spawn knowledge-keeper when you find external documentation, API references, or community best practices that contradict or supplement what's currently documented in the project's knowledge files.",
51
-
file_picker:
52
-
'Spawn knowledge-keeper when you discover configuration files, architectural patterns, or code structures that lack corresponding documentation or when existing knowledge.md files are missing from important directories.',
53
-
reviewer:
54
-
'Spawn knowledge-keeper when code reviews reveal undocumented design decisions, new patterns being introduced, or when you notice that existing documentation has become outdated due to code changes.',
55
-
thinker:
56
-
'Spawn knowledge-keeper when your deep analysis uncovers complex architectural trade-offs, system dependencies, or technical debt that should be documented to prevent future confusion.',
57
-
brainstormer:
58
-
'Spawn knowledge-keeper when you generate innovative solutions for knowledge sharing, discover new ways to organize tribal knowledge, or identify creative approaches to making project information more accessible.',
59
-
base: 'Spawn knowledge-keeper when users explicitly ask about project documentation, request explanations of how things work, or when you encounter knowledge gaps while helping with their requests.',
60
-
planner:
61
-
'Spawn knowledge-keeper when creating long-term documentation strategies, planning knowledge migration between systems, or when developing systematic approaches to capturing institutional memory.',
62
-
},
48
+
// parentInstructions: {
49
+
// researcher:
50
+
// "Spawn knowledge-keeper when you find external documentation, API references, or community best practices that contradict or supplement what's currently documented in the project's knowledge files.",
51
+
// file_picker:
52
+
// 'Spawn knowledge-keeper when you discover configuration files, architectural patterns, or code structures that lack corresponding documentation or when existing knowledge.md files are missing from important directories.',
53
+
// reviewer:
54
+
// 'Spawn knowledge-keeper when code reviews reveal undocumented design decisions, new patterns being introduced, or when you notice that existing documentation has become outdated due to code changes.',
55
+
// thinker:
56
+
// 'Spawn knowledge-keeper when your deep analysis uncovers complex architectural trade-offs, system dependencies, or technical debt that should be documented to prevent future confusion.',
57
+
// brainstormer:
58
+
// 'Spawn knowledge-keeper when you generate innovative solutions for knowledge sharing, discover new ways to organize tribal knowledge, or identify creative approaches to making project information more accessible.',
59
+
// base: 'Spawn knowledge-keeper when users explicitly ask about project documentation, request explanations of how things work, or when you encounter knowledge gaps while helping with their requests.',
60
+
// planner:
61
+
// 'Spawn knowledge-keeper when creating long-term documentation strategies, planning knowledge migration between systems, or when developing systematic approaches to capturing institutional memory.',
0 commit comments