cfsa-antigravity 2.18.2 → 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 +1 -1
- package/package.json +1 -1
- package/template/.agent/instructions/workflow.md +12 -0
- package/template/.agent/kit-sync.md +3 -3
- package/template/.agent/rules/completion-checklist.md +5 -0
- package/template/.agent/skills/prd-templates/SKILL.md +2 -2
- package/template/.agent/skills/prd-templates/references/decomposition-templates.md +2 -2
- package/template/.agent/skills/prd-templates/references/placeholder-workflow-mapping.md +1 -1
- package/template/.agent/skills/prd-templates/references/shard-split-remediation.md +6 -6
- package/template/.agent/skills/prd-templates/references/skill-loading-protocol.md +1 -1
- package/template/.agent/workflows/decompose-architecture-structure.md +1 -1
- package/template/.agent/workflows/remediate-shard-split.md +1 -1
- package/template/.agent/workflows/write-fe-spec-classify.md +1 -1
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
|
|
|
@@ -100,8 +100,8 @@ docs/plans/ia/
|
|
|
100
100
|
├── 01-operations.md ← ## Features seeded from ideation/surfaces/desktop/01-operations/ (index + feature files)
|
|
101
101
|
├── 02-device-history.md ← ## Features seeded from ideation/domains/02-device-history/ (index + feature files)
|
|
102
102
|
|
|
103
|
-
docs/plans/desktop/
|
|
104
|
-
docs/plans/desktop/
|
|
103
|
+
docs/plans/be/desktop/ ← per-surface BE specs (inside be/)
|
|
104
|
+
docs/plans/fe/desktop/ ← per-surface FE specs (inside fe/)
|
|
105
105
|
docs/plans/be/ ← shared BE specs (pre-scaffolded, serves as shared surface)
|
|
106
106
|
docs/plans/fe/ ← shared FE specs (pre-scaffolded, serves as shared surface)
|
|
107
107
|
```
|
|
@@ -212,8 +212,8 @@ Create or update `docs/plans/index.md`:
|
|
|
212
212
|
| Surface | BE Index | FE Index | Description |
|
|
213
213
|
|---------|----------|----------|-------------|
|
|
214
214
|
| **Shared** | [be/index.md](be/index.md) | [fe/index.md](fe/index.md) | Cross-surface contracts (pre-scaffolded dirs) |
|
|
215
|
-
| **[Surface 1]** | [surface-1/
|
|
216
|
-
| **[Surface 2]** | [surface-2/
|
|
215
|
+
| **[Surface 1]** | [be/surface-1/index.md](be/surface-1/index.md) | [fe/surface-1/index.md](fe/surface-1/index.md) | [description] |
|
|
216
|
+
| **[Surface 2]** | [be/surface-2/index.md](be/surface-2/index.md) | [fe/surface-2/index.md](fe/surface-2/index.md) | [description] |
|
|
217
217
|
|
|
218
218
|
## Pipeline
|
|
219
219
|
|
|
@@ -42,7 +42,7 @@ How each workflow determines which surface's row to read:
|
|
|
42
42
|
|
|
43
43
|
| Workflow Type | Resolution Method |
|
|
44
44
|
|--------------|-------------------|
|
|
45
|
-
| Spec-writing (`write-be-spec`, `write-fe-spec`) | Shard directory path: `docs/plans/desktop
|
|
45
|
+
| Spec-writing (`write-be-spec`, `write-fe-spec`) | Shard directory path: `docs/plans/be/desktop/` → surface `desktop`; flat `docs/plans/be/` → surface `shared` |
|
|
46
46
|
| Implementation (`implement-slice`) | Slice's `surface:` tag from the phase plan |
|
|
47
47
|
| Planning (`plan-phase`) | Iterates ALL surfaces in the map |
|
|
48
48
|
| Validation (`validate-phase`) | Runs per-surface commands for all surfaces |
|
|
@@ -45,12 +45,12 @@ Grep the entire `docs/plans/` tree for the parent shard number using these patte
|
|
|
45
45
|
| `docs/plans/ia/` | Always |
|
|
46
46
|
| `docs/plans/be/` | If exists |
|
|
47
47
|
| `docs/plans/fe/` | If exists |
|
|
48
|
-
| `docs/plans/web
|
|
49
|
-
| `docs/plans/web
|
|
50
|
-
| `docs/plans/desktop
|
|
51
|
-
| `docs/plans/desktop
|
|
52
|
-
| `docs/plans/mobile
|
|
53
|
-
| `docs/plans/mobile
|
|
48
|
+
| `docs/plans/be/web/` | If exists |
|
|
49
|
+
| `docs/plans/fe/web/` | If exists |
|
|
50
|
+
| `docs/plans/be/desktop/` | If exists |
|
|
51
|
+
| `docs/plans/fe/desktop/` | If exists |
|
|
52
|
+
| `docs/plans/be/mobile/` | If exists |
|
|
53
|
+
| `docs/plans/fe/mobile/` | If exists |
|
|
54
54
|
|
|
55
55
|
### Exclusions
|
|
56
56
|
|
|
@@ -4,7 +4,7 @@ Standard procedure for loading skills from the surface stack map before beginnin
|
|
|
4
4
|
|
|
5
5
|
## How to Load Skills from the Surface Stack Map
|
|
6
6
|
|
|
7
|
-
1. **Determine the surface**: Identify which surface this work belongs to from the directory path or phase plan (e.g., `docs/plans/web
|
|
7
|
+
1. **Determine the surface**: Identify which surface this work belongs to from the directory path or phase plan (e.g., `docs/plans/be/web/` → surface `web`; flat `docs/plans/be/` → surface `shared`).
|
|
8
8
|
|
|
9
9
|
2. **Read the surface stack map**: Open `.agent/instructions/tech-stack.md` and locate this surface's row.
|
|
10
10
|
|
|
@@ -34,7 +34,7 @@ Create directory structure, shard skeleton files, and all layer indexes.
|
|
|
34
34
|
|
|
35
35
|
IA shards are **shared across all surfaces** — they live in the flat `docs/plans/ia/` directory regardless of project type. IA describes domains, not surfaces.
|
|
36
36
|
|
|
37
|
-
For each surface identified in the architecture design, create per-surface
|
|
37
|
+
For each surface identified in the architecture design, create per-surface subdirectories **inside** `docs/plans/be/` and `docs/plans/fe/` (e.g., `docs/plans/be/web/`, `docs/plans/fe/web/`, `docs/plans/be/mobile/`, `docs/plans/fe/mobile/`, etc.). Each new directory must include a `.gitkeep` file and a `README.md`. **Do NOT create top-level surface directories** (e.g., `docs/plans/web/be/`) — all specs are layer-first. The pre-scaffolded `docs/plans/be/` and `docs/plans/fe/` root directories serve as the shared surface for cross-surface contracts.
|
|
38
38
|
|
|
39
39
|
Per-surface BE/FE directories hold surface-specific backend and frontend specs. The pre-scaffolded `docs/plans/be/` and `docs/plans/fe/` hold shared cross-surface contracts (downstream workflows already resolve flat `docs/plans/be/` as surface `shared`).
|
|
40
40
|
|
|
@@ -77,7 +77,7 @@ Grep `docs/plans/` recursively for all references to the parent shard number. Th
|
|
|
77
77
|
| Parenthetical inline refs | `(see shard 00)` |
|
|
78
78
|
| Cross-shard links | `[00-infrastructure.md]` |
|
|
79
79
|
|
|
80
|
-
**Scope**: All directories under `docs/plans/` — `ia/`, `be/`, `fe/`, and any per-surface
|
|
80
|
+
**Scope**: All directories under `docs/plans/` — `ia/`, `be/`, `fe/`, and any per-surface subdirectories within `be/` and `fe/` (e.g., `be/web/`, `fe/desktop/`, `be/mobile/`).
|
|
81
81
|
|
|
82
82
|
**Exclusion**: Skip the parent stub file itself (it's already marked SPLIT).
|
|
83
83
|
|
|
@@ -72,7 +72,7 @@ Not every FE spec maps 1:1 to a BE feature spec. Before writing anything, classi
|
|
|
72
72
|
- For feature specs: the BE spec(s) and IA shard it maps to
|
|
73
73
|
- For cross-cutting specs: confirmation that BE spec/IA shard mapping is skipped
|
|
74
74
|
|
|
75
|
-
Determine this shard's surface from its directory path (e.g., `docs/plans/web
|
|
75
|
+
Determine this shard's surface from its directory path (e.g., `docs/plans/fe/web/` → surface `web`; flat `docs/plans/fe/` → surface `shared` or the project's single surface).
|
|
76
76
|
|
|
77
77
|
Read `.agent/skills/prd-templates/references/skill-loading-protocol.md` and follow the **Skill Loading Protocol** for the `write-fe-spec-classify` workflow. Load all categories listed in its table for this workflow, plus these bundled skills:
|
|
78
78
|
- `.agent/skills/error-handling-patterns/SKILL.md`
|