cfsa-antigravity 2.18.3 → 2.18.4
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/README.md
CHANGED
|
@@ -23,7 +23,7 @@ This installs the `.agent/` folder, `docs/` structure, and agent config files in
|
|
|
23
23
|
| `cfsa-antigravity init --path ./dir` | Install into specific directory |
|
|
24
24
|
|
|
25
25
|
### ⚠️ Important Note on `.gitignore`
|
|
26
|
-
If you are using AI-powered editors like **Cursor** or **Windsurf**, adding the `.agent/` folder to your `.gitignore` may prevent the IDE from indexing the workflows. This results in slash commands (like `/
|
|
26
|
+
If you are using AI-powered editors like **Cursor** or **Windsurf**, adding the `.agent/` folder to your `.gitignore` may prevent the IDE from indexing the workflows. This results in slash commands (like `/ideate`, `/create-prd`) not appearing in the chat suggestion dropdown.
|
|
27
27
|
|
|
28
28
|
**Recommended Solution:**
|
|
29
29
|
To keep the `.agent/` folder local (not tracked by Git) while maintaining AI functionality:
|
package/package.json
CHANGED
|
@@ -43,6 +43,18 @@ After completing a workflow or substantial task:
|
|
|
43
43
|
> These steps are **not optional**. They are what differentiate a pipeline that gets
|
|
44
44
|
> smarter over time from one that repeats the same mistakes.
|
|
45
45
|
|
|
46
|
+
## 6. Recommend Next Step (MANDATORY)
|
|
47
|
+
|
|
48
|
+
Before reporting completion via `notify_user`:
|
|
49
|
+
- Check the pipeline progress state (`.agent/progress/spec-pipeline.md` or equivalent)
|
|
50
|
+
- Propose the next valid pipeline command to the user
|
|
51
|
+
- If multiple valid next steps exist, list them with brief context
|
|
52
|
+
- Never end a conversation without telling the user what to do next
|
|
53
|
+
|
|
54
|
+
> This closes the gap where individual workflow files include "next step" sections,
|
|
55
|
+
> but agents don't read those files at session start. This step ensures the
|
|
56
|
+
> recommendation happens regardless.
|
|
57
|
+
|
|
46
58
|
## Principles
|
|
47
59
|
|
|
48
60
|
- **Ask before assuming** — Clarify ambiguous requirements
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Kit Sync State
|
|
2
2
|
|
|
3
3
|
upstream: https://github.com/RepairYourTech/cfsa-antigravity
|
|
4
|
-
last_synced_commit:
|
|
5
|
-
last_synced_at: 2026-03-
|
|
6
|
-
kit_version: 2.18.
|
|
4
|
+
last_synced_commit: cef05f046caf3eda65a8bb10c8ce1fd5c457e4c6
|
|
5
|
+
last_synced_at: 2026-03-26T15:01:38Z
|
|
6
|
+
kit_version: 2.18.4
|
|
@@ -44,6 +44,11 @@ A unit of work is only DONE when:
|
|
|
44
44
|
- See rule: `memory-capture` for triggers and format
|
|
45
45
|
6. **The Session Log**: A session close log exists in `.agent/progress/sessions/`.
|
|
46
46
|
- Follow `.agent/skills/session-continuity/protocols/05-session-close.md` — write what was accomplished, deferred, and where the next session should start
|
|
47
|
+
7. **The Next Step**: The user is told what comes next in the pipeline.
|
|
48
|
+
- Read the pipeline progress file (`.agent/progress/spec-pipeline.md` or equivalent)
|
|
49
|
+
- Propose the next valid pipeline command based on current state
|
|
50
|
+
- If multiple options exist, present them as a numbered list with brief context
|
|
51
|
+
- If the pipeline stage is complete, say so explicitly
|
|
47
52
|
|
|
48
53
|
## Enforcement
|
|
49
54
|
|