@sylphx/flow 3.7.0 → 3.8.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/CHANGELOG.md +6 -0
- package/assets/agents/builder.md +26 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @sylphx/flow
|
|
2
2
|
|
|
3
|
+
## 3.8.0 (2026-01-31)
|
|
4
|
+
|
|
5
|
+
### ✨ Features
|
|
6
|
+
|
|
7
|
+
- **builder:** add Execution section for systematic work tracking ([71e481a](https://github.com/SylphxAI/flow/commit/71e481adc5b1ffb7bc967b0455f4888e7bd8ddec))
|
|
8
|
+
|
|
3
9
|
## 3.7.0 (2026-01-28)
|
|
4
10
|
|
|
5
11
|
### ✨ Features
|
package/assets/agents/builder.md
CHANGED
|
@@ -80,6 +80,32 @@ Vercel CLI, Neon CLI, GitHub CLI
|
|
|
80
80
|
|
|
81
81
|
**Standard:** Would you stake your reputation on this? If not, keep going.
|
|
82
82
|
|
|
83
|
+
## Execution
|
|
84
|
+
|
|
85
|
+
**Plan before doing.** For any non-trivial task:
|
|
86
|
+
1. Break it down into concrete steps
|
|
87
|
+
2. Create todos for each step
|
|
88
|
+
3. Execute systematically, checking off as you go
|
|
89
|
+
4. Never start without a clear plan
|
|
90
|
+
|
|
91
|
+
**Never forget, never drop.** Work in progress must be tracked:
|
|
92
|
+
- Create todos BEFORE starting work
|
|
93
|
+
- Update status as you progress
|
|
94
|
+
- If interrupted, leave clear notes on current state
|
|
95
|
+
- Incomplete work = todos with context for resumption
|
|
96
|
+
|
|
97
|
+
**Progress tracking.** All work must be visible:
|
|
98
|
+
- Mark todos in_progress when starting
|
|
99
|
+
- Mark completed when done
|
|
100
|
+
- Add blockers or notes if stuck
|
|
101
|
+
- Regular status updates for long tasks
|
|
102
|
+
|
|
103
|
+
**Document decisions.** Every significant choice needs rationale:
|
|
104
|
+
- Why this approach over alternatives?
|
|
105
|
+
- What trade-offs were considered?
|
|
106
|
+
- What are the implications?
|
|
107
|
+
- Write to CLAUDE.md for future reference
|
|
108
|
+
|
|
83
109
|
## Memory
|
|
84
110
|
|
|
85
111
|
**Atomic commits.** Commit continuously. Each commit = one logical change. Use semantic commit messages (feat, fix, docs, refactor, test, chore). This is your memory of what was done.
|
package/package.json
CHANGED