ronce-racine 0.5.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/AGENTS.md +90 -0
- package/LICENSE +21 -0
- package/README.md +281 -0
- package/agents/code-reviewer.md +33 -0
- package/agents/qa-tester.md +28 -0
- package/dist/hooks/README.md +182 -0
- package/dist/hooks/bash-npm-silent.mjs +81 -0
- package/dist/hooks/session-inject.mjs +53 -0
- package/dist/hooks/session-precompact.mjs +36 -0
- package/dist/hooks/session-writer.mjs +142 -0
- package/dist/hooks/skill-reminder.mjs +89 -0
- package/dist/hooks/truncate-bash-output.mjs +46 -0
- package/dist/hooks/truncate-output.mjs +88 -0
- package/dist/hooks/worktree-env-setup.mjs +123 -0
- package/dist/install.js +962 -0
- package/docs/adopting-a-repo.md +80 -0
- package/docs/architecture.md +76 -0
- package/docs/decisions.md +72 -0
- package/docs/developing.md +143 -0
- package/docs/evaluating-skills.md +41 -0
- package/docs/git-worktrees.md +62 -0
- package/docs/rules/clean-architecture-deps.md +66 -0
- package/docs/rules/commits.md +59 -0
- package/docs/rules/detection-gap-protocol.md +55 -0
- package/docs/rules/error-handling-discipline.md +62 -0
- package/docs/rules/minimal-code.md +58 -0
- package/docs/rules/no-raw-sql-interpolation.md +57 -0
- package/docs/rules/pre-commit-secret-detection.md +54 -0
- package/docs/rules/secure-logging.md +53 -0
- package/docs/rules/sql-migrations-discipline.md +58 -0
- package/docs/rules/subscription-cleanup.md +63 -0
- package/docs/rules/test-discipline.md +66 -0
- package/docs/rules/ui-states-complete.md +52 -0
- package/docs/templates/SKILL.template.md +66 -0
- package/docs/templates/rule.template.md +16 -0
- package/docs/writing-a-rule.md +43 -0
- package/docs/writing-a-skill.md +118 -0
- package/package.json +45 -0
- package/rules/clean-architecture-deps.md +20 -0
- package/rules/commits.md +16 -0
- package/rules/detection-gap-protocol.md +35 -0
- package/rules/error-handling-discipline.md +23 -0
- package/rules/minimal-code.md +32 -0
- package/rules/no-raw-sql-interpolation.md +20 -0
- package/rules/pre-commit-secret-detection.md +14 -0
- package/rules/secure-logging.md +16 -0
- package/rules/sql-migrations-discipline.md +18 -0
- package/rules/subscription-cleanup.md +22 -0
- package/rules/test-discipline.md +20 -0
- package/rules/ui-states-complete.md +23 -0
- package/scripts/subscription-leak-scan.ts +53 -0
- package/skills/adversarial-feature-challenge/README.md +65 -0
- package/skills/adversarial-feature-challenge/SKILL.md +96 -0
- package/skills/adversarial-feature-challenge/assets/fuzz-payloads.txt +60 -0
- package/skills/adversarial-feature-challenge/templates/challenge-report.md +42 -0
- package/skills/api-contract-versioning/README.md +62 -0
- package/skills/api-contract-versioning/SKILL.md +76 -0
- package/skills/api-contract-versioning/templates/consumer-inventory.md +29 -0
- package/skills/audit-architecture/README.md +56 -0
- package/skills/audit-architecture/SKILL.md +97 -0
- package/skills/audit-architecture/reference/ar-architecture.md +275 -0
- package/skills/audit-architecture/reference/di-disponibilite.md +252 -0
- package/skills/audit-architecture/reference/im-incidents.md +217 -0
- package/skills/audit-architecture/reference/pa-pannes.md +362 -0
- package/skills/audit-architecture/reference/re-recuperation.md +300 -0
- package/skills/audit-architecture/reference/sc-scalabilite.md +173 -0
- package/skills/audit-architecture/reference/su-support.md +180 -0
- package/skills/audit-ci-cd/README.md +54 -0
- package/skills/audit-ci-cd/SKILL.md +124 -0
- package/skills/audit-ci-cd/reference/artefacts.md +39 -0
- package/skills/audit-ci-cd/reference/deploiement.md +100 -0
- package/skills/audit-ci-cd/reference/dora.md +94 -0
- package/skills/audit-ci-cd/reference/iac.md +40 -0
- package/skills/audit-ci-cd/reference/pipeline-ci.md +36 -0
- package/skills/audit-ci-cd/reference/supply-chain.md +44 -0
- package/skills/audit-compliance/README.md +69 -0
- package/skills/audit-compliance/SKILL.md +176 -0
- package/skills/audit-compliance/reference/conformite-rgpd.md +295 -0
- package/skills/audit-compliance/reference/finops.md +318 -0
- package/skills/audit-compliance/reference/gouvernance-donnees.md +238 -0
- package/skills/audit-industrialisation/README.md +53 -0
- package/skills/audit-industrialisation/SKILL.md +251 -0
- package/skills/audit-observability/README.md +64 -0
- package/skills/audit-observability/SKILL.md +134 -0
- package/skills/audit-observability/reference/alerting.md +214 -0
- package/skills/audit-observability/reference/logging.md +114 -0
- package/skills/audit-observability/reference/metriques.md +166 -0
- package/skills/audit-observability/reference/traces-dashboards.md +90 -0
- package/skills/audit-performance-frontend/README.md +91 -0
- package/skills/audit-performance-frontend/SKILL.md +194 -0
- package/skills/audit-performance-frontend/reference/assets-cache-network.md +129 -0
- package/skills/audit-performance-frontend/reference/css-rendering-pipeline.md +154 -0
- package/skills/audit-performance-frontend/reference/html-critical-path.md +128 -0
- package/skills/audit-performance-frontend/reference/js-engine-runtime.md +280 -0
- package/skills/audit-performance-frontend/reference/memory-gc.md +126 -0
- package/skills/audit-performance-frontend/reference/profiling-tooling.md +98 -0
- package/skills/audit-quality/README.md +85 -0
- package/skills/audit-quality/SKILL.md +126 -0
- package/skills/audit-quality/reference/qa-devops.md +539 -0
- package/skills/audit-quality/reference/qu-qualite-donnees.md +402 -0
- package/skills/audit-report/README.md +72 -0
- package/skills/audit-report/SKILL.md +241 -0
- package/skills/audit-report/reference/scoring-model.md +45 -0
- package/skills/audit-security/README.md +72 -0
- package/skills/audit-security/SKILL.md +140 -0
- package/skills/audit-security/reference/auth-identite.md +98 -0
- package/skills/audit-security/reference/autorisation.md +66 -0
- package/skills/audit-security/reference/chiffrement-tls.md +97 -0
- package/skills/audit-security/reference/detection-patching.md +67 -0
- package/skills/audit-security/reference/incident-response.md +98 -0
- package/skills/audit-security/reference/reseau-conteneurs.md +72 -0
- package/skills/audit-security/reference/secrets.md +36 -0
- package/skills/audit-testing/README.md +82 -0
- package/skills/audit-testing/SKILL.md +131 -0
- package/skills/audit-testing/reference/golden-dataset.md +65 -0
- package/skills/audit-testing/reference/resilience-chaos.md +93 -0
- package/skills/audit-testing/reference/tests-contractuels.md +65 -0
- package/skills/audit-testing/reference/tests-e2e-flaky.md +67 -0
- package/skills/audit-testing/reference/tests-unit-integ-ci.md +125 -0
- package/skills/bug-ticket-root-cause/README.md +67 -0
- package/skills/bug-ticket-root-cause/SKILL.md +86 -0
- package/skills/bug-ticket-root-cause/templates/bug-ticket.md +43 -0
- package/skills/bug-triage-structured/README.md +63 -0
- package/skills/bug-triage-structured/SKILL.md +104 -0
- package/skills/bug-triage-structured/templates/bug-triage.md +38 -0
- package/skills/ci-pipeline-orchestration/README.md +55 -0
- package/skills/ci-pipeline-orchestration/SKILL.md +110 -0
- package/skills/commit-readiness-review/README.md +66 -0
- package/skills/commit-readiness-review/SKILL.md +82 -0
- package/skills/commit-readiness-review/scripts/precommit-scan.ts +81 -0
- package/skills/comprehensive-test-strategy/README.md +64 -0
- package/skills/comprehensive-test-strategy/SKILL.md +108 -0
- package/skills/comprehensive-test-strategy/reference/testing-advanced.md +85 -0
- package/skills/daily-workflow-optimization/README.md +56 -0
- package/skills/daily-workflow-optimization/SKILL.md +80 -0
- package/skills/database-schema-evolution/README.md +54 -0
- package/skills/database-schema-evolution/SKILL.md +107 -0
- package/skills/ddd-backend-implementation/README.md +63 -0
- package/skills/ddd-backend-implementation/SKILL.md +95 -0
- package/skills/design-system-component-lifecycle/README.md +56 -0
- package/skills/design-system-component-lifecycle/SKILL.md +97 -0
- package/skills/design-system-component-lifecycle/templates/component-contract.md +43 -0
- package/skills/detection-sweep/README.md +58 -0
- package/skills/detection-sweep/SKILL.md +93 -0
- package/skills/detection-sweep/scripts/sweep.ts +80 -0
- package/skills/domain-modeling-design/README.md +57 -0
- package/skills/domain-modeling-design/SKILL.md +83 -0
- package/skills/frontend-fullstack-implementation/README.md +60 -0
- package/skills/frontend-fullstack-implementation/SKILL.md +133 -0
- package/skills/frontend-spec-call-site-audit/README.md +66 -0
- package/skills/frontend-spec-call-site-audit/SKILL.md +82 -0
- package/skills/frontend-spec-call-site-audit/scripts/audit-entry-points.ts +79 -0
- package/skills/frontend-spec-call-site-audit/templates/ticket-frontend.md +32 -0
- package/skills/merge-request-review/README.md +60 -0
- package/skills/merge-request-review/SKILL.md +77 -0
- package/skills/merge-request-review/templates/mr-review-report.md +29 -0
- package/skills/production-incident-diagnostic/README.md +63 -0
- package/skills/production-incident-diagnostic/SKILL.md +103 -0
- package/skills/production-incident-diagnostic/templates/incident-report.md +33 -0
- package/skills/qa-session-intake/README.md +56 -0
- package/skills/qa-session-intake/SKILL.md +78 -0
- package/skills/recording-decisions/README.md +91 -0
- package/skills/recording-decisions/SKILL.md +84 -0
- package/skills/recurring-bug-root-cause/README.md +64 -0
- package/skills/recurring-bug-root-cause/SKILL.md +93 -0
- package/skills/recurring-bug-root-cause/scripts/detect-recurring-fixes.ts +46 -0
- package/skills/recurring-bug-root-cause/templates/postmortem-recidive.md +37 -0
- package/skills/refactoring-shared-component-api/README.md +50 -0
- package/skills/refactoring-shared-component-api/SKILL.md +84 -0
- package/skills/refactoring-shared-component-api/scripts/sweep-call-sites.ts +85 -0
- package/skills/refactoring-shared-component-api/templates/migration-checklist.md +19 -0
- package/skills/validating-features-end-to-end/README.md +50 -0
- package/skills/validating-features-end-to-end/SKILL.md +90 -0
- package/skills/visual-regression-check/README.md +51 -0
- package/skills/visual-regression-check/SKILL.md +89 -0
- package/skills/writing-robust-tests/README.md +53 -0
- package/skills/writing-robust-tests/SKILL.md +88 -0
- package/templates/.adopted.example +8 -0
- package/templates/anti-drift.gitlab-ci.yml +23 -0
|
@@ -0,0 +1,318 @@
|
|
|
1
|
+
# Section FI - FinOps: Cost Management (11 questions)
|
|
2
|
+
|
|
3
|
+
## Table of contents
|
|
4
|
+
|
|
5
|
+
- [FI-01 - Third-party API call cost monitoring](#fi-01--third-party-api-call-cost-monitoring--criticality--should)
|
|
6
|
+
- [FI-01a - Cost-tracking granularity](#fi-01a--cost-tracking-granularity--criticality--should)
|
|
7
|
+
- [FI-02 - Caching](#fi-02--caching--criticality--should)
|
|
8
|
+
- [FI-02a - Cache invalidation strategy](#fi-02a--cache-invalidation-strategy--criticality--should)
|
|
9
|
+
- [FI-03 - Superfluous-call detection + batching opportunities](#fi-03--superfluous-call-detection--batching-opportunities--criticality--should)
|
|
10
|
+
- [FI-04 - Per-customer cost attribution (tagging)](#fi-04--per-customer-cost-attribution-tagging--criticality--should)
|
|
11
|
+
- [FI-05 - Per-customer consumption reporting](#fi-05--per-customer-consumption-reporting--criticality--could)
|
|
12
|
+
- [FI-06 - Abuse / abnormal-usage detection](#fi-06--abuse--abnormal-usage-detection--criticality--should)
|
|
13
|
+
- [FI-06a - Actions on detected abuse](#fi-06a--actions-on-detected-abuse--criticality--should)
|
|
14
|
+
- [FI-07 - Cloud-waste detection and elimination](#fi-07--cloud-waste-detection-and-elimination--criticality--should)
|
|
15
|
+
- [FI-08 - Cloud commitment and reservation strategy](#fi-08--cloud-commitment-and-reservation-strategy--criticality--could)
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
### FI-01 - Third-party API call cost monitoring - Criticality: **SHOULD**
|
|
20
|
+
|
|
21
|
+
**Analyze:** Resource tags, configured budgets, cost alerts, API-call monitoring
|
|
22
|
+
|
|
23
|
+
**Verification commands:**
|
|
24
|
+
```bash
|
|
25
|
+
grep -ri "tags\|cost\|budget\|billing" . --include="*.tf" --include="*.yml" --include="*.yaml" 2>/dev/null | head -10
|
|
26
|
+
grep -ri "api.*cost\|api.*pricing\|usage.*track\|metering" . --include="*.ts" --include="*.rs" --include="*.py" 2>/dev/null | head -10
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
**Check:**
|
|
30
|
+
- Third-party API costs monitored (not just the cloud bill)
|
|
31
|
+
- Budget defined and tracked
|
|
32
|
+
- Alerts on cost overrun
|
|
33
|
+
- Periodic cost review
|
|
34
|
+
|
|
35
|
+
**Levels:**
|
|
36
|
+
| Level | Criteria |
|
|
37
|
+
|--------|----------|
|
|
38
|
+
| 0 | No visibility into costs. Cloud bill not analyzed. |
|
|
39
|
+
| 1 | Bill reviewed monthly. No tags. |
|
|
40
|
+
| 2 | Resources tagged. Budget defined. Alert on overrun. |
|
|
41
|
+
| 3 | FinOps dashboard. Cost per service/feature. Monthly review. |
|
|
42
|
+
| 4 | FinOps culture. Continuous optimization. Reserved instances/savings plans. Unit economics. |
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
### FI-01a - Cost-tracking granularity - Criticality: **SHOULD**
|
|
47
|
+
|
|
48
|
+
**Condition:** Evaluate if FI-01 >= 2
|
|
49
|
+
|
|
50
|
+
**Analyze:** Level of tracking detail: global, per service, per environment, per customer, per transaction
|
|
51
|
+
|
|
52
|
+
**Verification commands:**
|
|
53
|
+
```bash
|
|
54
|
+
grep -ri "cost.*center\|cost.*allocation\|unit.*economic\|cost.*per\|tag.*team\|tag.*project\|tag.*env" . --include="*.tf" --include="*.yml" 2>/dev/null | head -10
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
**Check:**
|
|
58
|
+
- Tracking granularity (global → service → environment → customer → transaction)
|
|
59
|
+
- Tagging strategy
|
|
60
|
+
- Cost centers defined
|
|
61
|
+
- Unit economics computed
|
|
62
|
+
|
|
63
|
+
**Levels:**
|
|
64
|
+
| Level | Criteria |
|
|
65
|
+
|--------|----------|
|
|
66
|
+
| 0 | Global cost only. |
|
|
67
|
+
| 1 | Per API/service. |
|
|
68
|
+
| 2 | Per environment (prod/staging). |
|
|
69
|
+
| 3 | Per customer/tenant and per feature. |
|
|
70
|
+
| 4 | Per transaction with unit economics. |
|
|
71
|
+
|
|
72
|
+
---
|
|
73
|
+
|
|
74
|
+
### FI-02 - Caching - Criticality: **SHOULD**
|
|
75
|
+
|
|
76
|
+
**Analyze:** Cache strategy, Redis/Memcached configs, CDN, application cache
|
|
77
|
+
|
|
78
|
+
**Verification commands:**
|
|
79
|
+
```bash
|
|
80
|
+
grep -ri "redis\|memcached\|cache\|cdn\|cloudfront\|varnish" . --include="*.ts" --include="*.rs" --include="*.yml" --include="*.yaml" --include="*.env*" 2>/dev/null | head -10
|
|
81
|
+
grep -ri "spot\|preemptible\|reserved\|savings" . --include="*.tf" --include="*.yml" 2>/dev/null | head -5
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
**Check:**
|
|
85
|
+
- Documented cache strategy
|
|
86
|
+
- Multi-level cache (CDN, reverse proxy, application, DB)
|
|
87
|
+
- Hit rate monitored
|
|
88
|
+
- Suitable eviction policy
|
|
89
|
+
|
|
90
|
+
**Levels:**
|
|
91
|
+
| Level | Criteria |
|
|
92
|
+
|--------|----------|
|
|
93
|
+
| 0 | No cache. Every request recomputed. |
|
|
94
|
+
| 1 | Basic cache on a few endpoints. No monitoring. |
|
|
95
|
+
| 2 | Documented cache strategy. Hit rate > 70%. |
|
|
96
|
+
| 3 | Multi-level cache. Hit rate > 90%. Automatic warming. |
|
|
97
|
+
| 4 | Smart adaptive cache. Predictive caching. Cost/performance optimized. |
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
101
|
+
### FI-02a - Cache invalidation strategy - Criticality: **SHOULD**
|
|
102
|
+
|
|
103
|
+
**Condition:** Evaluate if FI-02 >= 2
|
|
104
|
+
|
|
105
|
+
**Analyze:** Invalidation by TTL, event-driven, write-through, versioning
|
|
106
|
+
|
|
107
|
+
**Verification commands:**
|
|
108
|
+
```bash
|
|
109
|
+
grep -ri "invalidat\|cache.*bust\|cache.*clear\|write.through\|cache.aside\|stale.while.revalidate" . --include="*.ts" --include="*.rs" --include="*.py" 2>/dev/null | head -10
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
**Check:**
|
|
113
|
+
- Invalidation strategy defined (TTL, event-driven, write-through)
|
|
114
|
+
- Freshness/performance/complexity trade-off documented
|
|
115
|
+
- Distributed cache consistency if applicable
|
|
116
|
+
|
|
117
|
+
**Levels:**
|
|
118
|
+
| Level | Criteria |
|
|
119
|
+
|--------|----------|
|
|
120
|
+
| 0 | Fixed TTL only. Data potentially stale. |
|
|
121
|
+
| 1 | Manual invalidation on request. |
|
|
122
|
+
| 2 | Event-driven invalidation for critical cases. |
|
|
123
|
+
| 3 | Cache-aside with write-through. Versioning. |
|
|
124
|
+
| 4 | Distributed cache consistency. Eventual consistency documented and acceptable. |
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
### FI-03 - Superfluous-call detection + batching opportunities - Criticality: **SHOULD**
|
|
129
|
+
|
|
130
|
+
**Analyze:** API-call patterns, N+1 queries, excessive retries, batching opportunities
|
|
131
|
+
|
|
132
|
+
**Verification commands:**
|
|
133
|
+
```bash
|
|
134
|
+
grep -ri "dataloader\|batch\|bulk\|n.plus.one\|n\+1" . --include="*.ts" --include="*.rs" --include="*.py" 2>/dev/null | head -10
|
|
135
|
+
grep -ri "retry.*count\|retry.*max\|retry.*storm" . --include="*.ts" --include="*.rs" --include="*.yml" 2>/dev/null | head -5
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
**Check:**
|
|
139
|
+
- Analysis of call patterns (N+1, excessive retries, redundant calls)
|
|
140
|
+
- Batching opportunities identified
|
|
141
|
+
- DataLoader pattern used if applicable
|
|
142
|
+
- Call metrics per endpoint
|
|
143
|
+
|
|
144
|
+
**Levels:**
|
|
145
|
+
| Level | Criteria |
|
|
146
|
+
|--------|----------|
|
|
147
|
+
| 0 | No analysis. Potentially a lot of waste. |
|
|
148
|
+
| 1 | Occasional analysis during cost incidents. |
|
|
149
|
+
| 2 | Call metrics per endpoint. Manual anomaly detection. |
|
|
150
|
+
| 3 | Alerts on abnormal patterns (N+1, retry storms). Quarterly review. |
|
|
151
|
+
| 4 | ML detection of inefficiencies. Auto batching suggestions. A/B testing. |
|
|
152
|
+
|
|
153
|
+
---
|
|
154
|
+
|
|
155
|
+
### FI-04 - Per-customer cost attribution (tagging) - Criticality: **SHOULD**
|
|
156
|
+
|
|
157
|
+
**Analyze:** Per-tenant consumption tracking in multi-tenant, cost allocation
|
|
158
|
+
|
|
159
|
+
**Verification commands:**
|
|
160
|
+
```bash
|
|
161
|
+
grep -ri "tenant.*cost\|cost.*tenant\|metering\|usage.*track\|billing.*tenant" . --include="*.ts" --include="*.rs" --include="*.py" 2>/dev/null | head -10
|
|
162
|
+
grep -ri "cost.*allocat\|chargeback\|showback\|profitability" . --include="*.md" --include="*.yml" 2>/dev/null | head -5
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
**Check:**
|
|
166
|
+
- Consumption tracking per customer/tenant
|
|
167
|
+
- Resource tagging per tenant
|
|
168
|
+
- Per-customer cost reports
|
|
169
|
+
- Per-customer profitability analysis
|
|
170
|
+
- Per-customer unit economics
|
|
171
|
+
|
|
172
|
+
**Levels:**
|
|
173
|
+
| Level | Criteria |
|
|
174
|
+
|--------|----------|
|
|
175
|
+
| 0 | No attribution. Costs pooled without visibility. |
|
|
176
|
+
| 1 | Approximate attribution based on general usage. |
|
|
177
|
+
| 2 | Resource tagging per tenant. Manual reports. |
|
|
178
|
+
| 3 | Automatic attribution via metrics. Customer dashboard. Cost allocation. |
|
|
179
|
+
| 4 | Per-customer unit economics. Profitability analysis. Dynamic pricing ready. |
|
|
180
|
+
|
|
181
|
+
---
|
|
182
|
+
|
|
183
|
+
### FI-05 - Per-customer consumption reporting - Criticality: **COULD**
|
|
184
|
+
|
|
185
|
+
**Analyze:** Customer consumption reports, dashboards, projections
|
|
186
|
+
|
|
187
|
+
**Verification commands:**
|
|
188
|
+
```bash
|
|
189
|
+
grep -ri "usage.*report\|consumption.*report\|billing.*dashboard\|client.*report" . --include="*.ts" --include="*.rs" --include="*.py" --include="*.md" 2>/dev/null | head -10
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
**Check:**
|
|
193
|
+
- Consumption reports for customers
|
|
194
|
+
- Self-service dashboard
|
|
195
|
+
- History and trends
|
|
196
|
+
- Cost projections
|
|
197
|
+
- Optimization recommendations
|
|
198
|
+
|
|
199
|
+
**Levels:**
|
|
200
|
+
| Level | Criteria |
|
|
201
|
+
|--------|----------|
|
|
202
|
+
| 0 | No customer reporting. |
|
|
203
|
+
| 1 | Reporting on request. Manual and approximate. |
|
|
204
|
+
| 2 | Automated monthly reports. Main metrics. |
|
|
205
|
+
| 3 | Self-service dashboard for customers. History and trends. Configurable alerts. |
|
|
206
|
+
| 4 | Real-time reporting. Cost prediction. Optimization recommendations. |
|
|
207
|
+
|
|
208
|
+
---
|
|
209
|
+
|
|
210
|
+
### FI-06 - Abuse / abnormal-usage detection - Criticality: **SHOULD**
|
|
211
|
+
|
|
212
|
+
**Analyze:** Rate limiting, quotas, usage-anomaly detection, noisy neighbor
|
|
213
|
+
|
|
214
|
+
**Verification commands:**
|
|
215
|
+
```bash
|
|
216
|
+
grep -ri "rate.limit\|throttl\|quota\|abuse\|noisy.neighbor\|fair.usage" . --include="*.ts" --include="*.rs" --include="*.py" --include="*.yml" 2>/dev/null | head -10
|
|
217
|
+
grep -ri "anomaly.*detect\|usage.*pattern\|spike.*detect" . --include="*.ts" --include="*.rs" 2>/dev/null | head -5
|
|
218
|
+
```
|
|
219
|
+
|
|
220
|
+
**Check:**
|
|
221
|
+
- Rate limiting per customer/tenant
|
|
222
|
+
- Quotas configured
|
|
223
|
+
- Usage-anomaly detection
|
|
224
|
+
- Fair usage policy
|
|
225
|
+
- Protection against noisy neighbors
|
|
226
|
+
|
|
227
|
+
**Levels:**
|
|
228
|
+
| Level | Criteria |
|
|
229
|
+
|--------|----------|
|
|
230
|
+
| 0 | No detection. Discovered through impact on other customers. |
|
|
231
|
+
| 1 | Basic global rate limiting. No per-customer detection. |
|
|
232
|
+
| 2 | Per-customer quotas. Alerts on overrun. Manual throttling. |
|
|
233
|
+
| 3 | Anomaly detection on usage patterns. Auto-throttling. Customer notification. |
|
|
234
|
+
| 4 | Early ML detection. Automated remediation. Fair usage policies enforced. |
|
|
235
|
+
|
|
236
|
+
---
|
|
237
|
+
|
|
238
|
+
### FI-06a - Actions on detected abuse - Criticality: **SHOULD**
|
|
239
|
+
|
|
240
|
+
**Condition:** Evaluate if FI-06 >= 2
|
|
241
|
+
|
|
242
|
+
**Analyze:** Abuse-response protocol, graceful degradation, escalation
|
|
243
|
+
|
|
244
|
+
**Verification commands:**
|
|
245
|
+
```bash
|
|
246
|
+
grep -ri "abuse.*response\|throttle.*response\|escalat.*abuse\|upgrade.*plan" . --include="*.ts" --include="*.rs" --include="*.md" 2>/dev/null | head -10
|
|
247
|
+
```
|
|
248
|
+
|
|
249
|
+
**Check:**
|
|
250
|
+
- Defined response protocol (graceful degradation, no abrupt cutoff)
|
|
251
|
+
- Automatic customer notification
|
|
252
|
+
- Progressive escalation (throttling → notification → suspension)
|
|
253
|
+
- Self-service upgrade option
|
|
254
|
+
- Protection of other customers' SLA
|
|
255
|
+
|
|
256
|
+
**Levels:**
|
|
257
|
+
| Level | Criteria |
|
|
258
|
+
|--------|----------|
|
|
259
|
+
| 0 | Nothing. Absorb the cost. |
|
|
260
|
+
| 1 | Manual customer contact. Long delay. |
|
|
261
|
+
| 2 | Auto throttling + notification. |
|
|
262
|
+
| 3 | Defined escalation process. Additional billing possible. |
|
|
263
|
+
| 4 | Automated response workflow. Self-service upgrade. SLA protection. |
|
|
264
|
+
|
|
265
|
+
---
|
|
266
|
+
|
|
267
|
+
### FI-07 - Cloud-waste detection and elimination - Criticality: **SHOULD**
|
|
268
|
+
|
|
269
|
+
**Analyze:** Unused resources, orphaned volumes, forgotten environments
|
|
270
|
+
|
|
271
|
+
**Verification commands:**
|
|
272
|
+
```bash
|
|
273
|
+
grep -ri "trusted.advisor\|cost.explorer\|advisor\|waste\|unused\|orphan\|idle" . --include="*.tf" --include="*.yml" --include="*.md" 2>/dev/null | head -10
|
|
274
|
+
grep -ri "schedule.*stop\|auto.*shutdown\|cleanup.*env" . --include="*.tf" --include="*.yml" --include="*.sh" 2>/dev/null | head -5
|
|
275
|
+
```
|
|
276
|
+
|
|
277
|
+
**Check:**
|
|
278
|
+
- Detection of unused resources (idle instances, orphaned volumes)
|
|
279
|
+
- Cleanup of forgotten environments (staging, review apps)
|
|
280
|
+
- Detection tools (Trusted Advisor, Azure Advisor, Infracost)
|
|
281
|
+
- Alerts on under-used resources
|
|
282
|
+
- Automatic cleanup policy
|
|
283
|
+
|
|
284
|
+
**Levels:**
|
|
285
|
+
| Level | Criteria |
|
|
286
|
+
|--------|----------|
|
|
287
|
+
| 0 | No visibility into waste. Resources not detected. |
|
|
288
|
+
| 1 | Occasional manual checks. Reactive cleanup. |
|
|
289
|
+
| 2 | Cloud-provider tools used (Trusted Advisor, Advisor). Periodic reviews. |
|
|
290
|
+
| 3 | Automated waste detection. Alerts on unused resources. Cleanup policies. Scheduled reviews. |
|
|
291
|
+
| 4 | Continuous optimization platform. Auto-deletion of unused resources. Waste prevention at provisioning time. |
|
|
292
|
+
|
|
293
|
+
---
|
|
294
|
+
|
|
295
|
+
### FI-08 - Cloud commitment and reservation strategy - Criticality: **COULD**
|
|
296
|
+
|
|
297
|
+
**Analyze:** Reserved Instances, Savings Plans, Spot instances, commitment strategy
|
|
298
|
+
|
|
299
|
+
**Verification commands:**
|
|
300
|
+
```bash
|
|
301
|
+
grep -ri "reserved.instance\|savings.plan\|spot\|preemptible\|commitment\|reservation" . --include="*.tf" --include="*.yml" --include="*.md" 2>/dev/null | head -10
|
|
302
|
+
```
|
|
303
|
+
|
|
304
|
+
**Check:**
|
|
305
|
+
- Use of Reserved Instances / Savings Plans for stable workloads
|
|
306
|
+
- Spot instances for flexible workloads
|
|
307
|
+
- Analysis of usage patterns to size the commitments
|
|
308
|
+
- Optimized on-demand / reserved / spot mix
|
|
309
|
+
- Coverage objectives defined (% of workload under reservation)
|
|
310
|
+
|
|
311
|
+
**Levels:**
|
|
312
|
+
| Level | Criteria |
|
|
313
|
+
|--------|----------|
|
|
314
|
+
| 0 | 100% on-demand. No use of commitments or reservations. |
|
|
315
|
+
| 1 | Awareness of reservation options but not used. |
|
|
316
|
+
| 2 | A few Reserved Instances for obvious stable workloads. |
|
|
317
|
+
| 3 | Systematic analysis of usage patterns. Reserved/Savings/Spot mix. Coverage objectives defined. |
|
|
318
|
+
| 4 | Automated reservation management. Dynamic adjustment. Predictive purchasing. 70%+ coverage of stable workloads. |
|
|
@@ -0,0 +1,238 @@
|
|
|
1
|
+
# Section DG - Data Governance (8 questions)
|
|
2
|
+
|
|
3
|
+
## Table of contents
|
|
4
|
+
|
|
5
|
+
- [DG-01 - Data ownership and stewardship](#dg-01--data-ownership-and-stewardship--criticality--should)
|
|
6
|
+
- [DG-02 - Data catalog and metadata dictionary](#dg-02--data-catalog-and-metadata-dictionary--criticality--should)
|
|
7
|
+
- [DG-03 - Migrations and schema evolution](#dg-03--migrations-and-schema-evolution--criticality--must)
|
|
8
|
+
- [DG-04 - Data contracts between producers and consumers](#dg-04--data-contracts-between-producers-and-consumers--criticality--should)
|
|
9
|
+
- [DG-05 - Continuous data-quality monitoring](#dg-05--continuous-data-quality-monitoring--criticality--should)
|
|
10
|
+
- [DG-06 - Classification and protection of sensitive data](#dg-06--classification-and-protection-of-sensitive-data--criticality--must)
|
|
11
|
+
- [DG-07 - Retention policies and data lifecycle](#dg-07--retention-policies-and-data-lifecycle--criticality--must)
|
|
12
|
+
- [DG-08 - Data architecture and topology (Data Mesh)](#dg-08--data-architecture-and-topology-data-mesh--criticality--should)
|
|
13
|
+
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
### DG-01 - Data ownership and stewardship - Criticality: **SHOULD**
|
|
17
|
+
|
|
18
|
+
**Analyze:** Documentation of data models, data dictionary, responsibilities
|
|
19
|
+
|
|
20
|
+
**Verification commands:**
|
|
21
|
+
```bash
|
|
22
|
+
find docs/ -name "*data*" -o -name "*glossary*" -o -name "*dictionary*" -o -name "*owner*" 2>/dev/null | head -10
|
|
23
|
+
grep -ri "data.owner\|data.steward\|responsable.*donnee" . --include="*.md" --include="*.yml" 2>/dev/null | head -5
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
**Check:**
|
|
27
|
+
- Data owner identified for each domain
|
|
28
|
+
- Data catalog (documented schema)
|
|
29
|
+
- Shared business glossary
|
|
30
|
+
- Documented lineage (where the data comes from, where it goes)
|
|
31
|
+
|
|
32
|
+
**Levels:**
|
|
33
|
+
| Level | Criteria |
|
|
34
|
+
|--------|----------|
|
|
35
|
+
| 0 | Nobody knows who is responsible for which data. |
|
|
36
|
+
| 1 | Implicit data owners (whoever created the table). |
|
|
37
|
+
| 2 | Explicit data owners. Documented schema. |
|
|
38
|
+
| 3 | Formalized data catalog. Business glossary. Basic lineage. |
|
|
39
|
+
| 4 | Automated data catalog. Data contracts between teams. Data-quality SLA. |
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
### DG-02 - Data catalog and metadata dictionary - Criticality: **SHOULD**
|
|
44
|
+
|
|
45
|
+
**Analyze:** DB constraints, application validations, data-quality monitoring
|
|
46
|
+
|
|
47
|
+
**Verification commands:**
|
|
48
|
+
```bash
|
|
49
|
+
grep -ri "constraint\|unique\|not.null\|check\|foreign" . --include="*.sql" --include="*.ts" --include="*.rs" 2>/dev/null | head -10
|
|
50
|
+
find . -name "*catalog*" -o -name "*dictionar*" -o -name "*metadata*" 2>/dev/null | grep -v node_modules | head -10
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
**Check:**
|
|
54
|
+
- Integrity constraints in the database (FK, unique, not null, check)
|
|
55
|
+
- Application validation consistent with the DB schema
|
|
56
|
+
- Data-quality monitoring
|
|
57
|
+
- Data-anomaly detection
|
|
58
|
+
|
|
59
|
+
**Levels:**
|
|
60
|
+
| Level | Criteria |
|
|
61
|
+
|--------|----------|
|
|
62
|
+
| 0 | No constraints. Inconsistent data tolerated. |
|
|
63
|
+
| 1 | Basic constraints in the DB (PK, FK). Minimal application validation. |
|
|
64
|
+
| 2 | Complete constraints. Validation aligned DB <-> app. |
|
|
65
|
+
| 3 | Data-quality monitoring. Anomaly detection. Business rules in the DB. |
|
|
66
|
+
| 4 | Data-quality SLA. Automated data testing. Self-healing of known anomalies. |
|
|
67
|
+
|
|
68
|
+
---
|
|
69
|
+
|
|
70
|
+
### DG-03 - Migrations and schema evolution - Criticality: **MUST**
|
|
71
|
+
|
|
72
|
+
**Analyze:** Migration files (SQLx, Prisma, Knex, Flyway, Alembic), migration strategy
|
|
73
|
+
|
|
74
|
+
**Verification commands:**
|
|
75
|
+
```bash
|
|
76
|
+
# Migration directories
|
|
77
|
+
find . -path "*/migrations/*" -name "*.sql" -o -path "*/migrations/*" -name "*.rs" 2>/dev/null | head -10
|
|
78
|
+
ls prisma/migrations/ migrations/ alembic/ db/migrate/ 2>/dev/null
|
|
79
|
+
# Migration tool in the dependencies
|
|
80
|
+
grep -ri "migration\|migrate\|sqlx" package.json Cargo.toml 2>/dev/null
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
**Check:**
|
|
84
|
+
- Versioned and reproducible migrations
|
|
85
|
+
- No manual ALTER TABLE in production
|
|
86
|
+
- Reversible migrations (or documented forward-only)
|
|
87
|
+
- Review of migrations before execution
|
|
88
|
+
|
|
89
|
+
**Levels:**
|
|
90
|
+
| Level | Criteria |
|
|
91
|
+
|--------|----------|
|
|
92
|
+
| 0 | No migration system. Manual ALTER TABLEs. |
|
|
93
|
+
| 1 | Migration tool in place but used ad hoc. |
|
|
94
|
+
| 2 | Versioned migrations. Automated execution. Review before apply. |
|
|
95
|
+
| 3 | Reversible migrations. Migration tests. Documented zero-downtime migrations. |
|
|
96
|
+
| 4 | Schema drift detection. Migrations tested on a prod copy. Blue-green DB migrations. |
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
### DG-04 - Data contracts between producers and consumers - Criticality: **SHOULD**
|
|
101
|
+
|
|
102
|
+
**Analyze:** Data contracts, schema registries, data APIs, SLA on data
|
|
103
|
+
|
|
104
|
+
**Verification commands:**
|
|
105
|
+
```bash
|
|
106
|
+
grep -ri "data.contract\|schema.registry\|avro\|protobuf\|json.schema" . --include="*.ts" --include="*.rs" --include="*.yml" --include="*.yaml" 2>/dev/null | head -10
|
|
107
|
+
find . -name "*.avsc" -o -name "*.proto" -o -name "*schema*" 2>/dev/null | grep -v node_modules | head -10
|
|
108
|
+
grep -ri "confluent\|glue.*registry\|schema.*version" . 2>/dev/null | head -5
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
**Check:**
|
|
112
|
+
- Formal contracts between data producers and consumers
|
|
113
|
+
- Formalized schemas (Avro, Protobuf, JSON Schema)
|
|
114
|
+
- SLA on data (freshness, completeness, availability)
|
|
115
|
+
- Schema versioning and backward compatibility
|
|
116
|
+
- Contract testing in CI/CD
|
|
117
|
+
|
|
118
|
+
**Levels:**
|
|
119
|
+
| Level | Criteria |
|
|
120
|
+
|--------|----------|
|
|
121
|
+
| 0 | No contract. Consumers discover the schema from the source. Breaking changes without notice. |
|
|
122
|
+
| 1 | Schema documented informally (wiki, README). No SLA or compatibility guarantee. |
|
|
123
|
+
| 2 | Formalized schemas (Avro, Protobuf, JSON Schema). Schema registry in place. Versioning defined. |
|
|
124
|
+
| 3 | Explicit data contracts with SLA (freshness, completeness). Contract testing in CI/CD. Change notifications. |
|
|
125
|
+
| 4 | Data contracts as code versioned in Git. Backward compatibility enforced automatically. SLAs monitored with alerts. Self-service discovery portal. |
|
|
126
|
+
|
|
127
|
+
---
|
|
128
|
+
|
|
129
|
+
### DG-05 - Continuous data-quality monitoring - Criticality: **SHOULD**
|
|
130
|
+
|
|
131
|
+
**Analyze:** Data-quality tools, data tests, alerts on anomalies
|
|
132
|
+
|
|
133
|
+
**Verification commands:**
|
|
134
|
+
```bash
|
|
135
|
+
grep -ri "great.expectations\|monte.carlo\|soda\|dbt.test\|elementary\|data.quality" . --include="*.yml" --include="*.yaml" --include="*.py" --include="*.ts" 2>/dev/null | head -10
|
|
136
|
+
grep -ri "freshness\|completeness\|accuracy\|consistency\|uniqueness\|validity" . --include="*.yml" --include="*.md" 2>/dev/null | head -10
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
**Check:**
|
|
140
|
+
- Quality dimensions measured (freshness, completeness, accuracy, consistency, uniqueness, validity)
|
|
141
|
+
- Quality tests defined and run regularly
|
|
142
|
+
- Alerts on quality anomalies
|
|
143
|
+
- Data-quality dashboard
|
|
144
|
+
- Quality SLAs defined
|
|
145
|
+
|
|
146
|
+
**Levels:**
|
|
147
|
+
| Level | Criteria |
|
|
148
|
+
|--------|----------|
|
|
149
|
+
| 0 | No monitoring. Quality issues discovered by end users. |
|
|
150
|
+
| 1 | Ad-hoc manual checks via SQL queries. No alert. Reactive only. |
|
|
151
|
+
| 2 | Quality tests defined (Great Expectations, Soda, dbt tests) for critical datasets. Periodic execution. |
|
|
152
|
+
| 3 | Continuous monitoring with automatic alerts. Quality dashboard. Dimensions measured. Quality SLAs defined. |
|
|
153
|
+
| 4 | Integrated data-observability platform. ML anomaly detection. Automated root-cause analysis. Auto-remediation for simple cases. |
|
|
154
|
+
|
|
155
|
+
---
|
|
156
|
+
|
|
157
|
+
### DG-06 - Classification and protection of sensitive data - Criticality: **MUST**
|
|
158
|
+
|
|
159
|
+
**Analyze:** Classification policy, automatic PII detection, masking, access controls
|
|
160
|
+
|
|
161
|
+
**Verification commands:**
|
|
162
|
+
```bash
|
|
163
|
+
grep -ri "classification\|sensib\|confidential\|restricted\|public\|internal" . --include="*.md" --include="*.yml" 2>/dev/null | head -10
|
|
164
|
+
grep -ri "pii.*detect\|data.*masking\|tokeniz\|column.*encrypt" . --include="*.ts" --include="*.rs" --include="*.py" --include="*.yml" 2>/dev/null | head -10
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
**Check:**
|
|
168
|
+
- Classification levels defined (public, internal, confidential, restricted)
|
|
169
|
+
- PII identified and inventoried
|
|
170
|
+
- Automatic PII detection
|
|
171
|
+
- Dynamic masking depending on context
|
|
172
|
+
- Access controls aligned with the classification
|
|
173
|
+
|
|
174
|
+
**Levels:**
|
|
175
|
+
| Level | Criteria |
|
|
176
|
+
|--------|----------|
|
|
177
|
+
| 0 | No classification. No distinction between public and confidential data. PII not identified. |
|
|
178
|
+
| 1 | Informal classification of a few datasets. Ad-hoc masking. No automatic PII detection. |
|
|
179
|
+
| 2 | Documented classification policy with defined levels. PII identified and inventoried. Masking in place for test environments. |
|
|
180
|
+
| 3 | Systematic classification integrated into the catalog. Automatic PII detection. Dynamic masking. Aligned access controls. Regular audits. |
|
|
181
|
+
| 4 | Automatic classification via ML. Data masking as a service. Tokenization for real-time streams. Compliance dashboard. Proactive detection of undeclared sensitive data. |
|
|
182
|
+
|
|
183
|
+
---
|
|
184
|
+
|
|
185
|
+
### DG-07 - Retention policies and data lifecycle - Criticality: **MUST**
|
|
186
|
+
|
|
187
|
+
**Analyze:** Lifecycle policy, archiving, irreversible deletion, tiered storage
|
|
188
|
+
|
|
189
|
+
**Verification commands:**
|
|
190
|
+
```bash
|
|
191
|
+
grep -ri "lifecycle\|retention\|archiv\|ttl\|expire\|cold.storage\|tiered" . --include="*.ts" --include="*.rs" --include="*.yml" --include="*.yaml" --include="*.tf" 2>/dev/null | head -10
|
|
192
|
+
grep -ri "legal.hold\|gel.judiciaire\|retention.as.code" . --include="*.md" --include="*.yml" 2>/dev/null | head -5
|
|
193
|
+
```
|
|
194
|
+
|
|
195
|
+
**Check:**
|
|
196
|
+
- Retention policy per data category
|
|
197
|
+
- Retention durations aligned with legal obligations
|
|
198
|
+
- Automated archiving
|
|
199
|
+
- Right to erasure propagated to processors
|
|
200
|
+
- Certified deletion evidence
|
|
201
|
+
- Versioned retention-as-code
|
|
202
|
+
|
|
203
|
+
**Levels:**
|
|
204
|
+
| Level | Criteria |
|
|
205
|
+
|--------|----------|
|
|
206
|
+
| 0 | No retention policy. Data kept indefinitely. Right to erasure not implemented. |
|
|
207
|
+
| 1 | Informal policy. Occasional manual purges. Right to erasure case by case. |
|
|
208
|
+
| 2 | Documented policy per data category. Defined durations. Formalized right-to-erasure process. |
|
|
209
|
+
| 3 | Automated retention with TTL. Right-to-erasure workflow integrated with dependent systems. Legal hold supported. Deletion evidence. |
|
|
210
|
+
| 4 | Fully automated lifecycle management. Cost-optimized tiered storage. Right to erasure propagated to processors. Certified audit trail. Versioned retention-as-code. |
|
|
211
|
+
|
|
212
|
+
---
|
|
213
|
+
|
|
214
|
+
### DG-08 - Data architecture and topology (Data Mesh) - Criticality: **SHOULD**
|
|
215
|
+
|
|
216
|
+
**Analyze:** Data organization, data domains, data products, self-service platform
|
|
217
|
+
|
|
218
|
+
**Verification commands:**
|
|
219
|
+
```bash
|
|
220
|
+
grep -ri "data.mesh\|data.product\|data.domain\|data.platform\|federated.governance" . --include="*.md" --include="*.yml" 2>/dev/null | head -10
|
|
221
|
+
grep -ri "data.warehouse\|data.lake\|lakehouse\|dbt\|airflow\|dagster" . --include="*.yml" --include="*.yaml" --include="*.py" 2>/dev/null | head -10
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
**Check:**
|
|
225
|
+
- Data architecture defined and documented
|
|
226
|
+
- Data domains identified with ownership
|
|
227
|
+
- Data products with documentation and SLA
|
|
228
|
+
- Self-service platform for ingestion/transformation/publication
|
|
229
|
+
- Federated governance (policies as code)
|
|
230
|
+
|
|
231
|
+
**Levels:**
|
|
232
|
+
| Level | Criteria |
|
|
233
|
+
|--------|----------|
|
|
234
|
+
| 0 | No data architecture defined. Isolated silos. Each team manages independently. |
|
|
235
|
+
| 1 | Implicit architecture centered on a single data warehouse/lake. Overloaded centralized data team. |
|
|
236
|
+
| 2 | Documented architecture with identified data zones. Domains defined. First data-product initiatives. |
|
|
237
|
+
| 3 | Data Mesh or federated architecture in place. Data products with domain owners. Self-serve platform. Federated governance. |
|
|
238
|
+
| 4 | Mature Data Mesh with a marketplace of data products. Automated computational governance (policies as code). Measured cross-domain interoperability. Consumer-producer feedback loop. |
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
# `audit-industrialisation`
|
|
2
|
+
|
|
3
|
+
> Orchestrate a full, evidence-based audit of a project's software-engineering maturity: profile the project, run 8 domain audits in parallel, and consolidate a single scored report.
|
|
4
|
+
|
|
5
|
+
| | |
|
|
6
|
+
|---|---|
|
|
7
|
+
| **Type** | Skill (orchestrator workflow) |
|
|
8
|
+
| **Category** | `audit` |
|
|
9
|
+
| **Artifact** | [`SKILL.md`](SKILL.md) |
|
|
10
|
+
| **Tooling** | Subagents (Agent tool), shell detection commands; no bespoke script |
|
|
11
|
+
|
|
12
|
+
## What it is
|
|
13
|
+
|
|
14
|
+
`audit-industrialisation` is the **entry point** for a complete maturity audit. It does not carry the questions itself - those live in the eight domain skills (`audit-ci-cd`, `audit-testing`, `audit-security`, `audit-observability`, `audit-architecture`, `audit-quality`, `audit-compliance`, `audit-performance-frontend`). Its job is to **profile** the project once, **fan out** the eight audits as parallel subagents, then **consolidate** their results into one weighted, classified report.
|
|
15
|
+
|
|
16
|
+
The reference model is **214 questions across 18 sections and 8 domains**, each question scored on a 0-4 maturity scale (CMMI-adapted) or marked N/A.
|
|
17
|
+
|
|
18
|
+
## Why it exists
|
|
19
|
+
|
|
20
|
+
Running eight audits by hand is slow and inconsistent: each agent rediscovers the stack, questions get re-worded, IDs drift, and the final scores are impossible to compare across runs. The orchestrator fixes three things:
|
|
21
|
+
|
|
22
|
+
- **One shared profile.** The project is detected and described once, then that block is pasted into every subagent prompt - no agent re-derives the framework, database or CI system.
|
|
23
|
+
- **Stable IDs and stable weights.** Question IDs (`ci-01`, `te-09a`…) and the domain weight table are identical everywhere, so two audits of the same project are comparable.
|
|
24
|
+
- **Evidence over opinion.** Every level must rest on a captured command output, a source excerpt, or a document quote - or the question is marked non-auditable. No blind scoring.
|
|
25
|
+
|
|
26
|
+
## When it triggers
|
|
27
|
+
|
|
28
|
+
Invoke it for a **global, multi-domain** assessment - phrases like "industrialisation audit", "full audit", "project audit", "maturity audit", "global audit".
|
|
29
|
+
|
|
30
|
+
- Use a **single `audit-<domain>`** instead when the scope is one domain (e.g. just security).
|
|
31
|
+
- `audit-report` is used **inside** this skill (Phase 3) for the scoring rules and report template - it is not a competitor.
|
|
32
|
+
|
|
33
|
+
## How it works
|
|
34
|
+
|
|
35
|
+
The orchestrator runs in four phases. It first profiles the project once (detection commands + a relevance matrix that marks domains N/A by project type), then fans the 8 domain audits out as parallel subagents, each handed that shared profile and returning a mandatory per-question table plus recommendations. Phase 3 consolidates: domain scores are means (N/A excluded), the global score is a weighted mean (Security ×1.5, Testing ×1.2, Frontend Perf ×0.8, others ×1.0), a CMMI-style classification is assigned, and recommendations are prioritised and grouped into a dated action plan saved to `docs/audit/YYYY-MM-DD-audit-industrialisation.md`. Throughout, every level must rest on captured evidence (`code_analysis` / `technical_test` / `document`) rather than opinion.
|
|
36
|
+
|
|
37
|
+
Full phase-by-phase protocol, subagent prompt template, weight and classification tables → [`SKILL.md`](SKILL.md).
|
|
38
|
+
|
|
39
|
+
## Worked example
|
|
40
|
+
|
|
41
|
+
> You run a full audit on `acme-app`, a fullstack TypeScript app with GitLab CI and PostgreSQL.
|
|
42
|
+
|
|
43
|
+
1. Phase 1 detects the stack and produces the profile block; the relevance matrix keeps all 8 domains ("adapted" for Frontend Perf).
|
|
44
|
+
2. Phase 2 fans out 8 subagents. `audit-security` scores `se-04` (secrets management) at level 1 with high confidence, citing a hard-coded token found by grep.
|
|
45
|
+
3. Phase 3 computes a global score of, say, 2.3/4 - **Defined** - and lifts the hard-coded secret to an immediate MUST at the top of the plan.
|
|
46
|
+
4. The report lands in `docs/audit/2026-07-10-audit-industrialisation.md`, every level cited with evidence.
|
|
47
|
+
|
|
48
|
+
Scoping to `$ARGUMENTS = security testing` would run only those two domains and adapt the report to that scope.
|
|
49
|
+
|
|
50
|
+
## Related artifacts
|
|
51
|
+
|
|
52
|
+
- [`audit-report`](../audit-report/) - the scoring rules and report template used in Phase 3 (and usable standalone).
|
|
53
|
+
- [`audit-quality`](../audit-quality/), [`audit-security`](../audit-security/), [`audit-testing`](../audit-testing/), and the other five `audit-*` skills - the domains this orchestrator fans out to.
|