template-instructions 1.0.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.
@@ -0,0 +1,70 @@
1
+ # Phase Report - [Phase Name]
2
+
3
+ ## Document Info
4
+ | Field | Value |
5
+ |-------|-------|
6
+ | Phase | [Planning/Design/Development/Testing/Deployment] |
7
+ | Date | [YYYY-MM-DD] |
8
+ | Author | @REPORTER |
9
+ | Status | Complete / In Progress |
10
+
11
+ ---
12
+
13
+ ## 1. Phase Summary
14
+ | Metric | Planned | Actual |
15
+ |--------|---------|--------|
16
+ | Duration | [X days] | [X days] |
17
+ | Items | [X] | [X] |
18
+ | On Schedule | ✅/❌ | - |
19
+
20
+ ## 2. Completed Deliverables
21
+ | Deliverable | Owner | Version | Status |
22
+ |-------------|-------|---------|--------|
23
+ | [Artifact name] | @[ROLE] | v[X] | ✅ Complete |
24
+
25
+ ## 3. Key Accomplishments
26
+ - [Accomplishment 1]
27
+ - [Accomplishment 2]
28
+
29
+ ## 4. Issues & Resolutions
30
+ | Issue | Impact | Resolution | Status |
31
+ |-------|--------|------------|--------|
32
+ | [Issue 1] | [Impact] | [How resolved] | Resolved |
33
+
34
+ ## 5. Risks Identified
35
+ | Risk | Likelihood | Impact | Mitigation |
36
+ |------|------------|--------|------------|
37
+ | [Risk description] | High/Med/Low | High/Med/Low | [Action] |
38
+
39
+ ## 6. Metrics
40
+
41
+ ### Development Metrics (if applicable)
42
+ | Metric | Value |
43
+ |--------|-------|
44
+ | Features Completed | [X/Y] |
45
+ | Code Coverage | [X]% |
46
+ | Technical Debt Items | [X] |
47
+
48
+ ### Testing Metrics (if applicable)
49
+ | Metric | Value |
50
+ |--------|-------|
51
+ | Test Pass Rate | [X]% |
52
+ | Bugs Found | [X] |
53
+ | Bugs Fixed | [X] |
54
+
55
+ ## 7. Lessons Learned
56
+ - [Lesson 1]
57
+ - [Lesson 2]
58
+
59
+ ## 8. Next Phase Preview
60
+ | Phase | Start Date | Key Activities |
61
+ |-------|------------|----------------|
62
+ | [Next phase] | [Date] | [Activities] |
63
+
64
+ ---
65
+
66
+ ### Next Step:
67
+ - @[NEXT_ROLE] - Begin [next phase activities]
68
+ - @STAKEHOLDER - Review phase completion (if final phase)
69
+
70
+ #reporting
@@ -0,0 +1,84 @@
1
+ # Product Backlog - Version [X]
2
+
3
+ ## Document Info
4
+ | Field | Value |
5
+ |-------|-------|
6
+ | Version | [X.0] |
7
+ | Date | [YYYY-MM-DD] |
8
+ | Author | @PO |
9
+ | Status | Draft / Active |
10
+
11
+ ---
12
+
13
+ ## Backlog Summary
14
+ | Priority | Count | Status |
15
+ |----------|-------|--------|
16
+ | Must-Have | [X] | [X] Done |
17
+ | Should-Have | [X] | [X] Done |
18
+ | Could-Have | [X] | [X] Done |
19
+
20
+ ---
21
+
22
+ ## Must-Have Items
23
+
24
+ ### [ITEM-001] [Item Title]
25
+ | Field | Value |
26
+ |-------|-------|
27
+ | Priority | Must-Have |
28
+ | Status | Todo / In Progress / Done |
29
+ | Assigned | @[ROLE] |
30
+ | Sprint | [Sprint #] |
31
+
32
+ **Description:** [Brief description]
33
+
34
+ **Acceptance Criteria:**
35
+ - [ ] Criteria 1
36
+ - [ ] Criteria 2
37
+
38
+ ---
39
+
40
+ ## Should-Have Items
41
+
42
+ ### [ITEM-002] [Item Title]
43
+ | Field | Value |
44
+ |-------|-------|
45
+ | Priority | Should-Have |
46
+ | Status | Todo |
47
+ | Assigned | @[ROLE] |
48
+ | Sprint | [Sprint #] |
49
+
50
+ **Description:** [Brief description]
51
+
52
+ **Acceptance Criteria:**
53
+ - [ ] Criteria 1
54
+
55
+ ---
56
+
57
+ ## Could-Have Items
58
+
59
+ ### [ITEM-003] [Item Title]
60
+ | Field | Value |
61
+ |-------|-------|
62
+ | Priority | Could-Have |
63
+ | Status | Todo |
64
+ | Assigned | Unassigned |
65
+ | Sprint | Backlog |
66
+
67
+ **Description:** [Brief description]
68
+
69
+ ---
70
+
71
+ ## Sprint Planning
72
+
73
+ ### Sprint 1: [Focus Area]
74
+ | Item ID | Title | Assigned | Status |
75
+ |---------|-------|----------|--------|
76
+ | ITEM-001 | [Title] | @DEV | Todo |
77
+
78
+ ---
79
+
80
+ ### Next Step:
81
+ - @DEV - Begin development of Sprint 1 items
82
+ - @TESTER - Prepare test cases for Sprint 1
83
+
84
+ #product-owner #backlog
@@ -0,0 +1,79 @@
1
+ # Project Plan - Version [X]
2
+
3
+ ## Document Info
4
+ | Field | Value |
5
+ |-------|-------|
6
+ | Version | [X.0] |
7
+ | Date | [YYYY-MM-DD] |
8
+ | Author | @PM |
9
+ | Status | Draft / Approved |
10
+
11
+ ---
12
+
13
+ ## Project Title
14
+ [Project name]
15
+
16
+ ## Business Goals
17
+ - [Goal 1]
18
+ - [Goal 2]
19
+
20
+ ## Scope & Features
21
+
22
+ ### Must-Have
23
+ - [ ] Feature 1: [Description]
24
+ - [ ] Feature 2: [Description]
25
+
26
+ ### Should-Have
27
+ - [ ] Feature 1: [Description]
28
+
29
+ ### Could-Have (if time permits)
30
+ - [ ] Feature 1: [Description]
31
+
32
+ ## User Stories / Use Cases
33
+ | ID | As a... | I want... | So that... | Priority |
34
+ |----|---------|-----------|------------|----------|
35
+ | US-01 | [User type] | [Feature] | [Benefit] | Must |
36
+ | US-02 | [User type] | [Feature] | [Benefit] | Should |
37
+
38
+ ## Target Platforms & Tech Stack
39
+ | Layer | Technology |
40
+ |-------|------------|
41
+ | Frontend | [e.g., SvelteKit, React] |
42
+ | Backend | [e.g., Node.js, Python] |
43
+ | Database | [e.g., PostgreSQL, Supabase] |
44
+ | Deployment | [e.g., Vercel, AWS] |
45
+
46
+ ## High-Level Timeline
47
+ | Phase | Duration | Target Date |
48
+ |-------|----------|-------------|
49
+ | Planning | Complete | [Date] |
50
+ | Design | [X days] | [Date] |
51
+ | Development | [X days] | [Date] |
52
+ | Testing | [X days] | [Date] |
53
+ | Deployment | [X days] | [Date] |
54
+
55
+ ## Risks & Assumptions
56
+ | Type | Description | Mitigation |
57
+ |------|-------------|------------|
58
+ | Risk | [Risk description] | [Mitigation plan] |
59
+ | Assumption | [Assumption] | - |
60
+
61
+ ## Task Assignments
62
+ | Role | Responsibility |
63
+ |------|----------------|
64
+ | @SA | Backend architecture |
65
+ | @UIUX | UI/UX design |
66
+ | @DEV | Implementation |
67
+ | @DEVOPS | CI/CD, deployment |
68
+ | @TESTER | Testing |
69
+
70
+ ## Approval Status
71
+ ⏳ Awaiting user approval.
72
+
73
+ ---
74
+
75
+ ### Next Step After Approval:
76
+ - @SA @UIUX @PO - Start design phase (in parallel)
77
+ - @REPORTER - Begin progress tracking
78
+
79
+ #planning
@@ -0,0 +1,80 @@
1
+ # Security Review Report - Version [X]
2
+
3
+ ## Document Info
4
+ | Field | Value |
5
+ |-------|-------|
6
+ | Version | [X.0] |
7
+ | Date | [YYYY-MM-DD] |
8
+ | Author | @SECA |
9
+ | Status | Pass / Fail / Conditional Pass |
10
+
11
+ ---
12
+
13
+ ## 1. Scope of Review
14
+ | Area | Reviewed |
15
+ |------|----------|
16
+ | Authentication | ✅/❌ |
17
+ | Authorization | ✅/❌ |
18
+ | Data Validation | ✅/❌ |
19
+ | API Security | ✅/❌ |
20
+ | Data Storage | ✅/❌ |
21
+ | Dependencies | ✅/❌ |
22
+
23
+ ## 2. Security Summary
24
+ | Severity | Count | Status |
25
+ |----------|-------|--------|
26
+ | Critical | [X] | [X] Resolved |
27
+ | High | [X] | [X] Resolved |
28
+ | Medium | [X] | [X] Resolved |
29
+ | Low | [X] | [X] Resolved |
30
+
31
+ ## 3. Findings
32
+
33
+ ### 3.1 Critical
34
+ | ID | Finding | OWASP Ref | Status |
35
+ |----|---------|-----------|--------|
36
+ | SEC-001 | [Description] | [A01-A10] | Open/Resolved |
37
+
38
+ ### 3.2 High
39
+ | ID | Finding | OWASP Ref | Status |
40
+ |----|---------|-----------|--------|
41
+ | SEC-002 | [Description] | [A01-A10] | Open/Resolved |
42
+
43
+ ### 3.3 Medium
44
+ | ID | Finding | OWASP Ref | Status |
45
+ |----|---------|-----------|--------|
46
+ | SEC-003 | [Description] | [A01-A10] | Open/Resolved |
47
+
48
+ ### 3.4 Low
49
+ | ID | Finding | OWASP Ref | Status |
50
+ |----|---------|-----------|--------|
51
+ | SEC-004 | [Description] | [A01-A10] | Open/Resolved |
52
+
53
+ ## 4. Security Checklist
54
+ - [ ] Input validation on all endpoints
55
+ - [ ] SQL injection prevention (parameterized queries)
56
+ - [ ] XSS prevention (output encoding)
57
+ - [ ] CSRF protection
58
+ - [ ] Authentication tokens properly secured
59
+ - [ ] Authorization checks on all protected resources
60
+ - [ ] Sensitive data encrypted at rest
61
+ - [ ] Sensitive data encrypted in transit (HTTPS)
62
+ - [ ] No secrets in source code
63
+ - [ ] Dependency vulnerabilities addressed
64
+
65
+ ## 5. Recommendations
66
+ 1. [Security recommendation 1]
67
+ 2. [Security recommendation 2]
68
+
69
+ ## 6. Verdict
70
+ ☐ **PASS** - No blocking security issues
71
+ ☐ **CONDITIONAL PASS** - Proceed with noted mitigations
72
+ ☐ **FAIL** - Critical/High issues must be resolved
73
+
74
+ ---
75
+
76
+ ### Next Step:
77
+ - @SA @DEV - Address security findings (if any)
78
+ - @DEV - Proceed with development (if approved)
79
+
80
+ #security-review
@@ -0,0 +1,97 @@
1
+ # Test Report - Version [X]
2
+
3
+ ## Document Info
4
+ | Field | Value |
5
+ |-------|-------|
6
+ | Version | [X.0] |
7
+ | Date | [YYYY-MM-DD] |
8
+ | Author | @TESTER |
9
+ | Environment | Staging / Production |
10
+ | Build | [Build #/Version] |
11
+
12
+ ---
13
+
14
+ ## 1. Test Summary
15
+ | Metric | Value |
16
+ |--------|-------|
17
+ | Total Test Cases | [X] |
18
+ | Passed | [X] |
19
+ | Failed | [X] |
20
+ | Blocked | [X] |
21
+ | Pass Rate | [X]% |
22
+
23
+ ## 2. Test Coverage
24
+ | Feature | Test Cases | Passed | Failed |
25
+ |---------|------------|--------|--------|
26
+ | [Feature 1] | [X] | [X] | [X] |
27
+ | [Feature 2] | [X] | [X] | [X] |
28
+
29
+ ## 3. Test Cases
30
+
31
+ ### TC-001: [Test Case Name]
32
+ | Field | Value |
33
+ |-------|-------|
34
+ | Feature | [Feature name] |
35
+ | Priority | High/Medium/Low |
36
+ | Status | ✅ Pass / ❌ Fail / ⏸️ Blocked |
37
+
38
+ **Steps:**
39
+ 1. [Step 1]
40
+ 2. [Step 2]
41
+
42
+ **Expected Result:** [Expected behavior]
43
+ **Actual Result:** [Actual behavior]
44
+ **Evidence:** [Screenshot/Recording link]
45
+
46
+ ---
47
+
48
+ ### TC-002: [Test Case Name]
49
+ | Field | Value |
50
+ |-------|-------|
51
+ | Feature | [Feature name] |
52
+ | Priority | High/Medium/Low |
53
+ | Status | ✅ Pass / ❌ Fail / ⏸️ Blocked |
54
+
55
+ **Steps:**
56
+ 1. [Step 1]
57
+
58
+ **Expected Result:** [Expected behavior]
59
+ **Actual Result:** [Actual behavior]
60
+
61
+ ---
62
+
63
+ ## 4. Bugs Found
64
+ | Bug ID | Title | Severity | Status | Assigned |
65
+ |--------|-------|----------|--------|----------|
66
+ | BUG-001 | [Title] | Critical/High/Med/Low | Open | @DEV |
67
+ | BUG-002 | [Title] | Critical/High/Med/Low | Open | @DEV |
68
+
69
+ ### BUG-001: [Bug Title]
70
+ | Field | Value |
71
+ |-------|-------|
72
+ | Severity | Critical / #fixbug-critical |
73
+ | Steps to Reproduce | [Steps] |
74
+ | Expected | [Expected behavior] |
75
+ | Actual | [Actual behavior] |
76
+ | Evidence | [Screenshot/Recording] |
77
+
78
+ ---
79
+
80
+ ## 5. Test Verdict
81
+ ☐ **PASS** - All critical tests passed, ready for production
82
+ ☐ **CONDITIONAL PASS** - Minor issues, can proceed with known limitations
83
+ ☐ **FAIL** - Critical/High bugs must be fixed before release
84
+
85
+ ## 6. Blockers
86
+ | Blocker | Impact | Status |
87
+ |---------|--------|--------|
88
+ | [Blocker description] | [Impact] | Open/Resolved |
89
+
90
+ ---
91
+
92
+ ### Next Step:
93
+ - @DEV - Fix bugs: [BUG-001, BUG-002]
94
+ - @DEVOPS - Deploy to production (if approved)
95
+ - @REPORTER - Include test results in phase report
96
+
97
+ #testing
@@ -0,0 +1,151 @@
1
+ # Definition of Done (DoD) Checklist
2
+ **Version:** 1.0 | **Last Updated:** 2025-12-23
3
+
4
+ ---
5
+
6
+ ## Purpose
7
+ This checklist ensures consistent quality standards across all deliverables. A task is **NOT DONE** until ALL applicable items are checked.
8
+
9
+ ---
10
+
11
+ ## 📋 Development Task DoD
12
+
13
+ ### Code Quality
14
+ - [ ] Code implemented according to approved design specs
15
+ - [ ] Follows project coding standards and conventions
16
+ - [ ] No hardcoded values (use config/environment variables)
17
+ - [ ] No console.log / debug code left in production code
18
+ - [ ] Proper error handling implemented
19
+ - [ ] Code is self-documenting with clear naming
20
+
21
+ ### Testing
22
+ - [ ] Unit tests written and passing
23
+ - [ ] Local testing passed (all features work as expected)
24
+ - [ ] Edge cases handled and tested
25
+ - [ ] No regressions introduced
26
+
27
+ ### Documentation
28
+ - [ ] Code comments for complex logic
29
+ - [ ] API documentation updated (if applicable)
30
+ - [ ] Tagged with `#development`
31
+
32
+ ### Evidence
33
+ - [ ] Screenshots/recordings captured (if UI changes)
34
+ - [ ] Build logs showing success
35
+
36
+ ### Handoff
37
+ - [ ] Development-Log artifact updated
38
+ - [ ] @TESTER tagged for testing
39
+
40
+ ---
41
+
42
+ ## 🧪 Testing Task DoD
43
+
44
+ ### Test Execution
45
+ - [ ] All test cases from Test Plan executed
46
+ - [ ] Happy path scenarios verified
47
+ - [ ] Error/edge case scenarios verified
48
+ - [ ] Acceptance criteria from user stories validated
49
+
50
+ ### Bug Management
51
+ - [ ] All bugs logged with proper priority tags
52
+ - [ ] No `#fixbug-critical` or `#fixbug-high` bugs remaining open
53
+ - [ ] Responsible @DEV tagged for each bug
54
+
55
+ ### Evidence
56
+ - [ ] Screenshots/recordings for key flows
57
+ - [ ] Screenshots/recordings for each bug found
58
+
59
+ ### Documentation
60
+ - [ ] Test-Report artifact created/updated
61
+ - [ ] Tagged with `#testing`
62
+
63
+ ### Handoff (if passed)
64
+ - [ ] @REPORTER tagged
65
+ - [ ] @STAKEHOLDER tagged (if ready for final review)
66
+
67
+ ---
68
+
69
+ ## 🚀 Deployment Task DoD
70
+
71
+ ### Pre-Deployment
72
+ - [ ] All tests passing in CI/CD pipeline
73
+ - [ ] Security checklist completed
74
+ - [ ] Environment variables configured correctly
75
+ - [ ] Database migrations ready (if applicable)
76
+
77
+ ### Staging
78
+ - [ ] Deployed to staging environment successfully
79
+ - [ ] Smoke tests passed on staging
80
+ - [ ] Tagged with `#deployed-staging`
81
+
82
+ ### Production
83
+ - [ ] Staging approved by @TESTER
84
+ - [ ] Deployed to production environment
85
+ - [ ] Health checks passing
86
+ - [ ] Monitoring/alerting configured
87
+ - [ ] Tagged with `#deployed-production`
88
+
89
+ ### Documentation
90
+ - [ ] DevOps-Plan-and-Log artifact updated
91
+ - [ ] Deployment steps documented
92
+
93
+ ### Rollback
94
+ - [ ] Rollback plan documented and tested
95
+
96
+ ---
97
+
98
+ ## 📊 Design Task DoD
99
+
100
+ ### Design Quality
101
+ - [ ] All Must-Have requirements addressed
102
+ - [ ] Consistent with project plan scope
103
+ - [ ] Diagrams/mockups are clear and complete
104
+ - [ ] APIs designed for both UI needs and backend feasibility
105
+
106
+ ### Review Readiness
107
+ - [ ] Design-Spec artifact created with proper naming
108
+ - [ ] Tagged with `#designing` or `#uiux-design`
109
+
110
+ ### Handoff
111
+ - [ ] @QA tagged for design verification
112
+ - [ ] @SECA tagged for security review
113
+
114
+ ---
115
+
116
+ ## ✅ Project Completion DoD
117
+
118
+ ### Feature Delivery
119
+ - [ ] All Must-Have features implemented and verified
120
+ - [ ] All Should-Have features implemented (or justified deferral)
121
+ - [ ] No `#fixbug-critical` or `#fixbug-high` bugs remaining
122
+
123
+ ### Approvals
124
+ - [ ] Design approved by QA + SecA
125
+ - [ ] Testing passed by TESTER
126
+ - [ ] STAKEHOLDER final approval received
127
+
128
+ ### Documentation
129
+ - [ ] Master-Documentation.md complete and current
130
+ - [ ] Final-Project-Report.md created by REPORTER
131
+ - [ ] All artifacts versioned and archived
132
+
133
+ ### Notification
134
+ - [ ] User notified of project completion
135
+ - [ ] Handover documentation provided (if applicable)
136
+
137
+ ---
138
+
139
+ ## Quick Reference Card
140
+
141
+ | Task Type | Key Criteria | Tags |
142
+ |-----------|--------------|------|
143
+ | **Development** | Code works, tests pass, evidence captured | `#development` |
144
+ | **Testing** | All cases run, no critical/high bugs | `#testing` |
145
+ | **Deployment** | CI passes, staging verified, rollback ready | `#deployed-*` |
146
+ | **Design** | Covers requirements, diagrams clear | `#designing` |
147
+ | **Project** | All features done, stakeholder approved | `#reporting` |
148
+
149
+ ---
150
+
151
+ #global-rules #definition-of-done
@@ -0,0 +1,111 @@
1
+ # Incident Response Template
2
+ **Version:** 1.0 | **Last Updated:** 2025-12-23
3
+
4
+ ---
5
+
6
+ ## 🚨 Incident Details
7
+
8
+ | Field | Value |
9
+ |-------|-------|
10
+ | **Incident ID** | INC-[YYYY-MM-DD]-[###] |
11
+ | **Severity** | `Critical` / `High` / `Medium` / `Low` |
12
+ | **Status** | `Detected` / `Triaging` / `Fixing` / `Deploying` / `Resolved` / `Postmortem` |
13
+ | **Detected By** | @[role] |
14
+ | **Detected At** | [datetime] |
15
+ | **Resolved At** | [datetime] |
16
+ | **Duration** | [total downtime] |
17
+
18
+ ---
19
+
20
+ ## Incident Summary
21
+ [Brief description of what happened]
22
+
23
+ ## Impact
24
+ - **Affected Users:** [all / specific group / percentage]
25
+ - **Affected Features:** [list features]
26
+ - **Data Loss:** Yes / No
27
+ - **Security Breach:** Yes / No
28
+
29
+ ---
30
+
31
+ ## Response Timeline
32
+
33
+ | Time | Action | Owner | Status |
34
+ |------|--------|-------|--------|
35
+ | [time] | Incident detected | @TESTER / @DEVOPS | ✅ |
36
+ | [time] | Triage started | @PM + @DEVOPS | ✅ |
37
+ | [time] | Root cause identified | @DEV[#] | ✅ |
38
+ | [time] | Hotfix implemented | @DEV[#] | ✅ |
39
+ | [time] | Quick test passed | @TESTER | ✅ |
40
+ | [time] | Hotfix deployed | @DEVOPS | ✅ |
41
+ | [time] | Incident resolved | @PM | ✅ |
42
+
43
+ ---
44
+
45
+ ## Root Cause Analysis
46
+
47
+ ### What Happened
48
+ [Detailed technical explanation]
49
+
50
+ ### Why It Happened
51
+ [Root cause - code bug / config error / infrastructure / external dependency]
52
+
53
+ ### Contributing Factors
54
+ - [ ] Missing tests
55
+ - [ ] Inadequate monitoring
56
+ - [ ] Configuration drift
57
+ - [ ] External service failure
58
+ - [ ] Human error
59
+ - [ ] Other: [specify]
60
+
61
+ ---
62
+
63
+ ## Hotfix Details
64
+
65
+ | Item | Details |
66
+ |------|---------|
67
+ | **Hotfix Branch** | `hotfix/INC-[id]` |
68
+ | **Files Changed** | [list files] |
69
+ | **Testing** | Smoke test only / Full regression |
70
+ | **Rollback Plan** | [describe rollback steps] |
71
+
72
+ ### Hotfix Code Summary
73
+ ```
74
+ [Brief description or diff summary of the fix]
75
+ ```
76
+
77
+ ---
78
+
79
+ ## Action Items (Preventive Measures)
80
+
81
+ | # | Action | Owner | Priority | Due Date | Status |
82
+ |---|--------|-------|----------|----------|--------|
83
+ | 1 | [action] | @[role] | High | [date] | ⬜ |
84
+ | 2 | [action] | @[role] | Medium | [date] | ⬜ |
85
+ | 3 | [action] | @[role] | Low | [date] | ⬜ |
86
+
87
+ ---
88
+
89
+ ## Lessons Learned
90
+ 1. [lesson 1]
91
+ 2. [lesson 2]
92
+ 3. [lesson 3]
93
+
94
+ ---
95
+
96
+ ## Sign-Off
97
+
98
+ | Role | Name | Date | Signature |
99
+ |------|------|------|-----------|
100
+ | PM | | | ☐ Approved |
101
+ | DevOps | | | ☐ Approved |
102
+ | REPORTER | | | ☐ Documented |
103
+
104
+ ---
105
+
106
+ ### Next Step:
107
+ - @REPORTER - Include in Phase-Report
108
+ - @PM - Schedule postmortem review if needed
109
+ - @DEVOPS - Add monitoring for this scenario
110
+
111
+ #hotfix #fixbug-critical #incident #reporting