@jetrabbits/agentic 0.3.3 → 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 +8 -0
- package/CHANGELOG.md +18 -0
- package/Makefile +26 -5
- package/README.md +25 -6
- package/agentic +801 -66
- package/areas/devops/ci-cd/workflows/onboard-repo.md +29 -0
- package/areas/devops/ci-cd/workflows/pipeline-debug.md +26 -0
- package/areas/devops/ci-cd/workflows/release-pipeline.md +53 -0
- package/areas/devops/database-ops/workflows/backup-verify.md +27 -0
- package/areas/devops/database-ops/workflows/db-incident.md +30 -0
- package/areas/devops/devsecops/workflows/policy-onboard.md +34 -0
- package/areas/devops/devsecops/workflows/security-scan-pipeline.md +33 -0
- package/areas/devops/infrastructure/workflows/destroy-environment.md +31 -0
- package/areas/devops/infrastructure/workflows/drift-remediation.md +29 -0
- package/areas/devops/infrastructure/workflows/module-development.md +32 -0
- package/areas/devops/infrastructure/workflows/provision-environment.md +29 -0
- package/areas/devops/kubernetes/workflows/cluster-bootstrap.md +36 -0
- package/areas/devops/kubernetes/workflows/debug-workload.md +29 -0
- package/areas/devops/kubernetes/workflows/onboard-service.md +35 -0
- package/areas/devops/kubernetes/workflows/upgrade-cluster.md +30 -0
- package/areas/devops/networking/workflows/onboard-ingress.md +27 -0
- package/areas/devops/networking/workflows/service-mesh-onboard.md +27 -0
- package/areas/devops/observability/workflows/alert-investigation.md +29 -0
- package/areas/devops/observability/workflows/observability-stack-setup.md +33 -0
- package/areas/devops/observability/workflows/onboard-service-monitoring.md +31 -0
- package/areas/devops/sre/workflows/incident-response.md +48 -0
- package/areas/devops/sre/workflows/postmortem.md +32 -0
- package/areas/devops/sre/workflows/slo-review.md +35 -1
- package/areas/software/backend/workflows/add-migration.md +33 -0
- package/areas/software/backend/workflows/create-endpoint.md +40 -0
- package/areas/software/backend/workflows/debug-issue.md +31 -0
- package/areas/software/backend/workflows/develop-epic.md +37 -0
- package/areas/software/backend/workflows/develop-feature.md +44 -0
- package/areas/software/backend/workflows/refactor-module.md +35 -0
- package/areas/software/backend/workflows/test-feature.md +30 -0
- package/areas/software/data-engineering/workflows/backfill-data.md +25 -0
- package/areas/software/data-engineering/workflows/data-quality-incident.md +31 -0
- package/areas/software/data-engineering/workflows/lineage-trace.md +25 -0
- package/areas/software/data-engineering/workflows/new-model.md +30 -0
- package/areas/software/data-engineering/workflows/schema-migration.md +29 -0
- package/areas/software/frontend/workflows/a11y-fix.md +30 -0
- package/areas/software/frontend/workflows/bundle-analyze.md +28 -0
- package/areas/software/frontend/workflows/release-prep.md +33 -0
- package/areas/software/frontend/workflows/scaffold-component.md +32 -0
- package/areas/software/frontend/workflows/visual-regression.md +32 -0
- package/areas/software/full-stack/workflows/backend-project-full-cycle.md +47 -2
- package/areas/software/full-stack/workflows/debug-issue.md +29 -0
- package/areas/software/full-stack/workflows/develop-feature.md +38 -0
- package/areas/software/full-stack/workflows/feature-implementation-flow.md +38 -0
- package/areas/software/full-stack/workflows/testing-ci-pipeline.md +30 -0
- package/areas/software/general/workflows/code-review-workflow.md +31 -0
- package/areas/software/general/workflows/development-cycle-workflow.md +38 -0
- package/areas/software/general/workflows/project-setup-workflow.md +38 -0
- package/areas/software/mlops/workflows/champion-challenger.md +29 -0
- package/areas/software/mlops/workflows/deploy-endpoint.md +30 -0
- package/areas/software/mlops/workflows/evaluate-model.md +28 -0
- package/areas/software/mlops/workflows/model-incident.md +29 -0
- package/areas/software/mlops/workflows/train-experiment.md +25 -0
- package/areas/software/mobile/workflows/crash-triage.md +28 -0
- package/areas/software/mobile/workflows/device-testing.md +27 -0
- package/areas/software/mobile/workflows/ota-update.md +25 -0
- package/areas/software/mobile/workflows/release-build.md +30 -0
- package/areas/software/mobile/workflows/store-submission.md +29 -0
- package/areas/software/platform/workflows/cost-audit.md +28 -0
- package/areas/software/platform/workflows/deploy-production.md +30 -0
- package/areas/software/platform/workflows/drift-check.md +29 -0
- package/areas/software/platform/workflows/incident-response.md +33 -0
- package/areas/software/platform/workflows/provision-env.md +36 -0
- package/areas/software/qa/workflows/flakiness-investigation.md +30 -0
- package/areas/software/qa/workflows/performance-audit.md +29 -0
- package/areas/software/qa/workflows/regression-suite.md +28 -0
- package/areas/software/qa/workflows/smoke-test.md +31 -0
- package/areas/software/qa/workflows/test-coverage-report.md +28 -0
- package/areas/software/security/workflows/compliance-report.md +27 -0
- package/areas/software/security/workflows/pen-test-sim.md +28 -0
- package/areas/software/security/workflows/secret-rotation.md +33 -2
- package/areas/software/security/workflows/security-scan.md +29 -0
- package/areas/software/security/workflows/threat-model-review.md +30 -0
- package/docs/agentic-usage.md +19 -2
- package/docs/catalog.schema.json +5 -1
- package/docs/mcp/README.md +28 -0
- package/docs/opencode_setup.md +21 -1
- package/docs/site/README.md +15 -1
- package/docs/site/app.js +68 -0
- package/docs/site/catalog.json +74 -1
- package/docs/site/index.html +5 -1
- package/docs/site/styles.css +52 -4
- package/extensions/opencode/opencode.json +0 -1
- package/extensions/opencode/profiles/githubcopilot/opencode.json +87 -0
- package/extensions/opencode/profiles/openai/opencode.json +100 -0
- package/package.json +1 -1
- package/scripts/build_docs_catalog.py +13 -1
- package/scripts/sync_workflow_diagrams.py +199 -0
- package/extensions/opencode/plugins/sound-notification.ts +0 -13
|
@@ -152,5 +152,38 @@ for dashboard in infra/observability/dashboards/*.json; do
|
|
|
152
152
|
done
|
|
153
153
|
```
|
|
154
154
|
|
|
155
|
+
## Agent Interaction Diagram
|
|
156
|
+
|
|
157
|
+
<!-- agent-diagram:start -->
|
|
158
|
+
```mermaid
|
|
159
|
+
flowchart TD
|
|
160
|
+
start(["Start /observability-stack-setup"])
|
|
161
|
+
role_1["devops-engineer"]
|
|
162
|
+
step_1["1. Namespace & Prerequisites"]
|
|
163
|
+
step_2["2. kube-prometheus-stack (Prometheus + Grafana + Alertmanager)"]
|
|
164
|
+
step_3["3. Loki + Promtail (Logs)"]
|
|
165
|
+
step_4["4. Tempo (Traces)"]
|
|
166
|
+
step_5["5. OpenTelemetry Collector (DaemonSet)"]
|
|
167
|
+
step_6["6. Validate Stack"]
|
|
168
|
+
step_7["7. Import Dashboards"]
|
|
169
|
+
exit(["All 4 components healthy + test alert fired + dashboards showing data = sta..."])
|
|
170
|
+
start --> step_1
|
|
171
|
+
step_1 --> step_2
|
|
172
|
+
step_2 --> step_3
|
|
173
|
+
step_3 --> step_4
|
|
174
|
+
step_4 --> step_5
|
|
175
|
+
step_5 --> step_6
|
|
176
|
+
step_6 --> step_7
|
|
177
|
+
step_7 --> exit
|
|
178
|
+
role_1 -. owns .-> step_1
|
|
179
|
+
role_1 -. owns .-> step_2
|
|
180
|
+
role_1 -. owns .-> step_3
|
|
181
|
+
role_1 -. owns .-> step_4
|
|
182
|
+
role_1 -. owns .-> step_5
|
|
183
|
+
role_1 -. owns .-> step_6
|
|
184
|
+
role_1 -. owns .-> step_7
|
|
185
|
+
```
|
|
186
|
+
<!-- agent-diagram:end -->
|
|
187
|
+
|
|
155
188
|
## Exit
|
|
156
189
|
All 4 components healthy + test alert fired + dashboards showing data = stack deployed.
|
|
@@ -79,5 +79,36 @@ spec:
|
|
|
79
79
|
- Link trace panel (Tempo datasource) to request duration panel
|
|
80
80
|
- **Done when:** dashboard saved in `infra/dashboards/`; Grafana shows live data
|
|
81
81
|
|
|
82
|
+
## Agent Interaction Diagram
|
|
83
|
+
|
|
84
|
+
<!-- agent-diagram:start -->
|
|
85
|
+
```mermaid
|
|
86
|
+
flowchart TD
|
|
87
|
+
start(["Start /onboard-service-monitoring"])
|
|
88
|
+
role_1["developer"]
|
|
89
|
+
role_2["devops-engineer"]
|
|
90
|
+
step_1["1. Metrics Instrumentation"]
|
|
91
|
+
step_2["2. ServiceMonitor"]
|
|
92
|
+
step_3["3. Tracing Instrumentation"]
|
|
93
|
+
step_4["4. Log Labels"]
|
|
94
|
+
step_5["5. Alert Rules"]
|
|
95
|
+
step_6["6. Grafana Dashboard"]
|
|
96
|
+
exit(["Golden signals in Prometheus + logs in Loki + traces in Tempo + alerts depl..."])
|
|
97
|
+
start --> step_1
|
|
98
|
+
step_1 --> step_2
|
|
99
|
+
step_2 --> step_3
|
|
100
|
+
step_3 --> step_4
|
|
101
|
+
step_4 --> step_5
|
|
102
|
+
step_5 --> step_6
|
|
103
|
+
step_6 --> exit
|
|
104
|
+
role_1 -. owns .-> step_1
|
|
105
|
+
role_2 -. owns .-> step_2
|
|
106
|
+
role_1 -. owns .-> step_3
|
|
107
|
+
role_2 -. owns .-> step_4
|
|
108
|
+
role_2 -. owns .-> step_5
|
|
109
|
+
role_2 -. owns .-> step_6
|
|
110
|
+
```
|
|
111
|
+
<!-- agent-diagram:end -->
|
|
112
|
+
|
|
82
113
|
## Exit
|
|
83
114
|
Golden signals in Prometheus + logs in Loki + traces in Tempo + alerts deployed + dashboard live = service monitored.
|
|
@@ -62,5 +62,53 @@ quality-gates:
|
|
|
62
62
|
- Define action items with owners and due dates
|
|
63
63
|
- Publish to team wiki; announce in #postmortems
|
|
64
64
|
|
|
65
|
+
## Agent Interaction Diagram
|
|
66
|
+
|
|
67
|
+
<!-- agent-diagram:start -->
|
|
68
|
+
```mermaid
|
|
69
|
+
flowchart TD
|
|
70
|
+
start(["Start /incident-response"])
|
|
71
|
+
role_1["devops-engineer"]
|
|
72
|
+
role_2["developer"]
|
|
73
|
+
role_3["pm"]
|
|
74
|
+
role_4["devops-engineer (IC)"]
|
|
75
|
+
role_5["developer (technical lead)"]
|
|
76
|
+
role_6["pm (comms)"]
|
|
77
|
+
step_1["T+0–5: Acknowledge & Scope"]
|
|
78
|
+
step_2["T+5–15: Mitigate"]
|
|
79
|
+
step_3["T+10: Communicate"]
|
|
80
|
+
step_4["T+15–30: Stabilize"]
|
|
81
|
+
step_5["T+30: Resolve or Escalate"]
|
|
82
|
+
step_6["T+60: Preliminary Postmortem"]
|
|
83
|
+
step_7["T+24h: Full Postmortem"]
|
|
84
|
+
exit(["Service healthy + stakeholders informed + postmortem published = incident c..."])
|
|
85
|
+
start --> step_1
|
|
86
|
+
step_1 --> step_2
|
|
87
|
+
step_2 --> step_3
|
|
88
|
+
step_3 --> step_4
|
|
89
|
+
step_4 --> step_5
|
|
90
|
+
step_5 --> step_6
|
|
91
|
+
step_6 --> step_7
|
|
92
|
+
step_7 --> exit
|
|
93
|
+
role_1 -. owns .-> step_1
|
|
94
|
+
role_2 -. owns .-> step_2
|
|
95
|
+
role_1 -. owns .-> step_2
|
|
96
|
+
role_3 -. owns .-> step_3
|
|
97
|
+
role_1 -. owns .-> step_4
|
|
98
|
+
role_2 -. owns .-> step_5
|
|
99
|
+
role_4 -. owns .-> step_5
|
|
100
|
+
role_5 -. owns .-> step_5
|
|
101
|
+
role_6 -. owns .-> step_5
|
|
102
|
+
role_2 -. owns .-> step_6
|
|
103
|
+
role_4 -. owns .-> step_6
|
|
104
|
+
role_5 -. owns .-> step_6
|
|
105
|
+
role_6 -. owns .-> step_6
|
|
106
|
+
role_2 -. owns .-> step_7
|
|
107
|
+
role_4 -. owns .-> step_7
|
|
108
|
+
role_5 -. owns .-> step_7
|
|
109
|
+
role_6 -. owns .-> step_7
|
|
110
|
+
```
|
|
111
|
+
<!-- agent-diagram:end -->
|
|
112
|
+
|
|
65
113
|
## Exit
|
|
66
114
|
Service healthy + stakeholders informed + postmortem published = incident closed.
|
|
@@ -86,5 +86,37 @@ done
|
|
|
86
86
|
- Any blocked items? Need resource allocation?
|
|
87
87
|
- If root cause not addressed: escalate to engineering lead
|
|
88
88
|
|
|
89
|
+
## Agent Interaction Diagram
|
|
90
|
+
|
|
91
|
+
<!-- agent-diagram:start -->
|
|
92
|
+
```mermaid
|
|
93
|
+
flowchart TD
|
|
94
|
+
start(["Start /postmortem"])
|
|
95
|
+
role_1["devops-engineer"]
|
|
96
|
+
role_2["team-lead"]
|
|
97
|
+
step_1["1. Collect Data (within 2h of resolution)"]
|
|
98
|
+
step_2["2. Draft Postmortem"]
|
|
99
|
+
step_3["3. 5-Whys Facilitation Meeting (within 48h)"]
|
|
100
|
+
step_4["4. Finalize Document"]
|
|
101
|
+
step_5["5. Publish & Track"]
|
|
102
|
+
step_6["6. Follow-Up (2 weeks later)"]
|
|
103
|
+
exit(["Postmortem published + all action items in tracker + team notified = postmo..."])
|
|
104
|
+
start --> step_1
|
|
105
|
+
step_1 --> step_2
|
|
106
|
+
step_2 --> step_3
|
|
107
|
+
step_3 --> step_4
|
|
108
|
+
step_4 --> step_5
|
|
109
|
+
step_5 --> step_6
|
|
110
|
+
step_6 --> exit
|
|
111
|
+
role_1 -. owns .-> step_1
|
|
112
|
+
role_1 -. owns .-> step_2
|
|
113
|
+
role_1 -. owns .-> step_3
|
|
114
|
+
role_1 -. owns .-> step_4
|
|
115
|
+
role_1 -. owns .-> step_5
|
|
116
|
+
role_2 -. owns .-> step_5
|
|
117
|
+
role_2 -. owns .-> step_6
|
|
118
|
+
```
|
|
119
|
+
<!-- agent-diagram:end -->
|
|
120
|
+
|
|
89
121
|
## Exit
|
|
90
122
|
Postmortem published + all action items in tracker + team notified = postmortem complete.
|
|
@@ -21,7 +21,6 @@ related-rules:
|
|
|
21
21
|
- error-budget-policy.md
|
|
22
22
|
uses-skills:
|
|
23
23
|
- slo-sli-design
|
|
24
|
-
- slo-implementation
|
|
25
24
|
- capacity-planning
|
|
26
25
|
quality-gates:
|
|
27
26
|
- SLO targets grounded in actual reliability data (not aspirational)
|
|
@@ -91,5 +90,40 @@ kubectl apply -f rules/slo-${SERVICE}-generated.yaml -n monitoring
|
|
|
91
90
|
- notify: tighten SLO to 99.3%; generates meaningful error budget
|
|
92
91
|
```
|
|
93
92
|
|
|
93
|
+
## Agent Interaction Diagram
|
|
94
|
+
|
|
95
|
+
<!-- agent-diagram:start -->
|
|
96
|
+
```mermaid
|
|
97
|
+
flowchart TD
|
|
98
|
+
start(["Start /slo-review"])
|
|
99
|
+
role_1["devops-engineer"]
|
|
100
|
+
role_2["team-lead"]
|
|
101
|
+
role_3["product-owner"]
|
|
102
|
+
step_1["1. Pull Reliability Data"]
|
|
103
|
+
step_2["2. Classify Services"]
|
|
104
|
+
step_3["3. SLO Adjustment Workshop"]
|
|
105
|
+
step_4["4. Update SLO Definitions"]
|
|
106
|
+
step_5["5. Error Budget Policy Review"]
|
|
107
|
+
step_6["6. Publish SLO Review Report"]
|
|
108
|
+
exit(["Report published + SLO changes applied + action items in tracker = review c..."])
|
|
109
|
+
start --> step_1
|
|
110
|
+
step_1 --> step_2
|
|
111
|
+
step_2 --> step_3
|
|
112
|
+
step_3 --> step_4
|
|
113
|
+
step_4 --> step_5
|
|
114
|
+
step_5 --> step_6
|
|
115
|
+
step_6 --> exit
|
|
116
|
+
role_1 -. owns .-> step_1
|
|
117
|
+
role_1 -. owns .-> step_2
|
|
118
|
+
role_1 -. owns .-> step_3
|
|
119
|
+
role_2 -. owns .-> step_3
|
|
120
|
+
role_3 -. owns .-> step_3
|
|
121
|
+
role_1 -. owns .-> step_4
|
|
122
|
+
role_2 -. owns .-> step_5
|
|
123
|
+
role_3 -. owns .-> step_5
|
|
124
|
+
role_1 -. owns .-> step_6
|
|
125
|
+
```
|
|
126
|
+
<!-- agent-diagram:end -->
|
|
127
|
+
|
|
94
128
|
## Exit
|
|
95
129
|
Report published + SLO changes applied + action items in tracker = review complete.
|
|
@@ -72,6 +72,39 @@ quality-gates:
|
|
|
72
72
|
- **Output:** `migration_readiness.md` with deployment steps, rollback command, monitoring checklist
|
|
73
73
|
- **Done when:** ops/release team has everything needed to deploy safely
|
|
74
74
|
|
|
75
|
+
## Agent Interaction Diagram
|
|
76
|
+
|
|
77
|
+
<!-- agent-diagram:start -->
|
|
78
|
+
```mermaid
|
|
79
|
+
flowchart TD
|
|
80
|
+
start(["Start /add-migration"])
|
|
81
|
+
role_1["team-lead"]
|
|
82
|
+
role_2["developer"]
|
|
83
|
+
role_3["qa"]
|
|
84
|
+
role_4["pm"]
|
|
85
|
+
step_1["1. Risk & Compatibility Analysis"]
|
|
86
|
+
step_2["2. Migration Implementation"]
|
|
87
|
+
step_3["3. Test DB Validation & Data Checks"]
|
|
88
|
+
step_4["4. Review & Remediation Loop"]
|
|
89
|
+
step_5["5. Readiness Report"]
|
|
90
|
+
exit(["Validated migration + readiness report + @team-lead approval = ready to dep..."])
|
|
91
|
+
start --> step_1
|
|
92
|
+
step_1 --> step_2
|
|
93
|
+
step_2 --> step_3
|
|
94
|
+
step_3 --> step_4
|
|
95
|
+
step_4 --> step_5
|
|
96
|
+
step_5 --> exit
|
|
97
|
+
role_1 -. owns .-> step_1
|
|
98
|
+
role_2 -. owns .-> step_2
|
|
99
|
+
role_3 -. owns .-> step_3
|
|
100
|
+
role_1 -. owns .-> step_4
|
|
101
|
+
role_2 -. owns .-> step_4
|
|
102
|
+
role_4 -. owns .-> step_5
|
|
103
|
+
role_1 -. owns .-> step_5
|
|
104
|
+
step_5 -. iterate if blocked .-> step_1
|
|
105
|
+
```
|
|
106
|
+
<!-- agent-diagram:end -->
|
|
107
|
+
|
|
75
108
|
## Iteration Loop
|
|
76
109
|
If validation reveals data issues or compatibility risks → return to Step 1 for strategy revision.
|
|
77
110
|
|
|
@@ -85,5 +85,45 @@ quality-gates:
|
|
|
85
85
|
- **Output:** endpoint accepted; delivery note in `docs/<feature>/delivery_summary.md`
|
|
86
86
|
- **Done when:** `@product-owner` signs off
|
|
87
87
|
|
|
88
|
+
## Agent Interaction Diagram
|
|
89
|
+
|
|
90
|
+
<!-- agent-diagram:start -->
|
|
91
|
+
```mermaid
|
|
92
|
+
flowchart TD
|
|
93
|
+
start(["Start /create-endpoint"])
|
|
94
|
+
role_1["product-owner"]
|
|
95
|
+
role_2["pm"]
|
|
96
|
+
role_3["team-lead"]
|
|
97
|
+
role_4["developer"]
|
|
98
|
+
role_5["qa"]
|
|
99
|
+
step_1["1. Scope & Contract"]
|
|
100
|
+
step_2["2. Architecture Review"]
|
|
101
|
+
step_3["3. Implementation"]
|
|
102
|
+
step_4["4. Test Design & Execution"]
|
|
103
|
+
step_5["5. Code Review & Sign-off"]
|
|
104
|
+
step_6["6. Fix / Retest Loop"]
|
|
105
|
+
step_7["7. Acceptance"]
|
|
106
|
+
exit(["Accepted endpoint + passing tests + @team-lead sign-off = ready to merge."])
|
|
107
|
+
start --> step_1
|
|
108
|
+
step_1 --> step_2
|
|
109
|
+
step_2 --> step_3
|
|
110
|
+
step_3 --> step_4
|
|
111
|
+
step_4 --> step_5
|
|
112
|
+
step_5 --> step_6
|
|
113
|
+
step_6 --> step_7
|
|
114
|
+
step_7 --> exit
|
|
115
|
+
role_1 -. owns .-> step_1
|
|
116
|
+
role_2 -. owns .-> step_1
|
|
117
|
+
role_3 -. owns .-> step_2
|
|
118
|
+
role_4 -. owns .-> step_3
|
|
119
|
+
role_5 -. owns .-> step_4
|
|
120
|
+
role_3 -. owns .-> step_5
|
|
121
|
+
role_4 -. owns .-> step_6
|
|
122
|
+
role_5 -. owns .-> step_6
|
|
123
|
+
role_1 -. owns .-> step_7
|
|
124
|
+
role_2 -. owns .-> step_7
|
|
125
|
+
```
|
|
126
|
+
<!-- agent-diagram:end -->
|
|
127
|
+
|
|
88
128
|
## Exit
|
|
89
129
|
Accepted endpoint + passing tests + `@team-lead` sign-off = ready to merge.
|
|
@@ -73,5 +73,36 @@ quality-gates:
|
|
|
73
73
|
- **Output:** `root_cause_summary.md` — what failed, why, how fixed, how to prevent
|
|
74
74
|
- **Done when:** `@team-lead` approves fix; root cause documented; ticket closed
|
|
75
75
|
|
|
76
|
+
## Agent Interaction Diagram
|
|
77
|
+
|
|
78
|
+
<!-- agent-diagram:start -->
|
|
79
|
+
```mermaid
|
|
80
|
+
flowchart TD
|
|
81
|
+
start(["Start /debug-issue"])
|
|
82
|
+
role_1["pm"]
|
|
83
|
+
role_2["team-lead"]
|
|
84
|
+
role_3["developer"]
|
|
85
|
+
role_4["qa"]
|
|
86
|
+
step_1["1. Triage & Impact Classification"]
|
|
87
|
+
step_2["2. Reproduce & Isolate"]
|
|
88
|
+
step_3["3. Fix Implementation"]
|
|
89
|
+
step_4["4. Verification & Regression Checks"]
|
|
90
|
+
step_5["5. Technical Review & Closure"]
|
|
91
|
+
exit(["Merged fix + verified resolution + root cause documented = incident closed."])
|
|
92
|
+
start --> step_1
|
|
93
|
+
step_1 --> step_2
|
|
94
|
+
step_2 --> step_3
|
|
95
|
+
step_3 --> step_4
|
|
96
|
+
step_4 --> step_5
|
|
97
|
+
step_5 --> exit
|
|
98
|
+
role_1 -. owns .-> step_1
|
|
99
|
+
role_2 -. owns .-> step_1
|
|
100
|
+
role_3 -. owns .-> step_2
|
|
101
|
+
role_3 -. owns .-> step_3
|
|
102
|
+
role_4 -. owns .-> step_4
|
|
103
|
+
role_2 -. owns .-> step_5
|
|
104
|
+
```
|
|
105
|
+
<!-- agent-diagram:end -->
|
|
106
|
+
|
|
76
107
|
## Exit
|
|
77
108
|
Merged fix + verified resolution + root cause documented = incident closed.
|
|
@@ -71,6 +71,43 @@ quality-gates:
|
|
|
71
71
|
- **Output:** `docs/<epic>/delivery_summary.md` — accepted items, deferred items, follow-up backlog
|
|
72
72
|
- **Done when:** epic accepted; follow-up items logged
|
|
73
73
|
|
|
74
|
+
## Agent Interaction Diagram
|
|
75
|
+
|
|
76
|
+
<!-- agent-diagram:start -->
|
|
77
|
+
```mermaid
|
|
78
|
+
flowchart TD
|
|
79
|
+
start(["Start /develop-epic"])
|
|
80
|
+
role_1["product-owner"]
|
|
81
|
+
role_2["pm"]
|
|
82
|
+
role_3["team-lead"]
|
|
83
|
+
role_4["developer"]
|
|
84
|
+
role_5["qa"]
|
|
85
|
+
step_1["1. Epic Decomposition & Milestone Planning"]
|
|
86
|
+
step_2["2. Architecture Runway Definition"]
|
|
87
|
+
step_3["3. Increment Implementation"]
|
|
88
|
+
step_4["4. Increment Verification"]
|
|
89
|
+
step_5["5. Milestone Review & Replanning"]
|
|
90
|
+
step_6["6. Final Acceptance"]
|
|
91
|
+
exit(["All increments accepted by @product-owner + clean regression suite = epic d..."])
|
|
92
|
+
start --> step_1
|
|
93
|
+
step_1 --> step_2
|
|
94
|
+
step_2 --> step_3
|
|
95
|
+
step_3 --> step_4
|
|
96
|
+
step_4 --> step_5
|
|
97
|
+
step_5 --> step_6
|
|
98
|
+
step_6 --> exit
|
|
99
|
+
role_1 -. owns .-> step_1
|
|
100
|
+
role_2 -. owns .-> step_1
|
|
101
|
+
role_3 -. owns .-> step_2
|
|
102
|
+
role_4 -. owns .-> step_3
|
|
103
|
+
role_5 -. owns .-> step_4
|
|
104
|
+
role_2 -. owns .-> step_5
|
|
105
|
+
role_3 -. owns .-> step_5
|
|
106
|
+
role_1 -. owns .-> step_6
|
|
107
|
+
step_6 -. iterate if blocked .-> step_1
|
|
108
|
+
```
|
|
109
|
+
<!-- agent-diagram:end -->
|
|
110
|
+
|
|
74
111
|
## Iteration Loop
|
|
75
112
|
Steps 3–5 repeat for each increment. Replanning in Step 5 governs scope adjustments.
|
|
76
113
|
|
|
@@ -85,6 +85,50 @@ quality-gates:
|
|
|
85
85
|
- **Output:** `docs/<feature>/delivery_summary.md` — accepted / deferred with rationale
|
|
86
86
|
- **Done when:** feature accepted or explicitly deferred
|
|
87
87
|
|
|
88
|
+
## Agent Interaction Diagram
|
|
89
|
+
|
|
90
|
+
<!-- agent-diagram:start -->
|
|
91
|
+
```mermaid
|
|
92
|
+
flowchart TD
|
|
93
|
+
start(["Start /develop-feature"])
|
|
94
|
+
role_1["product-owner"]
|
|
95
|
+
role_2["pm"]
|
|
96
|
+
role_3["team-lead"]
|
|
97
|
+
role_4["designer"]
|
|
98
|
+
role_5["developer"]
|
|
99
|
+
role_6["qa"]
|
|
100
|
+
step_1["1. Requirements & Value Framing"]
|
|
101
|
+
step_2["2. Solution Design & Risk Plan"]
|
|
102
|
+
step_3["3. Implementation"]
|
|
103
|
+
step_4["4. Risk-Based Verification"]
|
|
104
|
+
step_5["5. Code Review & Architecture Sign-off"]
|
|
105
|
+
step_6["6. Fix / Retest Loop"]
|
|
106
|
+
step_7["7. Acceptance & Final Report"]
|
|
107
|
+
exit(["@product-owner acceptance + no unresolved blockers = feature complete and r..."])
|
|
108
|
+
start --> step_1
|
|
109
|
+
step_1 --> step_2
|
|
110
|
+
step_2 --> step_3
|
|
111
|
+
step_3 --> step_4
|
|
112
|
+
step_4 --> step_5
|
|
113
|
+
step_5 --> step_6
|
|
114
|
+
step_6 --> step_7
|
|
115
|
+
step_7 --> exit
|
|
116
|
+
role_1 -. owns .-> step_1
|
|
117
|
+
role_2 -. owns .-> step_1
|
|
118
|
+
role_3 -. owns .-> step_2
|
|
119
|
+
role_4 -. owns .-> step_2
|
|
120
|
+
role_5 -. owns .-> step_3
|
|
121
|
+
role_6 -. owns .-> step_4
|
|
122
|
+
role_3 -. owns .-> step_5
|
|
123
|
+
role_5 -. owns .-> step_6
|
|
124
|
+
role_6 -. owns .-> step_6
|
|
125
|
+
role_2 -. owns .-> step_6
|
|
126
|
+
role_1 -. owns .-> step_7
|
|
127
|
+
role_2 -. owns .-> step_7
|
|
128
|
+
step_7 -. iterate if blocked .-> step_1
|
|
129
|
+
```
|
|
130
|
+
<!-- agent-diagram:end -->
|
|
131
|
+
|
|
88
132
|
## Iteration Loop
|
|
89
133
|
Steps 3–6 repeat per increment for large features. `@pm` tracks scope changes and timeline impact.
|
|
90
134
|
|
|
@@ -69,5 +69,40 @@ quality-gates:
|
|
|
69
69
|
- **Output:** merge approval + note in `refactor_plan.md`: "Goal achieved: <description>"
|
|
70
70
|
- **Done when:** PR merged
|
|
71
71
|
|
|
72
|
+
## Agent Interaction Diagram
|
|
73
|
+
|
|
74
|
+
<!-- agent-diagram:start -->
|
|
75
|
+
```mermaid
|
|
76
|
+
flowchart TD
|
|
77
|
+
start(["Start /refactor-module"])
|
|
78
|
+
role_1["team-lead"]
|
|
79
|
+
role_2["qa"]
|
|
80
|
+
role_3["developer"]
|
|
81
|
+
step_1["1. Refactor Plan & Boundaries"]
|
|
82
|
+
step_2["2. Baseline Test Coverage"]
|
|
83
|
+
step_3["3. Incremental Refactor Implementation"]
|
|
84
|
+
step_4["4. Regression Validation"]
|
|
85
|
+
step_5["5. Review / Fix Loop"]
|
|
86
|
+
step_6["6. Closure with Parity Report"]
|
|
87
|
+
exit(["Merged refactor + behavior parity confirmed + improvement goal achieved = r..."])
|
|
88
|
+
start --> step_1
|
|
89
|
+
step_1 --> step_2
|
|
90
|
+
step_2 --> step_3
|
|
91
|
+
step_3 --> step_4
|
|
92
|
+
step_4 --> step_5
|
|
93
|
+
step_5 --> step_6
|
|
94
|
+
step_6 --> exit
|
|
95
|
+
role_1 -. owns .-> step_1
|
|
96
|
+
role_2 -. owns .-> step_2
|
|
97
|
+
role_3 -. owns .-> step_2
|
|
98
|
+
role_3 -. owns .-> step_3
|
|
99
|
+
role_2 -. owns .-> step_4
|
|
100
|
+
role_1 -. owns .-> step_5
|
|
101
|
+
role_3 -. owns .-> step_5
|
|
102
|
+
role_2 -. owns .-> step_5
|
|
103
|
+
role_1 -. owns .-> step_6
|
|
104
|
+
```
|
|
105
|
+
<!-- agent-diagram:end -->
|
|
106
|
+
|
|
72
107
|
## Exit
|
|
73
108
|
Merged refactor + behavior parity confirmed + improvement goal achieved = refactor complete.
|
|
@@ -63,5 +63,35 @@ quality-gates:
|
|
|
63
63
|
- **Output:** `quality_report.md`; stable CI run evidence
|
|
64
64
|
- **Done when:** zero flaky tests; coverage meets threshold; report complete
|
|
65
65
|
|
|
66
|
+
## Agent Interaction Diagram
|
|
67
|
+
|
|
68
|
+
<!-- agent-diagram:start -->
|
|
69
|
+
```mermaid
|
|
70
|
+
flowchart TD
|
|
71
|
+
start(["Start /test-feature"])
|
|
72
|
+
role_1["qa"]
|
|
73
|
+
role_2["developer"]
|
|
74
|
+
role_3["team-lead"]
|
|
75
|
+
step_1["1. Coverage Gap Analysis"]
|
|
76
|
+
step_2["2. Testability Adjustments"]
|
|
77
|
+
step_3["3. Automated Test Implementation"]
|
|
78
|
+
step_4["4. Review of Scenarios & Assertions"]
|
|
79
|
+
step_5["5. Stability Run & Reporting"]
|
|
80
|
+
exit(["Stable test suite + coverage threshold met + @team-lead approval = tests re..."])
|
|
81
|
+
start --> step_1
|
|
82
|
+
step_1 --> step_2
|
|
83
|
+
step_2 --> step_3
|
|
84
|
+
step_3 --> step_4
|
|
85
|
+
step_4 --> step_5
|
|
86
|
+
step_5 --> exit
|
|
87
|
+
role_1 -. owns .-> step_1
|
|
88
|
+
role_2 -. owns .-> step_2
|
|
89
|
+
role_1 -. owns .-> step_3
|
|
90
|
+
role_2 -. owns .-> step_3
|
|
91
|
+
role_3 -. owns .-> step_4
|
|
92
|
+
role_1 -. owns .-> step_5
|
|
93
|
+
```
|
|
94
|
+
<!-- agent-diagram:end -->
|
|
95
|
+
|
|
66
96
|
## Exit
|
|
67
97
|
Stable test suite + coverage threshold met + `@team-lead` approval = tests ready to merge.
|
|
@@ -55,5 +55,30 @@ quality-gates:
|
|
|
55
55
|
- **Output:** `validation_report.md` — row counts, metric comparison, dbt test results
|
|
56
56
|
- **Done when:** all tests pass; metrics match expected; consumers notified
|
|
57
57
|
|
|
58
|
+
## Agent Interaction Diagram
|
|
59
|
+
|
|
60
|
+
<!-- agent-diagram:start -->
|
|
61
|
+
```mermaid
|
|
62
|
+
flowchart TD
|
|
63
|
+
start(["Start /backfill-data"])
|
|
64
|
+
role_1["developer"]
|
|
65
|
+
role_2["qa"]
|
|
66
|
+
step_1["1. Impact Assessment"]
|
|
67
|
+
step_2["2. Dry Run"]
|
|
68
|
+
step_3["3. Execute Backfill"]
|
|
69
|
+
step_4["4. Post-Backfill Validation"]
|
|
70
|
+
exit(["Validated backfill + notified consumers + @team-lead sign-off = backfill co..."])
|
|
71
|
+
start --> step_1
|
|
72
|
+
step_1 --> step_2
|
|
73
|
+
step_2 --> step_3
|
|
74
|
+
step_3 --> step_4
|
|
75
|
+
step_4 --> exit
|
|
76
|
+
role_1 -. owns .-> step_1
|
|
77
|
+
role_2 -. owns .-> step_2
|
|
78
|
+
role_1 -. owns .-> step_3
|
|
79
|
+
role_2 -. owns .-> step_4
|
|
80
|
+
```
|
|
81
|
+
<!-- agent-diagram:end -->
|
|
82
|
+
|
|
58
83
|
## Exit
|
|
59
84
|
Validated backfill + notified consumers + `@team-lead` sign-off = backfill complete.
|
|
@@ -60,5 +60,36 @@ quality-gates:
|
|
|
60
60
|
- **Output:** postmortem; monitoring updated; dbt tests updated
|
|
61
61
|
- **Done when:** postmortem reviewed; prevention measures in place
|
|
62
62
|
|
|
63
|
+
## Agent Interaction Diagram
|
|
64
|
+
|
|
65
|
+
<!-- agent-diagram:start -->
|
|
66
|
+
```mermaid
|
|
67
|
+
flowchart TD
|
|
68
|
+
start(["Start /data-quality-incident"])
|
|
69
|
+
role_1["qa"]
|
|
70
|
+
role_2["developer"]
|
|
71
|
+
role_3["team-lead"]
|
|
72
|
+
step_1["1. Scope & Triage"]
|
|
73
|
+
step_2["2. Quarantine"]
|
|
74
|
+
step_3["3. Root Cause Isolation"]
|
|
75
|
+
step_4["4. Remediation"]
|
|
76
|
+
step_5["5. Post-Incident"]
|
|
77
|
+
exit(["Clean model + postmortem published + prevention measures added = incident c..."])
|
|
78
|
+
start --> step_1
|
|
79
|
+
step_1 --> step_2
|
|
80
|
+
step_2 --> step_3
|
|
81
|
+
step_3 --> step_4
|
|
82
|
+
step_4 --> step_5
|
|
83
|
+
step_5 --> exit
|
|
84
|
+
role_1 -. owns .-> step_1
|
|
85
|
+
role_2 -. owns .-> step_2
|
|
86
|
+
role_1 -. owns .-> step_3
|
|
87
|
+
role_2 -. owns .-> step_3
|
|
88
|
+
role_2 -. owns .-> step_4
|
|
89
|
+
role_3 -. owns .-> step_5
|
|
90
|
+
role_1 -. owns .-> step_5
|
|
91
|
+
```
|
|
92
|
+
<!-- agent-diagram:end -->
|
|
93
|
+
|
|
63
94
|
## Exit
|
|
64
95
|
Clean model + postmortem published + prevention measures added = incident closed.
|
|
@@ -52,5 +52,30 @@ quality-gates:
|
|
|
52
52
|
- **Output:** `lineage_report.md` with diagram, summary, and checklist
|
|
53
53
|
- **Done when:** report reviewed and ready to share with affected owners
|
|
54
54
|
|
|
55
|
+
## Agent Interaction Diagram
|
|
56
|
+
|
|
57
|
+
<!-- agent-diagram:start -->
|
|
58
|
+
```mermaid
|
|
59
|
+
flowchart TD
|
|
60
|
+
start(["Start /lineage-trace"])
|
|
61
|
+
role_1["developer"]
|
|
62
|
+
role_2["team-lead"]
|
|
63
|
+
step_1["1. Parse Target"]
|
|
64
|
+
step_2["2. Trace Lineage"]
|
|
65
|
+
step_3["3. Impact Assessment"]
|
|
66
|
+
step_4["4. Generate Report"]
|
|
67
|
+
exit(["Published lineage report + migration checklist = ready to plan the change s..."])
|
|
68
|
+
start --> step_1
|
|
69
|
+
step_1 --> step_2
|
|
70
|
+
step_2 --> step_3
|
|
71
|
+
step_3 --> step_4
|
|
72
|
+
step_4 --> exit
|
|
73
|
+
role_1 -. owns .-> step_1
|
|
74
|
+
role_1 -. owns .-> step_2
|
|
75
|
+
role_2 -. owns .-> step_3
|
|
76
|
+
role_1 -. owns .-> step_4
|
|
77
|
+
```
|
|
78
|
+
<!-- agent-diagram:end -->
|
|
79
|
+
|
|
55
80
|
## Exit
|
|
56
81
|
Published lineage report + migration checklist = ready to plan the change safely.
|
|
@@ -67,5 +67,35 @@ quality-gates:
|
|
|
67
67
|
- **Actions:** review SQL logic, naming conventions, documentation completeness; approve or return with blocking feedback
|
|
68
68
|
- **Done when:** `@team-lead` approves; PR merged
|
|
69
69
|
|
|
70
|
+
## Agent Interaction Diagram
|
|
71
|
+
|
|
72
|
+
<!-- agent-diagram:start -->
|
|
73
|
+
```mermaid
|
|
74
|
+
flowchart TD
|
|
75
|
+
start(["Start /new-model"])
|
|
76
|
+
role_1["pm"]
|
|
77
|
+
role_2["team-lead"]
|
|
78
|
+
role_3["developer"]
|
|
79
|
+
role_4["qa"]
|
|
80
|
+
step_1["1. Requirements Gathering"]
|
|
81
|
+
step_2["2. Model Design"]
|
|
82
|
+
step_3["3. SQL & YAML Implementation"]
|
|
83
|
+
step_4["4. Validation"]
|
|
84
|
+
step_5["5. Review & Merge"]
|
|
85
|
+
exit(["Passing dbt tests + complete YAML docs + @team-lead approval = model produc..."])
|
|
86
|
+
start --> step_1
|
|
87
|
+
step_1 --> step_2
|
|
88
|
+
step_2 --> step_3
|
|
89
|
+
step_3 --> step_4
|
|
90
|
+
step_4 --> step_5
|
|
91
|
+
step_5 --> exit
|
|
92
|
+
role_1 -. owns .-> step_1
|
|
93
|
+
role_2 -. owns .-> step_2
|
|
94
|
+
role_3 -. owns .-> step_3
|
|
95
|
+
role_4 -. owns .-> step_4
|
|
96
|
+
role_2 -. owns .-> step_5
|
|
97
|
+
```
|
|
98
|
+
<!-- agent-diagram:end -->
|
|
99
|
+
|
|
70
100
|
## Exit
|
|
71
101
|
Passing dbt tests + complete YAML docs + `@team-lead` approval = model production-ready.
|
|
@@ -63,5 +63,34 @@ quality-gates:
|
|
|
63
63
|
- **Output:** `validation_report.md`; catalog updated; owners notified
|
|
64
64
|
- **Done when:** all tests green; documentation current
|
|
65
65
|
|
|
66
|
+
## Agent Interaction Diagram
|
|
67
|
+
|
|
68
|
+
<!-- agent-diagram:start -->
|
|
69
|
+
```mermaid
|
|
70
|
+
flowchart TD
|
|
71
|
+
start(["Start /schema-migration"])
|
|
72
|
+
role_1["team-lead"]
|
|
73
|
+
role_2["developer"]
|
|
74
|
+
role_3["qa"]
|
|
75
|
+
step_1["1. Change Classification"]
|
|
76
|
+
step_2["2. Impact Assessment"]
|
|
77
|
+
step_3["3. Migration Strategy"]
|
|
78
|
+
step_4["4. Execute Migration"]
|
|
79
|
+
step_5["5. Verify & Document"]
|
|
80
|
+
exit(["Post-migration tests green + catalog updated + owners notified = migration..."])
|
|
81
|
+
start --> step_1
|
|
82
|
+
step_1 --> step_2
|
|
83
|
+
step_2 --> step_3
|
|
84
|
+
step_3 --> step_4
|
|
85
|
+
step_4 --> step_5
|
|
86
|
+
step_5 --> exit
|
|
87
|
+
role_1 -. owns .-> step_1
|
|
88
|
+
role_2 -. owns .-> step_2
|
|
89
|
+
role_1 -. owns .-> step_3
|
|
90
|
+
role_2 -. owns .-> step_4
|
|
91
|
+
role_3 -. owns .-> step_5
|
|
92
|
+
```
|
|
93
|
+
<!-- agent-diagram:end -->
|
|
94
|
+
|
|
66
95
|
## Exit
|
|
67
96
|
Post-migration tests green + catalog updated + owners notified = migration complete.
|