@fernado03/zoo-flow 0.8.1 → 0.8.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/package.json +1 -1
- package/templates/full/.roo/skills/engineering/commit-and-document/SKILL.md +10 -0
- package/templates/full/.roo/skills/engineering/diagnose/SKILL.md +1 -1
- package/templates/full/.roo/skills/engineering/prototype/SKILL.md +10 -0
- package/templates/full/.roo/skills/engineering/tdd/SKILL.md +10 -0
- package/templates/full/.roo/skills/engineering/triage/SKILL.md +9 -0
- package/templates/full/.roo/skills/engineering/tweak/SKILL.md +9 -0
- package/templates/full/.roo/skills/engineering/update-docs/SKILL.md +10 -0
- package/templates/full/.roo/skills/productivity/grill-me/SKILL.md +10 -0
- package/templates/full/.roo/skills/productivity/handoff/SKILL.md +8 -0
- package/templates/full/.roo/skills/productivity/teach/SKILL.md +12 -0
- package/templates/full/.roo/skills/productivity/write-a-skill/SKILL.md +9 -0
package/package.json
CHANGED
|
@@ -134,6 +134,16 @@ On `yes` → suggest `/update-docs <area>`. On `skip` → continue.
|
|
|
134
134
|
|
|
135
135
|
Report: commit hash + message, journal entry path, whether `.gitignore` was updated, and any issue actions taken. Close with: "All of `docs/` is gitignored, so this entry stays local."
|
|
136
136
|
|
|
137
|
+
## Complete
|
|
138
|
+
|
|
139
|
+
Call `attempt_completion` with:
|
|
140
|
+
- commit hash (short)
|
|
141
|
+
- journal entry path
|
|
142
|
+
- status (complete / blocked with reason)
|
|
143
|
+
- recommended next command
|
|
144
|
+
|
|
145
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
146
|
+
|
|
137
147
|
## Context economy
|
|
138
148
|
|
|
139
149
|
Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
|
|
@@ -85,4 +85,4 @@ MUST finish:
|
|
|
85
85
|
|
|
86
86
|
## 7. Save
|
|
87
87
|
|
|
88
|
-
Write the full diagnosis (hypotheses, instrumentation, root cause, fix) to `.scratch/diagnoses/<date>/diagnose-<slug>.md`.
|
|
88
|
+
Write the full diagnosis (hypotheses, instrumentation, root cause, fix) to `.scratch/diagnoses/<date>/diagnose-<slug>.md`.
|
|
@@ -35,3 +35,13 @@ Do not re-read unchanged files; use prior findings unless the file changed.
|
|
|
35
35
|
7. No polish: no tests, minimal errors, no abstractions.
|
|
36
36
|
8. Surface full relevant state after each action/variant switch.
|
|
37
37
|
9. Done → capture answer in commit/ADR/issue/`NOTES.md`; delete or fold into real code.
|
|
38
|
+
|
|
39
|
+
## Complete
|
|
40
|
+
|
|
41
|
+
Call `attempt_completion` with:
|
|
42
|
+
- question answered
|
|
43
|
+
- prototype location (`.scratch/prototypes/<slug>/` or real module path)
|
|
44
|
+
- outcome (absorbed / discarded / needs decision)
|
|
45
|
+
- recommended next command
|
|
46
|
+
|
|
47
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
@@ -52,6 +52,16 @@ Checklist per cycle:
|
|
|
52
52
|
|
|
53
53
|
After green, suggest `/verify`, then `/review`, then `/commit-and-document` for non-trivial work. Do not auto-launch follow-up commands.
|
|
54
54
|
|
|
55
|
+
## Complete
|
|
56
|
+
|
|
57
|
+
Call `attempt_completion` with:
|
|
58
|
+
- what was implemented (behaviours, interfaces)
|
|
59
|
+
- tests written (count, pass/fail)
|
|
60
|
+
- status (complete / blocked with reason)
|
|
61
|
+
- recommended next command
|
|
62
|
+
|
|
63
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
64
|
+
|
|
55
65
|
## Context economy
|
|
56
66
|
|
|
57
67
|
Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
|
|
@@ -77,3 +77,12 @@ Show counts + one-line summaries. Let maintainer pick.
|
|
|
77
77
|
```
|
|
78
78
|
|
|
79
79
|
Rules: capture resolved info; ask specific/actionable questions; on resume, do not re-ask answered questions.
|
|
80
|
+
|
|
81
|
+
## Complete
|
|
82
|
+
|
|
83
|
+
Call `attempt_completion` with:
|
|
84
|
+
- issues triaged (count, outcomes applied)
|
|
85
|
+
- status (complete / blocked with reason)
|
|
86
|
+
- recommended next command
|
|
87
|
+
|
|
88
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
@@ -17,6 +17,15 @@ Use for small known fixes.
|
|
|
17
17
|
8. For R3+ risk, suggest `/verify` or `/review` before commit. Otherwise offer `/commit-and-document` only after user satisfied.
|
|
18
18
|
9. Do not auto-launch follow-up commands.
|
|
19
19
|
|
|
20
|
+
## Complete
|
|
21
|
+
|
|
22
|
+
Call `attempt_completion` with:
|
|
23
|
+
- what was changed (file paths, line ranges)
|
|
24
|
+
- status (complete / blocked with reason)
|
|
25
|
+
- recommended next command
|
|
26
|
+
|
|
27
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
28
|
+
|
|
20
29
|
## Context economy
|
|
21
30
|
|
|
22
31
|
Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
|
|
@@ -64,3 +64,13 @@ Do not re-read unchanged files; use prior findings unless the file changed.
|
|
|
64
64
|
## 7. Recommend next step
|
|
65
65
|
|
|
66
66
|
Recommend one: `/explore` (still unclear), `/feature` (plan emerged), `/refactor` (tangled-but-working code), `/fix` (bug found), `/commit-and-document` (done). Do not auto-run.
|
|
67
|
+
|
|
68
|
+
## Complete
|
|
69
|
+
|
|
70
|
+
Call `attempt_completion` with:
|
|
71
|
+
- docs updated (file paths)
|
|
72
|
+
- what changed (summary)
|
|
73
|
+
- status (complete / blocked with reason)
|
|
74
|
+
- recommended next command
|
|
75
|
+
|
|
76
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
@@ -11,3 +11,13 @@ description: Interview the user relentlessly about a plan or design until reachi
|
|
|
11
11
|
4. Ask one question at a time.
|
|
12
12
|
5. Include recommended answer.
|
|
13
13
|
6. Inspect code instead of asking when code can answer.
|
|
14
|
+
|
|
15
|
+
## Complete
|
|
16
|
+
|
|
17
|
+
Call `attempt_completion` with:
|
|
18
|
+
- decision tree branches resolved (count)
|
|
19
|
+
- key decisions made (summary)
|
|
20
|
+
- status (complete / blocked with reason)
|
|
21
|
+
- recommended next command
|
|
22
|
+
|
|
23
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
@@ -12,3 +12,11 @@ argument-hint: "What will the next session be used for?"
|
|
|
12
12
|
4. Include suggested skills section.
|
|
13
13
|
5. Reference artifacts by path/URL; do not duplicate.
|
|
14
14
|
6. Redact secrets/API keys/passwords/PII.
|
|
15
|
+
|
|
16
|
+
## Complete
|
|
17
|
+
|
|
18
|
+
Call `attempt_completion` with:
|
|
19
|
+
- handoff file path (OS temp dir)
|
|
20
|
+
- status (complete / blocked with reason)
|
|
21
|
+
|
|
22
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
@@ -105,3 +105,15 @@ Default: attempt an answer, then route to a high-reputation community from `RESO
|
|
|
105
105
|
## `NOTES.md`
|
|
106
106
|
|
|
107
107
|
The user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.
|
|
108
|
+
|
|
109
|
+
## Complete
|
|
110
|
+
|
|
111
|
+
When the user ends the teaching session or says "done" / "stop teaching":
|
|
112
|
+
|
|
113
|
+
Call `attempt_completion` with:
|
|
114
|
+
- lessons created (count, paths)
|
|
115
|
+
- mission status (created / updated)
|
|
116
|
+
- learning records updated (count)
|
|
117
|
+
- status (session complete / paused)
|
|
118
|
+
|
|
119
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|
|
@@ -50,3 +50,12 @@ Add when: deterministic op; repeated code; explicit error handling needed.
|
|
|
50
50
|
- [ ] Terminology consistent.
|
|
51
51
|
- [ ] Examples concrete.
|
|
52
52
|
- [ ] References one level deep.
|
|
53
|
+
|
|
54
|
+
## Complete
|
|
55
|
+
|
|
56
|
+
Call `attempt_completion` with:
|
|
57
|
+
- skill created (name, path)
|
|
58
|
+
- files written (SKILL.md, references, scripts)
|
|
59
|
+
- status (complete / blocked with reason)
|
|
60
|
+
|
|
61
|
+
Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
|