antigravity-ai-kit 3.5.3 → 3.7.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/.agent/CheatSheet.md +1 -1
- package/.agent/checklists/pre-commit.md +1 -1
- package/.agent/checklists/session-end.md +1 -1
- package/.agent/checklists/session-start.md +1 -1
- package/.agent/checklists/task-complete.md +12 -9
- package/.agent/commands/help.md +2 -2
- package/.agent/manifest.json +15 -3
- package/.agent/session-context.md +1 -1
- package/.agent/skills/README.md +3 -2
- package/.agent/skills/production-readiness/SKILL.md +272 -0
- package/.agent/workflows/README.md +6 -4
- package/.agent/workflows/deploy.md +3 -2
- package/.agent/workflows/pr.md +291 -0
- package/.agent/workflows/preflight.md +225 -0
- package/.agent/workflows/review.md +2 -2
- package/README.md +15 -12
- package/package.json +2 -2
package/.agent/CheatSheet.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Task-Complete Checkpoint
|
|
2
2
|
|
|
3
|
-
> **Framework**: Antigravity AI Kit v3.
|
|
3
|
+
> **Framework**: Antigravity AI Kit v3.7.0
|
|
4
4
|
> **Purpose**: Decision gate after task completion — present options before commit/push
|
|
5
5
|
> **Principle**: Human-in-the-loop governance
|
|
6
6
|
|
|
@@ -28,10 +28,11 @@ Present these options to the developer:
|
|
|
28
28
|
| 2 | 🛡️ Retrospective Audit | `/retrospective` | Sprint-end or milestone |
|
|
29
29
|
| 3 | 📋 Update Tracking | Manual | ✅ Always |
|
|
30
30
|
| 4 | 📦 Commit & Push | `git commit + push` | After review passes |
|
|
31
|
-
| 5 |
|
|
32
|
-
| 6 |
|
|
33
|
-
| 7 |
|
|
34
|
-
| 8 |
|
|
31
|
+
| 5 | 🔀 Pull Request | `/pr` | Feature branch with commits |
|
|
32
|
+
| 6 | 🔚 Session-End | Protocol | End of work session |
|
|
33
|
+
| 7 | 🚀 Deploy | `/deploy` | Production-impacting changes |
|
|
34
|
+
| 8 | 📝 Continue Working | Skip commit | Batching multiple changes |
|
|
35
|
+
| 9 | ⏭️ Skip Checkpoint | Session flag | Rapid iteration mode |
|
|
35
36
|
|
|
36
37
|
**Prompt format:**
|
|
37
38
|
|
|
@@ -42,10 +43,11 @@ How should we proceed?
|
|
|
42
43
|
2. 🛡️ /retrospective — Tier-1 audit (architecture, market benchmark, ethics)
|
|
43
44
|
3. 📋 Update tracking — Sync ROADMAP.md, session-context.md, session-state.json
|
|
44
45
|
4. 📦 Commit & push — Stage, commit (conventional), push to remote
|
|
45
|
-
5.
|
|
46
|
-
6.
|
|
47
|
-
7.
|
|
48
|
-
8.
|
|
46
|
+
5. 🔀 /pr — Create pull request with pre-flight checks and CI verification
|
|
47
|
+
6. 🔚 Session-end protocol — Preserve context and prepare for handoff
|
|
48
|
+
7. 🚀 /deploy — Production deployment with pre-flight checks
|
|
49
|
+
8. 📝 Continue working — Proceed to next task without committing
|
|
50
|
+
9. ⏭️ Skip checkpoint — Disable checkpoint for remainder of session
|
|
49
51
|
|
|
50
52
|
> Choose options (e.g., "1, 3, 4" or "1 through 5"):
|
|
51
53
|
```
|
|
@@ -62,6 +64,7 @@ Dynamically adjust recommendations based on:
|
|
|
62
64
|
- [ ] **File count**: If >5 files changed → recommend atomic commit review
|
|
63
65
|
- [ ] **New code without tests**: Flag with ⚠️ if test coverage gap detected
|
|
64
66
|
- [ ] **Security-sensitive**: If auth/crypto/token files changed → recommend `/review security`
|
|
67
|
+
- [ ] **Feature branch**: If on feature branch with unpushed commits → recommend `/pr`
|
|
65
68
|
|
|
66
69
|
---
|
|
67
70
|
|
package/.agent/commands/help.md
CHANGED
|
@@ -11,7 +11,7 @@ Your complete guide to the Antigravity AI Kit. Type `/help` for a quick overview
|
|
|
11
11
|
```
|
|
12
12
|
/help # Quick overview of all capabilities
|
|
13
13
|
/help commands # All 31 slash commands with descriptions
|
|
14
|
-
/help workflows # All
|
|
14
|
+
/help workflows # All 15 workflows with descriptions
|
|
15
15
|
/help agents # All 19 AI agents with domains
|
|
16
16
|
/help skills # All 32 skill modules
|
|
17
17
|
/help rules # Governance rules
|
|
@@ -24,7 +24,7 @@ Your complete guide to the Antigravity AI Kit. Type `/help` for a quick overview
|
|
|
24
24
|
|
|
25
25
|
## Quick Overview
|
|
26
26
|
|
|
27
|
-
**Antigravity AI Kit v3.
|
|
27
|
+
**Antigravity AI Kit v3.7.0** — Trust-Grade AI Development Framework
|
|
28
28
|
|
|
29
29
|
| Category | Count | Description |
|
|
30
30
|
|:---------|:------|:------------|
|
package/.agent/manifest.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": "1.0.0",
|
|
3
|
-
"kitVersion": "3.
|
|
3
|
+
"kitVersion": "3.7.0",
|
|
4
4
|
"lastAuditedAt": null,
|
|
5
5
|
"description": "Antigravity AI Kit — Trust-Grade AI Development Framework",
|
|
6
6
|
"repository": "https://github.com/besync-labs/antigravity-ai-kit",
|
|
@@ -110,7 +110,7 @@
|
|
|
110
110
|
"directory": "commands/"
|
|
111
111
|
},
|
|
112
112
|
"skills": {
|
|
113
|
-
"count":
|
|
113
|
+
"count": 33,
|
|
114
114
|
"items": [
|
|
115
115
|
{
|
|
116
116
|
"name": "api-patterns",
|
|
@@ -208,6 +208,10 @@
|
|
|
208
208
|
"name": "plan-writing",
|
|
209
209
|
"directory": "skills/plan-writing/"
|
|
210
210
|
},
|
|
211
|
+
{
|
|
212
|
+
"name": "production-readiness",
|
|
213
|
+
"directory": "skills/production-readiness/"
|
|
214
|
+
},
|
|
211
215
|
{
|
|
212
216
|
"name": "security-practices",
|
|
213
217
|
"directory": "skills/security-practices/"
|
|
@@ -243,7 +247,7 @@
|
|
|
243
247
|
]
|
|
244
248
|
},
|
|
245
249
|
"workflows": {
|
|
246
|
-
"count":
|
|
250
|
+
"count": 16,
|
|
247
251
|
"items": [
|
|
248
252
|
{
|
|
249
253
|
"name": "brainstorm",
|
|
@@ -273,6 +277,14 @@
|
|
|
273
277
|
"name": "plan",
|
|
274
278
|
"file": "workflows/plan.md"
|
|
275
279
|
},
|
|
280
|
+
{
|
|
281
|
+
"name": "pr",
|
|
282
|
+
"file": "workflows/pr.md"
|
|
283
|
+
},
|
|
284
|
+
{
|
|
285
|
+
"name": "preflight",
|
|
286
|
+
"file": "workflows/preflight.md"
|
|
287
|
+
},
|
|
276
288
|
{
|
|
277
289
|
"name": "preview",
|
|
278
290
|
"file": "workflows/preview.md"
|
package/.agent/skills/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Antigravity AI Kit — Skills
|
|
2
2
|
|
|
3
3
|
> **Purpose**: Workflow definitions and domain knowledge extensions
|
|
4
|
-
> **Count**:
|
|
4
|
+
> **Count**: 32 Skills (6 Operational + 4 Orchestration + 13 Domain + 9 Development)
|
|
5
5
|
|
|
6
6
|
---
|
|
7
7
|
|
|
@@ -25,7 +25,7 @@ Skills are automatically loaded based on task context. Agents invoke relevant sk
|
|
|
25
25
|
|
|
26
26
|
---
|
|
27
27
|
|
|
28
|
-
## Operational Skills (
|
|
28
|
+
## Operational Skills (6)
|
|
29
29
|
|
|
30
30
|
| Skill | Purpose |
|
|
31
31
|
| :-------------------------------------------------- | :------------------------ |
|
|
@@ -34,6 +34,7 @@ Skills are automatically loaded based on task context. Agents invoke relevant sk
|
|
|
34
34
|
| [strategic-compact](strategic-compact/SKILL.md) | Context window management |
|
|
35
35
|
| [eval-harness](eval-harness/SKILL.md) | Performance evaluation |
|
|
36
36
|
| [context-budget](context-budget/SKILL.md) | LLM token budget mgmt |
|
|
37
|
+
| [production-readiness](production-readiness/SKILL.md) | Production readiness audits |
|
|
37
38
|
|
|
38
39
|
---
|
|
39
40
|
|
|
@@ -0,0 +1,272 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: production-readiness
|
|
3
|
+
description: Production readiness audit domains, weighted scoring criteria, and check specifications for the /preflight workflow.
|
|
4
|
+
version: 1.0.0
|
|
5
|
+
triggers: [pre-deploy, pre-launch, milestone, production-readiness]
|
|
6
|
+
allowed-tools: Read, Grep
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Production Readiness
|
|
10
|
+
|
|
11
|
+
> **Purpose**: Assess project readiness for production deployment across 10 audit domains
|
|
12
|
+
> **Invoked by**: `/preflight` workflow
|
|
13
|
+
> **Reusable by**: `/retrospective`, `/deploy`
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
This skill defines the audit domains, sub-check rubrics, and scoring model used by the `/preflight` workflow to generate a Production Readiness Scorecard. Each domain has weighted scoring with evidence-based pass criteria.
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## Principles
|
|
24
|
+
|
|
25
|
+
1. **Evidence over assertion** — every score must be backed by observable proof
|
|
26
|
+
2. **Non-destructive** — all checks are read-only analysis
|
|
27
|
+
3. **Fail-safe defaults** — unverifiable checks score 0 (not assumed pass)
|
|
28
|
+
4. **Domain independence** — each domain is scored independently
|
|
29
|
+
5. **Blocker precedence** — blocker rules override total score
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## Domain Definitions
|
|
34
|
+
|
|
35
|
+
### D1: Task Completeness (8 points)
|
|
36
|
+
|
|
37
|
+
> Verify all planned work is complete, scope is aligned, and no undocumented features exist.
|
|
38
|
+
|
|
39
|
+
**Primary Skill**: `plan-writing` · **Check Method**: Read ROADMAP.md, task files
|
|
40
|
+
|
|
41
|
+
| Sub-Check | Points | Pass Criteria |
|
|
42
|
+
| :--- | :--- | :--- |
|
|
43
|
+
| ROADMAP.md or task tracker exists and is current | 2 | File exists, contains structured task list |
|
|
44
|
+
| All MVP/milestone tasks marked complete | 3 | No `[ ]` items remain in milestone scope |
|
|
45
|
+
| No undocumented features | 2 | Every implemented feature has a task entry |
|
|
46
|
+
| Scope drift detection | 1 | No features implemented outside planned scope |
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
### D2: User Journey Validation (10 points)
|
|
51
|
+
|
|
52
|
+
> Verify critical user flows work end-to-end and fail-safe behavior is defined.
|
|
53
|
+
|
|
54
|
+
**Primary Skill**: `webapp-testing` · **Secondary Skill**: `testing-patterns` · **Check Method**: Walk critical flows, check error handling
|
|
55
|
+
|
|
56
|
+
| Sub-Check | Points | Pass Criteria |
|
|
57
|
+
| :--- | :--- | :--- |
|
|
58
|
+
| Critical user flows identified | 2 | At least 3 key flows documented or testable |
|
|
59
|
+
| Happy path verified | 3 | Core flows produce expected outcomes |
|
|
60
|
+
| Error/edge case handling | 3 | Graceful degradation on failure paths |
|
|
61
|
+
| Accessibility baseline | 2 | Basic keyboard navigation, ARIA labels on critical elements |
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
### D3: Implementation Correctness (10 points)
|
|
66
|
+
|
|
67
|
+
> Verify features function as specified, no dead code, and test suite passes.
|
|
68
|
+
|
|
69
|
+
**Primary Skill**: `verification-loop` · **Secondary Skill**: `testing-patterns` · **Check Method**: Run test suite, static analysis
|
|
70
|
+
|
|
71
|
+
| Sub-Check | Points | Pass Criteria |
|
|
72
|
+
| :--- | :--- | :--- |
|
|
73
|
+
| Test suite passes | 4 | Zero test failures |
|
|
74
|
+
| Test coverage adequate | 2 | Coverage ≥ project target (or ≥60% default) |
|
|
75
|
+
| No dead code or unused exports | 2 | Static analysis clean |
|
|
76
|
+
| Feature correctness audit | 2 | Implemented features match specifications |
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
### D4: Code Quality (15 points)
|
|
81
|
+
|
|
82
|
+
> Verify code meets quality gates. Delegates to the `/review` workflow.
|
|
83
|
+
|
|
84
|
+
**Primary Skill**: `verification-loop` · **Secondary Skill**: `clean-code` · **Check Method**: Delegate to `/review`
|
|
85
|
+
|
|
86
|
+
| Sub-Check | Points | Pass Criteria |
|
|
87
|
+
| :--- | :--- | :--- |
|
|
88
|
+
| Lint passes | 3 | Zero lint errors |
|
|
89
|
+
| Type check passes | 3 | Zero type errors in strict mode |
|
|
90
|
+
| Build succeeds | 3 | Production build completes without errors |
|
|
91
|
+
| Code style compliance | 3 | Follows project conventions (naming, structure) |
|
|
92
|
+
| Dependency health | 3 | No critical/high vulnerabilities in dependencies |
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
### D5: Security & Privacy (18 points)
|
|
97
|
+
|
|
98
|
+
> Non-negotiable security assessment. Highest weight domain.
|
|
99
|
+
|
|
100
|
+
**Primary Skill**: `security-practices` · **Check Method**: OWASP check, secrets scan, dependency audit
|
|
101
|
+
|
|
102
|
+
| Sub-Check | Points | Pass Criteria |
|
|
103
|
+
| :--- | :--- | :--- |
|
|
104
|
+
| No hardcoded secrets | 4 | Grep for API keys, passwords, tokens — zero matches |
|
|
105
|
+
| Dependencies vulnerability scan | 3 | No critical/high CVEs in production deps |
|
|
106
|
+
| Authentication/authorization audit | 3 | Auth flows follow security-practices skill standards |
|
|
107
|
+
| Input validation on all endpoints | 3 | No unvalidated user input reaches business logic |
|
|
108
|
+
| HTTPS/security headers configured | 3 | CSP, HSTS, X-Frame-Options present in production config |
|
|
109
|
+
| Privacy compliance check | 2 | PII handling documented, consent mechanisms present |
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
### D6: Configuration Readiness (8 points)
|
|
114
|
+
|
|
115
|
+
> Verify environment configuration is production-ready.
|
|
116
|
+
|
|
117
|
+
**Primary Skill**: `deployment-procedures` · **Secondary Skill**: `shell-conventions` · **Check Method**: Env var audit, config validation
|
|
118
|
+
|
|
119
|
+
| Sub-Check | Points | Pass Criteria |
|
|
120
|
+
| :--- | :--- | :--- |
|
|
121
|
+
| All required env vars documented | 2 | `.env.example` or equivalent exists with all vars |
|
|
122
|
+
| No dev-only values in production config | 2 | No `localhost`, `debug=true`, dev API keys |
|
|
123
|
+
| Secrets management strategy defined | 2 | Secrets via env vars or vault, not committed |
|
|
124
|
+
| Environment-specific configs separated | 2 | Dev/staging/prod configs isolated |
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
### D7: Performance Baseline (8 points)
|
|
129
|
+
|
|
130
|
+
> Verify performance meets baseline thresholds.
|
|
131
|
+
|
|
132
|
+
**Primary Skill**: `performance-profiling` · **Check Method**: Bundle analysis, response time check
|
|
133
|
+
|
|
134
|
+
| Sub-Check | Points | Pass Criteria |
|
|
135
|
+
| :--- | :--- | :--- |
|
|
136
|
+
| Bundle size within budget | 2 | Initial JS < 200KB gzipped (web) or reasonable for platform |
|
|
137
|
+
| No obvious performance anti-patterns | 2 | No N+1 queries, unbounded loops, memory leaks |
|
|
138
|
+
| Core Web Vitals baseline (web) | 2 | LCP < 2.5s, CLS < 0.1 (if applicable) |
|
|
139
|
+
| API response times acceptable | 2 | p95 < 500ms for critical endpoints |
|
|
140
|
+
|
|
141
|
+
---
|
|
142
|
+
|
|
143
|
+
### D8: Documentation (5 points)
|
|
144
|
+
|
|
145
|
+
> Verify operational documentation is adequate.
|
|
146
|
+
|
|
147
|
+
**Primary Skill**: `plan-writing` · **Check Method**: File existence and content check
|
|
148
|
+
|
|
149
|
+
| Sub-Check | Points | Pass Criteria |
|
|
150
|
+
| :--- | :--- | :--- |
|
|
151
|
+
| README with setup instructions | 2 | README exists, includes install + run commands |
|
|
152
|
+
| API documentation (if applicable) | 1 | Endpoints documented or N/A justified |
|
|
153
|
+
| Runbook or incident procedures | 1 | Basic operational guide exists or N/A justified |
|
|
154
|
+
| CHANGELOG current | 1 | Recent changes documented |
|
|
155
|
+
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
### D9: Infrastructure & CI/CD (10 points)
|
|
159
|
+
|
|
160
|
+
> Verify deployment pipeline and infrastructure readiness.
|
|
161
|
+
|
|
162
|
+
**Primary Skill**: `deployment-procedures` · **Secondary Skill**: `docker-patterns` · **Check Method**: CI config analysis, deployment strategy
|
|
163
|
+
|
|
164
|
+
| Sub-Check | Points | Pass Criteria |
|
|
165
|
+
| :--- | :--- | :--- |
|
|
166
|
+
| CI pipeline passes | 3 | All CI checks green on target branch |
|
|
167
|
+
| Deployment strategy defined | 2 | Deploy method documented (manual, CD, container) |
|
|
168
|
+
| Rollback capability exists | 3 | Rollback procedure tested or documented |
|
|
169
|
+
| Health check endpoint (if applicable) | 2 | `/health` or equivalent returns service status |
|
|
170
|
+
|
|
171
|
+
---
|
|
172
|
+
|
|
173
|
+
### D10: Observability & Monitoring (8 points)
|
|
174
|
+
|
|
175
|
+
> Verify incident visibility and error tracking readiness.
|
|
176
|
+
|
|
177
|
+
**Primary Skill**: `deployment-procedures` · **Check Method**: Config analysis, logging audit
|
|
178
|
+
|
|
179
|
+
| Sub-Check | Points | Pass Criteria |
|
|
180
|
+
| :--- | :--- | :--- |
|
|
181
|
+
| Error tracking configured | 3 | Error monitoring service connected (Sentry, etc.) or plan documented |
|
|
182
|
+
| Structured logging in place | 2 | Application logs are structured (JSON) with severity levels |
|
|
183
|
+
| Alerting configured for critical paths | 2 | At least downtime/error-rate alerts defined |
|
|
184
|
+
| No PII in logs | 1 | Grep logs config for email/password/token patterns |
|
|
185
|
+
|
|
186
|
+
---
|
|
187
|
+
|
|
188
|
+
## Scoring Model
|
|
189
|
+
|
|
190
|
+
### Domain Weights
|
|
191
|
+
|
|
192
|
+
| Domain | Weight | Max Score |
|
|
193
|
+
| :--- | :--- | :--- |
|
|
194
|
+
| D1: Task Completeness | 8% | 8 |
|
|
195
|
+
| D2: User Journey Validation | 10% | 10 |
|
|
196
|
+
| D3: Implementation Correctness | 10% | 10 |
|
|
197
|
+
| D4: Code Quality | 15% | 15 |
|
|
198
|
+
| D5: Security & Privacy | 18% | 18 |
|
|
199
|
+
| D6: Configuration Readiness | 8% | 8 |
|
|
200
|
+
| D7: Performance Baseline | 8% | 8 |
|
|
201
|
+
| D8: Documentation | 5% | 5 |
|
|
202
|
+
| D9: Infrastructure & CI/CD | 10% | 10 |
|
|
203
|
+
| D10: Observability & Monitoring | 8% | 8 |
|
|
204
|
+
| **Total** | **100%** | **100** |
|
|
205
|
+
|
|
206
|
+
---
|
|
207
|
+
|
|
208
|
+
### Go/No-Go Thresholds
|
|
209
|
+
|
|
210
|
+
| Score | Status | Action |
|
|
211
|
+
| :--- | :--- | :--- |
|
|
212
|
+
| ≥ 85/100 | 🟢 **Production Ready** | Proceed to `/pr` → `/deploy` |
|
|
213
|
+
| 70-84 | 🟡 **Conditionally Ready** | Fix medium issues, re-run with `--rescan` |
|
|
214
|
+
| < 70 | 🔴 **Not Ready** | Fix critical/high issues, re-run with `--rescan` |
|
|
215
|
+
|
|
216
|
+
---
|
|
217
|
+
|
|
218
|
+
### Blocker Rule Precedence
|
|
219
|
+
|
|
220
|
+
Blocker rules **override** the total score. Even if the total score is above threshold, a blocker rule violation forces a lower verdict.
|
|
221
|
+
|
|
222
|
+
**Evaluation order**: Blockers are checked BEFORE the total score is evaluated.
|
|
223
|
+
|
|
224
|
+
| Rule | Condition | Override Verdict | Rationale |
|
|
225
|
+
| :--- | :--- | :--- | :--- |
|
|
226
|
+
| **Zero Domain** | Any domain scores 0/max | 🔴 Not Ready | A completely unchecked domain is a blind spot |
|
|
227
|
+
| **Security Floor** | D5 < 50% (< 9/18) | 🔴 Not Ready | Security is non-negotiable for production |
|
|
228
|
+
| **Quality Floor** | D4 < 50% (< 8/15) | 🟡 minimum | Code quality below threshold needs attention |
|
|
229
|
+
|
|
230
|
+
**Precedence**: Zero Domain > Security Floor > Quality Floor > Total Score
|
|
231
|
+
|
|
232
|
+
---
|
|
233
|
+
|
|
234
|
+
### Evidence Requirements
|
|
235
|
+
|
|
236
|
+
Every sub-check score must be supported by one of:
|
|
237
|
+
|
|
238
|
+
- **File evidence**: path to file or config that proves compliance
|
|
239
|
+
- **Command output**: result of a verification command (lint, test, scan)
|
|
240
|
+
- **Observation**: documented observation with specific detail
|
|
241
|
+
- **N/A justification**: one-line reason why the check doesn't apply
|
|
242
|
+
|
|
243
|
+
Unsupported scores default to 0.
|
|
244
|
+
|
|
245
|
+
---
|
|
246
|
+
|
|
247
|
+
## Delta Comparison (`--rescan`)
|
|
248
|
+
|
|
249
|
+
When invoked with `--rescan`, compare against the most recent previous scorecard:
|
|
250
|
+
|
|
251
|
+
1. Load previous scorecard from conversation artifacts
|
|
252
|
+
2. Run full D1-D10 scan with current state
|
|
253
|
+
3. Generate delta table:
|
|
254
|
+
|
|
255
|
+
```markdown
|
|
256
|
+
| Domain | Previous | Current | Delta |
|
|
257
|
+
| :--- | :--- | :--- | :--- |
|
|
258
|
+
| D1: Tasks | 5/8 | 8/8 | +3 ✅ |
|
|
259
|
+
| D5: Security | 6/18 | 14/18 | +8 ✅ |
|
|
260
|
+
```
|
|
261
|
+
|
|
262
|
+
4. Highlight regressions (negative delta) with `[!WARNING]`
|
|
263
|
+
5. Summary: total improvement, remaining gaps, updated verdict
|
|
264
|
+
|
|
265
|
+
---
|
|
266
|
+
|
|
267
|
+
## Integration
|
|
268
|
+
|
|
269
|
+
- **Primary consumer**: `/preflight` workflow (Verify phase)
|
|
270
|
+
- **Reusable by**: `/retrospective` (sprint audit can reference domain definitions)
|
|
271
|
+
- **Reusable by**: `/deploy` (deployment pre-flight can reference D5, D6, D9 checks)
|
|
272
|
+
- **References**: 8 existing skills via the delegation map in domain definitions
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Antigravity AI Kit — Workflows
|
|
2
2
|
|
|
3
3
|
> **Purpose**: Process templates for common development tasks
|
|
4
|
-
> **Count**:
|
|
4
|
+
> **Count**: 16 Workflows
|
|
5
5
|
> **Standard**: Enterprise Workflow Standard (EWS) v1.0
|
|
6
6
|
|
|
7
7
|
---
|
|
@@ -27,6 +27,8 @@ Invoke them using slash commands (e.g., `/brainstorm authentication system`).
|
|
|
27
27
|
| **ui-ux-pro-max** | `/ui-ux-pro-max` | Build | Premium UI/UX design and implementation |
|
|
28
28
|
| **test** | `/test` | Verify | Systematic test writing and execution |
|
|
29
29
|
| **review** | `/review` | Verify | Sequential quality gate pipeline |
|
|
30
|
+
| **preflight** | `/preflight` | Verify | Production readiness assessment with 10-domain scoring |
|
|
31
|
+
| **pr** | `/pr` | Ship | Production-grade PR creation with pre-flight checks |
|
|
30
32
|
| **deploy** | `/deploy` | Ship | Production deployment with pre-flight checks |
|
|
31
33
|
| **debug** | `/debug` | Reactive | Systematic problem investigation |
|
|
32
34
|
| **orchestrate** | `/orchestrate` | Reactive | Multi-agent coordination for complex tasks |
|
|
@@ -41,9 +43,9 @@ Invoke them using slash commands (e.g., `/brainstorm authentication system`).
|
|
|
41
43
|
Discover ──► Plan ──► Build ──► Verify ──► Ship ──► Evaluate
|
|
42
44
|
│ │ │ │ │ │
|
|
43
45
|
▼ ▼ ▼ ▼ ▼ ▼
|
|
44
|
-
/brainstorm /plan /create /test /
|
|
45
|
-
/quality-gate /enhance /review
|
|
46
|
-
/preview
|
|
46
|
+
/brainstorm /plan /create /test /pr /retrospective
|
|
47
|
+
/quality-gate /enhance /review /deploy
|
|
48
|
+
/preview /preflight
|
|
47
49
|
/ui-ux-pro-max
|
|
48
50
|
|
|
49
51
|
Reactive (any phase) Cross-cutting (any phase)
|
|
@@ -9,7 +9,7 @@ commit-types: [chore, fix]
|
|
|
9
9
|
# /deploy — Production Deployment
|
|
10
10
|
|
|
11
11
|
> **Trigger**: `/deploy [sub-command]`
|
|
12
|
-
> **Lifecycle**: Ship — after `/
|
|
12
|
+
> **Lifecycle**: Ship — after `/pr` is merged
|
|
13
13
|
|
|
14
14
|
> [!CAUTION]
|
|
15
15
|
> Deployment impacts production users and consumes platform credits. Every push to `production` triggers builds on hosting platforms (Vercel, Railway, etc.). Never deploy untested code. Always have a rollback plan before deploying.
|
|
@@ -189,7 +189,8 @@ Run `/deploy rollback` to restore [previous version].
|
|
|
189
189
|
|
|
190
190
|
## Related Resources
|
|
191
191
|
|
|
192
|
-
- **Previous**: `/
|
|
192
|
+
- **Previous**: `/pr` (PR must be created and merged before deployment)
|
|
193
|
+
- **Pre-requisite**: `/preflight` (production readiness must be verified before deployment)
|
|
193
194
|
- **Next**: `/status` (post-deploy monitoring)
|
|
194
195
|
- **Skill**: `.agent/skills/deployment-procedures/SKILL.md`
|
|
195
196
|
- **Global Rule**: Production Merge Discipline (see global rules)
|
|
@@ -0,0 +1,291 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Production-grade PR creation with pre-flight checks, branch sync, and CI verification.
|
|
3
|
+
version: 2.1.0
|
|
4
|
+
sdlc-phase: ship
|
|
5
|
+
skills: [git-workflow, verification-loop]
|
|
6
|
+
commit-types: [feat, fix, refactor, perf, chore, docs, test]
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# /pr — Production-Grade Pull Request Workflow
|
|
10
|
+
|
|
11
|
+
> **Trigger**: `/pr [target]` (default: `main`) · `/pr --draft [target]`
|
|
12
|
+
> **Lifecycle**: Ship — after `/preflight` readiness passes, before `/deploy`
|
|
13
|
+
|
|
14
|
+
> [!CAUTION]
|
|
15
|
+
> PR creation pushes code to remote and triggers CI pipelines. Always run local pre-flight checks via `/review` before pushing. Never create PRs with unresolved conflicts or failing tests. Every CI run consumes pipeline credits.
|
|
16
|
+
|
|
17
|
+
> [!TIP]
|
|
18
|
+
> This workflow leverages the **git-workflow** skill. Read `.agent/skills/git-workflow/SKILL.md` for extended guidance on branching, conventional commits, and PR templates.
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Scope Filter
|
|
23
|
+
|
|
24
|
+
| Commit Type | PR Mode | Gates Skipped |
|
|
25
|
+
| :---------- | :------ | :------------ |
|
|
26
|
+
| `feat()` — new features | ✅ Full (8 steps) | None |
|
|
27
|
+
| `fix()` — bug fixes | ✅ Full (8 steps) | None |
|
|
28
|
+
| `refactor()` — structural | ✅ Full (8 steps) | None |
|
|
29
|
+
| `perf()` — performance | ✅ Full (8 steps) | None |
|
|
30
|
+
| `chore()` — maintenance | ⚠️ Lightweight | Step 3 (pre-flight) |
|
|
31
|
+
| `docs()` — documentation | ⚠️ Lightweight | Steps 3, 7 (pre-flight, CI) |
|
|
32
|
+
| `test()` — test additions | ⚠️ Lightweight | Step 3 runs test gate only |
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## Critical Rules
|
|
37
|
+
|
|
38
|
+
1. **ALWAYS** sync with target branch before creating PR — prevents merge conflicts
|
|
39
|
+
2. **ALWAYS** run pre-flight `/review` locally before pushing — catches issues pre-CI
|
|
40
|
+
3. **NEVER** create a PR from `main` or `production` branches
|
|
41
|
+
4. **NEVER** create a PR with known conflicts — resolve first
|
|
42
|
+
5. **NEVER** merge without all CI checks passing
|
|
43
|
+
6. **ATOMIC** PRs — one logical unit of work per PR, not multi-sprint kitchen sinks
|
|
44
|
+
7. **CONVENTIONAL** titles — `type(scope): description` format
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## Argument Parsing
|
|
49
|
+
|
|
50
|
+
| Command | Action |
|
|
51
|
+
| :---------------------- | :--------------------------------------------------- |
|
|
52
|
+
| `/pr` | Create PR targeting default branch (`main`) |
|
|
53
|
+
| `/pr [target]` | Create PR targeting specified branch (e.g., `/pr dev`) |
|
|
54
|
+
| `/pr --draft` | Create PR as draft (may not trigger CI) |
|
|
55
|
+
| `/pr --draft [target]` | Create draft PR targeting specified branch |
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Steps
|
|
60
|
+
|
|
61
|
+
Execute IN ORDER. Stop at first failure.
|
|
62
|
+
|
|
63
|
+
### Step 1: Verify Branch State
|
|
64
|
+
|
|
65
|
+
// turbo
|
|
66
|
+
|
|
67
|
+
```powershell
|
|
68
|
+
git branch --show-current
|
|
69
|
+
git status --porcelain
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
- If on `main` or `production` → **STOP**, instruct user to create feature branch
|
|
73
|
+
- If working tree dirty → prompt to commit or stash
|
|
74
|
+
|
|
75
|
+
### Step 2: Sync with Target Branch
|
|
76
|
+
|
|
77
|
+
// turbo
|
|
78
|
+
|
|
79
|
+
```powershell
|
|
80
|
+
git fetch origin <target>
|
|
81
|
+
git merge origin/<target> --no-edit
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
- If conflicts detected → invoke **Conflict Resolution Protocol** (see below)
|
|
85
|
+
- If clean merge → proceed to Step 3
|
|
86
|
+
|
|
87
|
+
> [!WARNING]
|
|
88
|
+
> If the branch has diverged significantly from the target, expect conflicts in shared files like `.gitignore`, `package.json`, or lock files. Always check `git diff --name-only origin/<target>..HEAD` before creating the PR.
|
|
89
|
+
|
|
90
|
+
### Step 3: Run Pre-Flight Checks
|
|
91
|
+
|
|
92
|
+
Delegate to `/review` pipeline (Gates 1-5: lint, type-check, test, security, build).
|
|
93
|
+
|
|
94
|
+
- Scope filter applies:
|
|
95
|
+
- `docs()` → skip all gates
|
|
96
|
+
- `chore()` → skip test + build gates
|
|
97
|
+
- `test()` → run test gate only
|
|
98
|
+
- All others → full pipeline
|
|
99
|
+
- If any gate fails → stop, fix, re-run
|
|
100
|
+
|
|
101
|
+
> [!CAUTION]
|
|
102
|
+
> If ANY pre-flight check fails, fix it BEFORE proceeding. Do NOT rely on CI to catch issues — that wastes pipeline credits and delays the team.
|
|
103
|
+
|
|
104
|
+
### Step 4: Push to Remote
|
|
105
|
+
|
|
106
|
+
```powershell
|
|
107
|
+
git push origin HEAD
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
- If rejected (upstream diverged) → re-run Step 2, then retry push
|
|
111
|
+
- If authentication error → guide user to configure credentials
|
|
112
|
+
|
|
113
|
+
### Step 5: Generate PR Title & Body
|
|
114
|
+
|
|
115
|
+
// turbo
|
|
116
|
+
|
|
117
|
+
**Title generation:**
|
|
118
|
+
- Parse branch name: `feature/ABC-123-add-user-auth` → `feat(auth): add user auth`
|
|
119
|
+
- Fallback: use first commit message subject line
|
|
120
|
+
- Format: `type(scope): description` (conventional commits)
|
|
121
|
+
|
|
122
|
+
**Body generation:**
|
|
123
|
+
- Populate from `git log origin/<target>..HEAD --oneline` and `git diff --stat origin/<target>..HEAD`
|
|
124
|
+
- Use **PR Body Template** (see below)
|
|
125
|
+
|
|
126
|
+
### Step 6: Create PR
|
|
127
|
+
|
|
128
|
+
**Pre-check:** Query existing PRs for current branch. If open PR exists → offer to update title/body instead of creating new.
|
|
129
|
+
|
|
130
|
+
**MCP-first 3-tier fallback:**
|
|
131
|
+
1. Attempt `mcp_github-mcp-server_create_pull_request` with title, body, `is_draft`, base, head
|
|
132
|
+
2. If MCP fails → attempt `gh pr create --title "<title>" --body "<body>" --base <target> [--draft]`
|
|
133
|
+
3. If `gh` fails → provide pre-formatted title + body for manual browser copy-paste
|
|
134
|
+
|
|
135
|
+
### Step 7: Verify CI Pipeline
|
|
136
|
+
|
|
137
|
+
- Poll via `mcp_github-mcp-server_pull_request_read` (method: `get_status`)
|
|
138
|
+
- Report each check as it resolves
|
|
139
|
+
- If draft PR → note: "Draft PRs may not trigger CI on some repositories. Convert to ready-for-review via MCP `update_pull_request` if CI doesn't appear."
|
|
140
|
+
|
|
141
|
+
> [!NOTE]
|
|
142
|
+
> If CI checks do NOT appear, check:
|
|
143
|
+
> 1. **Merge conflicts** — `mergeable_state: dirty` blocks CI entirely
|
|
144
|
+
> 2. **Workflow file** — `.github/workflows/` must contain CI config on the target branch
|
|
145
|
+
> 3. **Branch targeting** — CI may only trigger on PRs targeting specific branches
|
|
146
|
+
|
|
147
|
+
### Step 8: Handle Results
|
|
148
|
+
|
|
149
|
+
- ✅ All green → offer to assign reviewers via `update_pull_request`, link issues with `Closes #N`
|
|
150
|
+
- ❌ Any fail → read failure logs, suggest fix, re-run from Step 3
|
|
151
|
+
- ⏳ Timeout → provide manual check instructions
|
|
152
|
+
|
|
153
|
+
---
|
|
154
|
+
|
|
155
|
+
## PR Body Template
|
|
156
|
+
|
|
157
|
+
```markdown
|
|
158
|
+
## Summary
|
|
159
|
+
[One-line description derived from branch name and commits]
|
|
160
|
+
|
|
161
|
+
## Changes
|
|
162
|
+
|
|
163
|
+
### [Category — derived from commit types]
|
|
164
|
+
- [Change description from commit messages]
|
|
165
|
+
|
|
166
|
+
## Test Plan
|
|
167
|
+
- [x] Pre-flight `/review` passed locally (lint, type-check, test, security, build)
|
|
168
|
+
- [x] Branch synced with `{target}` — no conflicts
|
|
169
|
+
- [x] No secrets or PII in diff
|
|
170
|
+
|
|
171
|
+
## Breaking Changes
|
|
172
|
+
[None / List any breaking changes — derived from `BREAKING CHANGE:` commit footers]
|
|
173
|
+
|
|
174
|
+
## Related Issues
|
|
175
|
+
[Closes #N — derived from commit messages or branch name pattern]
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
---
|
|
179
|
+
|
|
180
|
+
## Conflict Resolution Protocol
|
|
181
|
+
|
|
182
|
+
When merge conflicts are detected in Step 2:
|
|
183
|
+
|
|
184
|
+
```powershell
|
|
185
|
+
# 1. Check conflicted files
|
|
186
|
+
git diff --name-only --diff-filter=U
|
|
187
|
+
|
|
188
|
+
# 2. Resolve each conflict manually
|
|
189
|
+
# - .gitignore: combine both versions, prefer more restrictive
|
|
190
|
+
# - Package manifests (package.json, pubspec.yaml): merge dependencies carefully
|
|
191
|
+
# - Source files: understand both changes, merge logically
|
|
192
|
+
|
|
193
|
+
# 3. Mark resolved and commit
|
|
194
|
+
git add <resolved-files>
|
|
195
|
+
git commit -m "merge: resolve conflicts with <target>"
|
|
196
|
+
|
|
197
|
+
# 4. Re-run pre-flight checks (Step 3)
|
|
198
|
+
# Invoke /review to verify merge didn't break anything
|
|
199
|
+
|
|
200
|
+
# 5. Resume from Step 4 (Push)
|
|
201
|
+
```
|
|
202
|
+
|
|
203
|
+
---
|
|
204
|
+
|
|
205
|
+
## Output Template
|
|
206
|
+
|
|
207
|
+
### ✅ PR Created Successfully
|
|
208
|
+
|
|
209
|
+
```markdown
|
|
210
|
+
## ✅ PR Created Successfully
|
|
211
|
+
|
|
212
|
+
| Field | Value |
|
|
213
|
+
| :--- | :--- |
|
|
214
|
+
| PR | #[N] |
|
|
215
|
+
| Title | [type(scope): description] |
|
|
216
|
+
| Branch | [source] → [target] |
|
|
217
|
+
| Status | [draft / ready for review] |
|
|
218
|
+
| URL | [link] |
|
|
219
|
+
|
|
220
|
+
### CI Status
|
|
221
|
+
| Check | Status |
|
|
222
|
+
| :--- | :--- |
|
|
223
|
+
| [name] | ✅ Pass / ⏳ Pending / ❌ Fail |
|
|
224
|
+
|
|
225
|
+
**Next**: Wait for CI → `/deploy` when ready.
|
|
226
|
+
```
|
|
227
|
+
|
|
228
|
+
### ❌ PR Creation Failed
|
|
229
|
+
|
|
230
|
+
```markdown
|
|
231
|
+
## ❌ PR Creation Failed at Step [N]
|
|
232
|
+
|
|
233
|
+
### Error
|
|
234
|
+
[Error description]
|
|
235
|
+
|
|
236
|
+
### Resolution
|
|
237
|
+
1. [Fix steps]
|
|
238
|
+
2. Re-run: `/pr [target]`
|
|
239
|
+
|
|
240
|
+
### Fallback
|
|
241
|
+
[Manual instructions if MCP + CLI both failed]
|
|
242
|
+
```
|
|
243
|
+
|
|
244
|
+
---
|
|
245
|
+
|
|
246
|
+
## Governance
|
|
247
|
+
|
|
248
|
+
**PROHIBITED:**
|
|
249
|
+
- Creating PRs from `main` or `production` branches
|
|
250
|
+
- Creating PRs with unresolved merge conflicts
|
|
251
|
+
- Pushing without local pre-flight `/review` passing
|
|
252
|
+
- Merging PRs with failing CI checks
|
|
253
|
+
- Including generated files, PII, secrets, or `.env` in diff
|
|
254
|
+
- Multi-sprint mega-PRs — keep PRs focused and reviewable
|
|
255
|
+
- Using `// turbo` on state-mutating steps (push, create, merge)
|
|
256
|
+
- Skipping failed steps · proceeding without resolution
|
|
257
|
+
|
|
258
|
+
**REQUIRED:**
|
|
259
|
+
- Branch sync with target before every PR
|
|
260
|
+
- Local pre-flight via `/review` before push
|
|
261
|
+
- Conventional commit PR title format
|
|
262
|
+
- Structured PR body using template
|
|
263
|
+
- CI verification after PR creation
|
|
264
|
+
- Human approval before push and PR creation (non-turbo)
|
|
265
|
+
- MCP-first with graceful fallback strategy
|
|
266
|
+
- Conflict resolution before push
|
|
267
|
+
|
|
268
|
+
---
|
|
269
|
+
|
|
270
|
+
## Completion Criteria
|
|
271
|
+
|
|
272
|
+
- [ ] On feature branch (not `main`/`production`)
|
|
273
|
+
- [ ] Working tree clean (committed or stashed)
|
|
274
|
+
- [ ] Target branch synced (no conflicts)
|
|
275
|
+
- [ ] Pre-flight `/review` passes (scope-filtered)
|
|
276
|
+
- [ ] Pushed to remote
|
|
277
|
+
- [ ] PR created with conventional title and structured body
|
|
278
|
+
- [ ] CI checks monitored and passed (or draft acknowledged)
|
|
279
|
+
- [ ] Review requested (if applicable)
|
|
280
|
+
- [ ] After CI passes: proceed to `/deploy` when ready
|
|
281
|
+
|
|
282
|
+
---
|
|
283
|
+
|
|
284
|
+
## Related Resources
|
|
285
|
+
|
|
286
|
+
- **Previous**: `/preflight` (production readiness verified) · `/review` (code quality gates)
|
|
287
|
+
- **Next**: `/deploy` (deployment after PR is merged)
|
|
288
|
+
- **Skills**: `.agent/skills/git-workflow/SKILL.md` · `.agent/skills/verification-loop/SKILL.md`
|
|
289
|
+
- **Global Rule**: Production Merge Discipline (see global rules)
|
|
290
|
+
- **Related**: `/status` (check PR and CI status)
|
|
291
|
+
- **Note**: PR body template supersedes the basic template in `git-workflow` skill
|
|
@@ -0,0 +1,225 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Production readiness assessment with weighted scoring across 10 audit domains.
|
|
3
|
+
version: 1.0.0
|
|
4
|
+
sdlc-phase: verify
|
|
5
|
+
skills: [production-readiness, verification-loop, security-practices]
|
|
6
|
+
commit-types: [feat, fix, refactor, perf]
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# /preflight — Production Readiness Assessment
|
|
10
|
+
|
|
11
|
+
> **Trigger**: `/preflight [domain|flag]`
|
|
12
|
+
> **Lifecycle**: Verify — after `/review`, before `/pr`
|
|
13
|
+
|
|
14
|
+
> [!CAUTION]
|
|
15
|
+
> Production readiness gate. All critical domains must pass before proceeding
|
|
16
|
+
> to `/pr` → `/deploy`. A failing preflight blocks the shipping pipeline.
|
|
17
|
+
|
|
18
|
+
> [!TIP]
|
|
19
|
+
> This workflow leverages the **production-readiness**, **verification-loop**, and
|
|
20
|
+
> **security-practices** skills. Read `.agent/skills/production-readiness/SKILL.md`
|
|
21
|
+
> for domain specifications and scoring criteria.
|
|
22
|
+
|
|
23
|
+
---
|
|
24
|
+
|
|
25
|
+
## Critical Rules
|
|
26
|
+
|
|
27
|
+
1. **Evidence-backed scoring** — every domain score must cite observable proof (file, command output, observation)
|
|
28
|
+
2. **Never bypass blockers** — blocker rule violations override total score (see skill for precedence)
|
|
29
|
+
3. **Human approval required** — Go/No-Go recommendation requires explicit user decision
|
|
30
|
+
4. **Non-destructive** — all checks are read-only analysis; no files modified, no commands with side effects
|
|
31
|
+
5. **Skill-mediated delegation** — domain checks reference existing skills, never duplicate their logic
|
|
32
|
+
6. **Fail-safe defaults** — unverifiable checks score 0, not assumed pass
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## Argument Parsing
|
|
37
|
+
|
|
38
|
+
| Command | Action |
|
|
39
|
+
| :--- | :--- |
|
|
40
|
+
| `/preflight` | Full scan — all 10 domains (D1-D10), standard scorecard |
|
|
41
|
+
| `/preflight [domain]` | Single domain focus (e.g., `/preflight security`, `/preflight tasks`) |
|
|
42
|
+
| `/preflight --quick` | Quick scan — D4 (Code) + D5 (Security) + D6 (Config) + D9 (CI/CD) |
|
|
43
|
+
| `/preflight --full` | Deep scan — all D1-D10 + market benchmark comparison |
|
|
44
|
+
| `/preflight --rescan` | Re-scan — all D1-D10 with delta comparison against previous scorecard |
|
|
45
|
+
|
|
46
|
+
### Domain Name Aliases
|
|
47
|
+
|
|
48
|
+
| Domain | Aliases |
|
|
49
|
+
| :--- | :--- |
|
|
50
|
+
| D1: Task Completeness | `tasks`, `roadmap`, `scope` |
|
|
51
|
+
| D2: User Journey Validation | `journeys`, `ux`, `flows` |
|
|
52
|
+
| D3: Implementation Correctness | `implementation`, `correctness`, `tests` |
|
|
53
|
+
| D4: Code Quality | `code`, `quality`, `lint` |
|
|
54
|
+
| D5: Security & Privacy | `security`, `sec`, `privacy` |
|
|
55
|
+
| D6: Configuration Readiness | `config`, `configuration`, `env` |
|
|
56
|
+
| D7: Performance Baseline | `performance`, `perf`, `speed` |
|
|
57
|
+
| D8: Documentation | `docs`, `documentation` |
|
|
58
|
+
| D9: Infrastructure & CI/CD | `infra`, `ci`, `cicd`, `pipeline` |
|
|
59
|
+
| D10: Observability & Monitoring | `observability`, `monitoring`, `logs` |
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
## Steps
|
|
64
|
+
|
|
65
|
+
// turbo
|
|
66
|
+
1. **Project Detection & Inventory**
|
|
67
|
+
- Detect project type (web, mobile, API, library, monorepo)
|
|
68
|
+
- Identify tech stack (language, framework, build tool)
|
|
69
|
+
- Locate key files: ROADMAP.md, package.json/pubspec.yaml, CI config, .env files
|
|
70
|
+
- Identify the target deployment platform
|
|
71
|
+
- Determine which domains are applicable (not all domains apply to every project type)
|
|
72
|
+
- Load the `production-readiness` skill for domain definitions
|
|
73
|
+
|
|
74
|
+
// turbo
|
|
75
|
+
2. **Domain Scanning**
|
|
76
|
+
- For each applicable domain (D1-D10):
|
|
77
|
+
- Load the primary skill referenced in the domain definition
|
|
78
|
+
- Execute each sub-check per the rubric in the `production-readiness` skill
|
|
79
|
+
- Record evidence for each sub-check (file path, command output, observation)
|
|
80
|
+
- Calculate domain score based on sub-check results
|
|
81
|
+
- Classify findings by severity:
|
|
82
|
+
- 🔴 **Critical**: Blocks production, must fix
|
|
83
|
+
- 🟠 **High**: Significant risk, should fix before ship
|
|
84
|
+
- 🟡 **Medium**: Improvement recommended, can ship with plan
|
|
85
|
+
- 🟢 **Low**: Minor suggestion, no blocking impact
|
|
86
|
+
- For `--quick` mode: execute only D4, D5, D6, D9
|
|
87
|
+
- For single domain: execute only the specified domain
|
|
88
|
+
|
|
89
|
+
// turbo
|
|
90
|
+
3. **Scoring & Classification**
|
|
91
|
+
- Calculate per-domain scores from sub-check results
|
|
92
|
+
- Apply Blocker Rule Precedence (see `production-readiness` skill):
|
|
93
|
+
1. Check: Any domain = 0? → 🔴 Not Ready
|
|
94
|
+
2. Check: D5 < 50%? → 🔴 Not Ready
|
|
95
|
+
3. Check: D4 < 50%? → 🟡 minimum
|
|
96
|
+
- Calculate total score (sum of all domain scores)
|
|
97
|
+
- Determine Go/No-Go status from thresholds:
|
|
98
|
+
- ≥ 85: 🟢 Production Ready
|
|
99
|
+
- 70-84: 🟡 Conditionally Ready
|
|
100
|
+
- < 70: 🔴 Not Ready
|
|
101
|
+
- For `--rescan`: generate delta comparison table
|
|
102
|
+
- For `--full`: add market benchmark comparison section
|
|
103
|
+
|
|
104
|
+
4. **Go/No-Go Recommendation**
|
|
105
|
+
- Present the Production Readiness Scorecard to the user
|
|
106
|
+
- Highlight critical/high findings with remediation guidance
|
|
107
|
+
- Recommend next actions based on verdict
|
|
108
|
+
- **Wait for explicit user decision** — never auto-proceed
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
## Output Template
|
|
113
|
+
|
|
114
|
+
```markdown
|
|
115
|
+
# 🚀 Production Readiness Scorecard
|
|
116
|
+
|
|
117
|
+
> Project: [project name] · Date: [date] · Mode: [default|quick|full|rescan]
|
|
118
|
+
|
|
119
|
+
## Overall Verdict
|
|
120
|
+
|
|
121
|
+
| Score | Status | Decision |
|
|
122
|
+
| :--- | :--- | :--- |
|
|
123
|
+
| [XX/100] | [🟢/🟡/🔴] [Status] | [Recommendation] |
|
|
124
|
+
|
|
125
|
+
## Domain Scores
|
|
126
|
+
|
|
127
|
+
| Domain | Score | Status | Key Finding |
|
|
128
|
+
| :--- | :--- | :--- | :--- |
|
|
129
|
+
| D1: Task Completeness | X/8 | [emoji] | [summary] |
|
|
130
|
+
| D2: User Journeys | X/10 | [emoji] | [summary] |
|
|
131
|
+
| D3: Implementation | X/10 | [emoji] | [summary] |
|
|
132
|
+
| D4: Code Quality | X/15 | [emoji] | [summary] |
|
|
133
|
+
| D5: Security & Privacy | X/18 | [emoji] | [summary] |
|
|
134
|
+
| D6: Configuration | X/8 | [emoji] | [summary] |
|
|
135
|
+
| D7: Performance | X/8 | [emoji] | [summary] |
|
|
136
|
+
| D8: Documentation | X/5 | [emoji] | [summary] |
|
|
137
|
+
| D9: Infrastructure | X/10 | [emoji] | [summary] |
|
|
138
|
+
| D10: Observability | X/8 | [emoji] | [summary] |
|
|
139
|
+
|
|
140
|
+
## Blocker Check
|
|
141
|
+
|
|
142
|
+
| Rule | Condition | Result |
|
|
143
|
+
| :--- | :--- | :--- |
|
|
144
|
+
| Zero Domain | Any domain = 0 | [PASS/FAIL] |
|
|
145
|
+
| Security Floor | D5 ≥ 50% | [PASS/FAIL] |
|
|
146
|
+
| Quality Floor | D4 ≥ 50% | [PASS/FAIL] |
|
|
147
|
+
|
|
148
|
+
## Findings
|
|
149
|
+
|
|
150
|
+
### 🔴 Critical
|
|
151
|
+
- [finding with evidence and remediation]
|
|
152
|
+
|
|
153
|
+
### 🟠 High
|
|
154
|
+
- [finding with evidence and remediation]
|
|
155
|
+
|
|
156
|
+
### 🟡 Medium
|
|
157
|
+
- [finding with evidence and remediation]
|
|
158
|
+
|
|
159
|
+
## Recommended Next Actions
|
|
160
|
+
|
|
161
|
+
1. [action based on verdict]
|
|
162
|
+
2. [action based on top findings]
|
|
163
|
+
|
|
164
|
+
---
|
|
165
|
+
|
|
166
|
+
Verdict: [🟢/🟡/🔴] [score]/100 — [status text]
|
|
167
|
+
Run `/preflight --rescan` after fixes to verify improvement.
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
---
|
|
171
|
+
|
|
172
|
+
## Governance
|
|
173
|
+
|
|
174
|
+
**PROHIBITED:**
|
|
175
|
+
- Auto-deploying based on a passing score — human decision always required
|
|
176
|
+
- Skipping blocker rule evaluation
|
|
177
|
+
- Fabricating evidence for sub-check scores
|
|
178
|
+
- Modifying project files during analysis
|
|
179
|
+
- Proceeding to `/pr` without presenting the scorecard
|
|
180
|
+
|
|
181
|
+
**REQUIRED:**
|
|
182
|
+
- Evidence citation for every scored sub-check
|
|
183
|
+
- Blocker rule evaluation before total score
|
|
184
|
+
- Human approval for Go/No-Go decision
|
|
185
|
+
- Skill reference for each domain scan
|
|
186
|
+
- Finding classification by severity (🔴/🟠/🟡/🟢)
|
|
187
|
+
|
|
188
|
+
---
|
|
189
|
+
|
|
190
|
+
## Completion Criteria
|
|
191
|
+
|
|
192
|
+
- [ ] Project type and tech stack detected
|
|
193
|
+
- [ ] Applicable domains identified
|
|
194
|
+
- [ ] All applicable domain sub-checks executed with evidence
|
|
195
|
+
- [ ] Blocker rules evaluated
|
|
196
|
+
- [ ] Per-domain scores calculated
|
|
197
|
+
- [ ] Total score and Go/No-Go status determined
|
|
198
|
+
- [ ] Findings classified by severity
|
|
199
|
+
- [ ] Scorecard presented to user
|
|
200
|
+
- [ ] User has made explicit Go/No-Go decision
|
|
201
|
+
- [ ] After approval: proceed to `/pr` for PR creation
|
|
202
|
+
|
|
203
|
+
---
|
|
204
|
+
|
|
205
|
+
## Scope Filter
|
|
206
|
+
|
|
207
|
+
| Commit Type | Preflight Required? | Rationale |
|
|
208
|
+
| :--- | :--- | :--- |
|
|
209
|
+
| `feat()` | ✅ Required | New features need readiness validation |
|
|
210
|
+
| `fix()` | ⚠️ Optional | Critical fixes may need quick deploy path |
|
|
211
|
+
| `refactor()` | ✅ Required | Structural changes need validation |
|
|
212
|
+
| `perf()` | ✅ Required | Performance changes need baseline verification |
|
|
213
|
+
| `docs()` | ❌ Skip | No production impact |
|
|
214
|
+
| `chore()` | ❌ Skip | No production impact |
|
|
215
|
+
| `test()` | ❌ Skip | No production impact |
|
|
216
|
+
| Pre-launch | ✅ Required | Major releases always require preflight |
|
|
217
|
+
|
|
218
|
+
---
|
|
219
|
+
|
|
220
|
+
## Related Resources
|
|
221
|
+
|
|
222
|
+
- **Previous**: `/review` (code quality gates must pass before preflight)
|
|
223
|
+
- **Next**: `/pr` (create pull request after readiness verified)
|
|
224
|
+
- **Skills**: `.agent/skills/production-readiness/SKILL.md` · `.agent/skills/verification-loop/SKILL.md` · `.agent/skills/security-practices/SKILL.md`
|
|
225
|
+
- **Related**: `/deploy` (deployment after PR merged) · `/retrospective` (sprint-level audit)
|
|
@@ -9,7 +9,7 @@ commit-types: [fix, refactor]
|
|
|
9
9
|
# /review — Code Review Quality Gate
|
|
10
10
|
|
|
11
11
|
> **Trigger**: `/review` (full) · `/review lint` · `/review tests` · `/review security` · `/review build`
|
|
12
|
-
> **Lifecycle**: After implementation, before `/
|
|
12
|
+
> **Lifecycle**: After implementation, before `/pr`
|
|
13
13
|
|
|
14
14
|
> [!CAUTION]
|
|
15
15
|
> Sequential gate pipeline — each step must pass before proceeding. Failed gates block merge. No overrides.
|
|
@@ -183,6 +183,6 @@ Re-run: `/review` or `/review {gate}`
|
|
|
183
183
|
## Related Resources
|
|
184
184
|
|
|
185
185
|
- **Previous**: `/test` (tests must pass before review)
|
|
186
|
-
- **Next**: `/
|
|
186
|
+
- **Next**: `/preflight` (production readiness assessment) · `/pr` (create pull request)
|
|
187
187
|
- **Skill**: `.agent/skills/verification-loop/SKILL.md`
|
|
188
188
|
- **Related**: `/quality-gate` (pre-task research) · `/retrospective` (sprint-level audit)
|
package/README.md
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
# 🚀 Antigravity AI Kit
|
|
2
2
|
|
|
3
|
-

|
|
4
4
|

|
|
5
5
|

|
|
6
|
-

|
|
7
7
|

|
|
8
|
-

|
|
9
9
|

|
|
10
10
|

|
|
11
11
|

|
|
@@ -15,7 +15,7 @@
|
|
|
15
15
|
</p>
|
|
16
16
|
|
|
17
17
|
<p align="center">
|
|
18
|
-
Antigravity AI Kit is a <b>Trust-Grade AI development framework</b> with a <b>29-module runtime engine</b>, <b>19 specialized agents</b>, <b>31 commands</b>, <b>
|
|
18
|
+
Antigravity AI Kit is a <b>Trust-Grade AI development framework</b> with a <b>29-module runtime engine</b>, <b>19 specialized agents</b>, <b>31 commands</b>, <b>33 skills</b>, and <b>16 workflows</b> — all backed by <b>341 tests</b> and governance-first principles.
|
|
19
19
|
</p>
|
|
20
20
|
|
|
21
21
|
<p align="center">
|
|
@@ -40,7 +40,7 @@
|
|
|
40
40
|
- [Commands](#%EF%B8%8F-commands-31)
|
|
41
41
|
- [Skills](#%EF%B8%8F-skills-32)
|
|
42
42
|
- [Runtime Engine](#%EF%B8%8F-runtime-engine-29-modules)
|
|
43
|
-
- [Workflows](#-workflows-
|
|
43
|
+
- [Workflows](#-workflows-15)
|
|
44
44
|
- [Operating Constraints](#%EF%B8%8F-operating-constraints)
|
|
45
45
|
- [Session Management](#-session-management)
|
|
46
46
|
- [How to Extend](#-how-to-extend)
|
|
@@ -56,9 +56,9 @@
|
|
|
56
56
|
| Feature | Count | Description |
|
|
57
57
|
| :---------------- | :---- | :--------------------------------------------------------------------- |
|
|
58
58
|
| 🤖 **AI Agents** | 19 | Specialized roles (Mobile, DevOps, Database, Security, Performance...) |
|
|
59
|
-
| 🛠️ **Skills** |
|
|
59
|
+
| 🛠️ **Skills** | 33 | Domain knowledge modules (API, Testing, MCP, Architecture, Docker...) |
|
|
60
60
|
| ⌨️ **Commands** | 31 | Slash commands for every development workflow |
|
|
61
|
-
| 🔄 **Workflows** |
|
|
61
|
+
| 🔄 **Workflows** | 16 | Process templates (/create, /debug, /deploy, /pr, /test...) |
|
|
62
62
|
| ⚙️ **Runtime** | 29 | Runtime engine modules (governance, reputation, self-healing...) |
|
|
63
63
|
| ✅ **Checklists** | 4 | Quality gates (session-start, session-end, pre-commit, task-complete) |
|
|
64
64
|
| ⚖️ **Rules** | 8 | Modular governance constraints (coding, security, testing, git, docs, sprint) |
|
|
@@ -149,7 +149,7 @@ Antigravity AI Kit is designed to **never touch your project files**. All operat
|
|
|
149
149
|
┌─────────────────────────────────────────────────────────────────────┐
|
|
150
150
|
│ USER INTERFACE LAYER │
|
|
151
151
|
│ ┌─────────────────────────┐ ┌─────────────────────────┐ │
|
|
152
|
-
│ │ Slash Commands (31) │ │ Workflows (
|
|
152
|
+
│ │ Slash Commands (31) │ │ Workflows (15) │ │
|
|
153
153
|
│ └────────────┬────────────┘ └────────────┬────────────┘ │
|
|
154
154
|
├───────────────┼────────────────────────────┼────────────────────────┤
|
|
155
155
|
│ ▼ INTELLIGENCE LAYER ▼ │
|
|
@@ -320,12 +320,13 @@ EXPLORE → PLAN → IMPLEMENT → VERIFY → CHECKPOINT → REVIEW → DEPLOY
|
|
|
320
320
|
|
|
321
321
|
---
|
|
322
322
|
|
|
323
|
-
## 🛠️ Skills (
|
|
323
|
+
## 🛠️ Skills (33)
|
|
324
324
|
|
|
325
|
-
### Operational Skills (
|
|
325
|
+
### Operational Skills (6)
|
|
326
326
|
|
|
327
327
|
| Skill | Purpose |
|
|
328
328
|
| :-------------------- | :------------------------ |
|
|
329
|
+
| `production-readiness`| Production readiness audits |
|
|
329
330
|
| `verification-loop` | Continuous quality gates |
|
|
330
331
|
| `continuous-learning` | Pattern extraction (PAAL) |
|
|
331
332
|
| `strategic-compact` | Context window management |
|
|
@@ -423,7 +424,7 @@ Antigravity AI Kit v3.2.0 includes a **full runtime engine** built across 4 phas
|
|
|
423
424
|
|
|
424
425
|
---
|
|
425
426
|
|
|
426
|
-
## 🔄 Workflows (
|
|
427
|
+
## 🔄 Workflows (16)
|
|
427
428
|
|
|
428
429
|
| Workflow | Description | Command |
|
|
429
430
|
| :---------------- | :----------------------- | :--------------- |
|
|
@@ -434,6 +435,8 @@ Antigravity AI Kit v3.2.0 includes a **full runtime engine** built across 4 phas
|
|
|
434
435
|
| **enhance** | Improve existing code | `/enhance` |
|
|
435
436
|
| **orchestrate** | Multi-agent coordination | `/orchestrate` |
|
|
436
437
|
| **plan** | Implementation planning | `/plan` |
|
|
438
|
+
| **pr** | Production-grade PR creation | `/pr` |
|
|
439
|
+
| **preflight** | Production readiness assessment | `/preflight` |
|
|
437
440
|
| **preview** | Preview changes | `/preview` |
|
|
438
441
|
| **quality-gate** | Pre-task validation | `/quality-gate` |
|
|
439
442
|
| **retrospective** | Sprint audit & review | `/retrospective` |
|
|
@@ -634,7 +637,7 @@ antigravity-ai-kit/
|
|
|
634
637
|
│ ├── agents/ # 19 specialized agents
|
|
635
638
|
│ ├── commands/ # 31 slash commands
|
|
636
639
|
│ ├── skills/ # 32 capability modules
|
|
637
|
-
│ ├── workflows/ #
|
|
640
|
+
│ ├── workflows/ # 15 process templates
|
|
638
641
|
│ ├── engine/ # Autonomy Engine (state machine, loading rules, configs)
|
|
639
642
|
│ ├── hooks/ # 8 event hooks (runtime + git-hook)
|
|
640
643
|
│ ├── rules/ # 8 modular governance rules
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "antigravity-ai-kit",
|
|
3
|
-
"version": "3.
|
|
4
|
-
"description": "🚀 Trust-Grade AI development framework with a 29-module runtime engine — 19 Agents,
|
|
3
|
+
"version": "3.7.0",
|
|
4
|
+
"description": "🚀 Trust-Grade AI development framework with a 29-module runtime engine — 19 Agents, 33 Skills, 31 Commands, 16 Workflows, 8 Rules, 341 Tests. Workflow enforcement, task governance, agent reputation, self-healing, and skill marketplace.",
|
|
5
5
|
"main": "bin/ag-kit.js",
|
|
6
6
|
"bin": {
|
|
7
7
|
"ag-kit": "./bin/ag-kit.js"
|