scene-capability-engine 3.0.0

package/template/.kiro/templates/operations/default/feedback-response.md

@@ -0,0 +1,269 @@
+# Feedback Response Procedures
+
+## Feedback Classification Rules
+
+### Rule 1: Bug Reports
+
+**Indicators**:
+- Keywords: error, bug, broken, crash, fail
+- User reports unexpected behavior
+- System logs show errors
+
+**Classification**:
+- Type: bug_report
+- Severity: Based on impact (critical/high/medium/low)
+
+**Routing**: Development team
+
+### Rule 2: Performance Issues
+
+**Indicators**:
+- Keywords: slow, timeout, lag, performance
+- Response time complaints
+- Resource utilization alerts
+
+**Classification**:
+- Type: performance_issue
+- Severity: Based on degradation level
+
+**Routing**: Operations team
+
+### Rule 3: Feature Requests
+
+**Indicators**:
+- Keywords: feature, enhancement, improvement, add
+- User suggests new functionality
+- Workflow improvement ideas
+
+**Classification**:
+- Type: feature_request
+- Severity: low (unless critical business need)
+
+**Routing**: Product team
+
+### Rule 4: Operational Concerns
+
+**Indicators**:
+- Keywords: availability, downtime, access
+- Service interruption reports
+- Configuration issues
+
+**Classification**:
+- Type: operational_concern
+- Severity: Based on service impact
+
+**Routing**: Operations team
+
+## Response Procedures
+
+### Critical Severity Response
+
+**SLA**: Acknowledge within 15 minutes, respond within 1 hour
+
+**Immediate actions**:
+1. Acknowledge receipt
+2. Assess impact and scope
+3. Trigger incident response (see troubleshooting.md)
+4. Notify stakeholders
+5. Provide status updates every 30 minutes
+
+**Response template**:
+```
+Thank you for reporting this critical issue. We have:
+- Acknowledged: [timestamp]
+- Assigned to: [team/person]
+- Current status: [investigating/identified/fixing]
+- Expected resolution: [timeframe]
+- Next update: [timestamp]
+```
+
+### High Severity Response
+
+**SLA**: Acknowledge within 1 hour, respond within 4 hours
+
+**Actions**:
+1. Acknowledge receipt
+2. Investigate root cause
+3. Implement fix or workaround
+4. Verify resolution
+5. Follow up with reporter
+
+**Response template**:
+```
+Thank you for reporting this issue. We have:
+- Acknowledged: [timestamp]
+- Investigation findings: [summary]
+- Resolution: [fix/workaround]
+- Status: [resolved/in-progress]
+```
+
+### Medium Severity Response
+
+**SLA**: Acknowledge within 4 hours, respond within 1 business day
+
+**Actions**:
+1. Acknowledge receipt
+2. Schedule investigation
+3. Provide workaround if available
+4. Plan fix in next release
+5. Update reporter on progress
+
+**Response template**:
+```
+Thank you for your feedback. We have:
+- Acknowledged: [timestamp]
+- Workaround: [if available]
+- Planned fix: [release version]
+- Timeline: [expected date]
+```
+
+### Low Severity Response
+
+**SLA**: Acknowledge within 1 business day, respond within 3 business days
+
+**Actions**:
+1. Acknowledge receipt
+2. Add to backlog
+3. Prioritize with other requests
+4. Provide timeline estimate
+
+**Response template**:
+```
+Thank you for your suggestion. We have:
+- Acknowledged: [timestamp]
+- Added to: [backlog/roadmap]
+- Priority: [low/medium/high]
+- Estimated timeline: [timeframe]
+```
+
+## Escalation Paths
+
+### Level 1: First Response Team
+
+**Responsibility**: Initial triage and response
+
+**Escalate to Level 2 if**:
+- Cannot resolve within SLA
+- Requires specialized expertise
+- Affects multiple systems
+
+### Level 2: Subject Matter Experts
+
+**Responsibility**: Deep investigation and resolution
+
+**Escalate to Level 3 if**:
+- Requires architectural changes
+- Affects business operations
+- Needs executive decision
+
+### Level 3: Leadership
+
+**Responsibility**: Strategic decisions and resource allocation
+
+**Escalate to Level 4 if**:
+- Major incident
+- Legal/compliance implications
+- Significant business impact
+
+### Level 4: Executive
+
+**Responsibility**: Crisis management and external communication
+
+## Resolution Tracking
+
+### Tracking Fields
+
+**Required fields**:
+- Feedback ID
+- Received date
+- Classification (type + severity)
+- Assigned to
+- Status (acknowledged/investigating/resolved/verified)
+- Resolution date
+- Resolution summary
+
+**Optional fields**:
+- Root cause
+- Related issues
+- Lessons learned
+- Follow-up actions
+
+### Status Transitions
+
+```
+acknowledged → investigating → resolved → verified
+```
+
+**Transition rules**:
+- acknowledged → investigating: When investigation starts
+- investigating → resolved: When fix is deployed
+- resolved → verified: When reporter confirms resolution
+
+### Metrics to Track
+
+**Response metrics**:
+- Time to acknowledge
+- Time to respond
+- Time to resolve
+- Time to verify
+
+**Quality metrics**:
+- First contact resolution rate
+- Reopened feedback rate
+- Customer satisfaction score
+
+**Volume metrics**:
+- Feedback by channel
+- Feedback by type
+- Feedback by severity
+- Feedback by version
+
+## Automated Response Patterns
+
+### Pattern 1: Known Issues
+
+**Trigger**: Feedback matches known issue signature
+
+**Automated response**:
+```
+Thank you for your report. This is a known issue:
+- Issue ID: [id]
+- Status: [status]
+- Workaround: [if available]
+- Expected fix: [version/date]
+
+For updates, track: [link]
+```
+
+**Human review**: Required for critical severity
+
+### Pattern 2: Duplicate Reports
+
+**Trigger**: Feedback duplicates existing report
+
+**Automated response**:
+```
+Thank you for your report. This issue has been reported:
+- Original report: [id]
+- Current status: [status]
+- Expected resolution: [timeframe]
+
+We've linked your report for tracking.
+```
+
+**Human review**: Not required unless new information
+
+### Pattern 3: Status Updates
+
+**Trigger**: Scheduled update or status change
+
+**Automated response**:
+```
+Update on your feedback [id]:
+- Status: [new status]
+- Progress: [summary]
+- Next steps: [actions]
+- Expected completion: [timeframe]
+```
+
+**Human review**: Required for critical/high severity

package/template/.kiro/templates/operations/default/migration-plan.md

@@ -0,0 +1,172 @@
+# Data Migration Plan
+
+## Migration Strategy
+
+**Strategy type**: Online / Offline / Hybrid
+
+**Rationale**: Why this strategy was chosen
+
+**Downtime**: Required / Not required (if required, duration)
+
+**Rollback capability**: Yes / No
+
+## Data Mapping
+
+### Mapping 1: [Source → Target]
+
+**Source**:
+- System: Source system name
+- Schema: Source schema/structure
+- Volume: Estimated data volume
+
+**Target**:
+- System: Target system name
+- Schema: Target schema/structure
+- Transformations: Required transformations
+
+**Mapping rules**:
+```
+source_field_1 → target_field_1 (transformation if any)
+source_field_2 → target_field_2 (transformation if any)
+```
+
+**Data quality checks**:
+- [ ] Check 1
+- [ ] Check 2
+- [ ] Check 3
+
+### Mapping 2: [Source → Target]
+
+**Source**:
+- System: Source system name
+- Schema: Source schema/structure
+- Volume: Estimated data volume
+
+**Target**:
+- System: Target system name
+- Schema: Target schema/structure
+- Transformations: Required transformations
+
+**Mapping rules**:
+```
+source_field_1 → target_field_1 (transformation if any)
+source_field_2 → target_field_2 (transformation if any)
+```
+
+**Data quality checks**:
+- [ ] Check 1
+- [ ] Check 2
+- [ ] Check 3
+
+## Validation Steps
+
+### Pre-Migration Validation
+
+**Purpose**: Ensure readiness for migration
+
+**Checks**:
+1. Check 1
+   ```bash
+   # Validation command
+   ```
+   Expected result: Description
+
+2. Check 2
+   ```bash
+   # Validation command
+   ```
+   Expected result: Description
+
+3. Check 3
+   ```bash
+   # Validation command
+   ```
+   Expected result: Description
+
+**Go/No-Go criteria**:
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+### During-Migration Validation
+
+**Purpose**: Monitor migration progress
+
+**Checks**:
+1. Check 1 - Frequency: Every X minutes
+2. Check 2 - Frequency: Every X minutes
+3. Check 3 - Frequency: Every X minutes
+
+**Abort criteria**:
+- Condition 1
+- Condition 2
+- Condition 3
+
+### Post-Migration Validation
+
+**Purpose**: Verify migration success
+
+**Checks**:
+1. Data completeness
+   ```bash
+   # Validation command
+   ```
+   Expected result: Description
+
+2. Data integrity
+   ```bash
+   # Validation command
+   ```
+   Expected result: Description
+
+3. Application functionality
+   ```bash
+   # Validation command
+   ```
+   Expected result: Description
+
+**Success criteria**:
+- [ ] All data migrated
+- [ ] No data corruption
+- [ ] Application functional
+- [ ] Performance acceptable
+
+## Rollback Plan
+
+**Rollback triggers**:
+- Trigger 1
+- Trigger 2
+- Trigger 3
+
+**Rollback procedure**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Data preservation**:
+- How to preserve data during rollback
+- Recovery point objective (RPO)
+- Recovery time objective (RTO)
+
+**Verification after rollback**:
+- [ ] System restored
+- [ ] Data intact
+- [ ] No data loss
+
+## Timeline
+
+| Phase | Duration | Start | End | Owner |
+|-------|----------|-------|-----|-------|
+| Preparation | | | | |
+| Pre-migration validation | | | | |
+| Migration execution | | | | |
+| Post-migration validation | | | | |
+| Monitoring period | | | | |
+
+**Critical path**: Steps that cannot be delayed
+
+**Dependencies**: External dependencies that could affect timeline
+
+**Communication plan**:
+- Stakeholder updates: Frequency and method
+- Issue escalation: Who to contact and when

package/template/.kiro/templates/operations/default/monitoring.md

@@ -0,0 +1,135 @@
+# Monitoring Specification
+
+## Metrics
+
+### Metric 1: [Metric Name]
+
+**Description**: What this metric measures
+
+**Type**: Counter / Gauge / Histogram / Summary
+
+**Collection method**: How the metric is collected
+
+**Frequency**: How often to collect
+
+**Labels**: Key-value pairs for metric dimensions
+
+```
+metric_name{label1="value1", label2="value2"}
+```
+
+### Metric 2: [Metric Name]
+
+**Description**: What this metric measures
+
+**Type**: Counter / Gauge / Histogram / Summary
+
+**Collection method**: How the metric is collected
+
+**Frequency**: How often to collect
+
+**Labels**: Key-value pairs for metric dimensions
+
+```
+metric_name{label1="value1", label2="value2"}
+```
+
+## Thresholds
+
+### Threshold 1: [Threshold Name]
+
+**Metric**: Which metric this threshold applies to
+
+**Warning level**: Value that triggers warning
+
+**Critical level**: Value that triggers critical alert
+
+**Duration**: How long condition must persist
+
+**Rationale**: Why these thresholds were chosen
+
+### Threshold 2: [Threshold Name]
+
+**Metric**: Which metric this threshold applies to
+
+**Warning level**: Value that triggers warning
+
+**Critical level**: Value that triggers critical alert
+
+**Duration**: How long condition must persist
+
+**Rationale**: Why these thresholds were chosen
+
+## Alert Rules
+
+### Alert 1: [Alert Name]
+
+**Condition**: When this alert fires
+
+**Severity**: Critical / High / Medium / Low
+
+**Notification channels**: Where to send alerts
+
+**Escalation**: Who to notify and when
+
+**Runbook**: Link to troubleshooting procedure
+
+### Alert 2: [Alert Name]
+
+**Condition**: When this alert fires
+
+**Severity**: Critical / High / Medium / Low
+
+**Notification channels**: Where to send alerts
+
+**Escalation**: Who to notify and when
+
+**Runbook**: Link to troubleshooting procedure
+
+## Response Procedures
+
+### Procedure 1: [Procedure Name]
+
+**Trigger**: What alert or condition triggers this procedure
+
+**Immediate actions**:
+1. Action 1
+2. Action 2
+3. Action 3
+
+**Investigation steps**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Resolution**:
+- Resolution approach 1
+- Resolution approach 2
+
+**Post-incident**:
+- [ ] Document incident
+- [ ] Update runbook if needed
+- [ ] Review and improve
+
+### Procedure 2: [Procedure Name]
+
+**Trigger**: What alert or condition triggers this procedure
+
+**Immediate actions**:
+1. Action 1
+2. Action 2
+3. Action 3
+
+**Investigation steps**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Resolution**:
+- Resolution approach 1
+- Resolution approach 2
+
+**Post-incident**:
+- [ ] Document incident
+- [ ] Update runbook if needed
+- [ ] Review and improve

package/template/.kiro/templates/operations/default/operations.md

@@ -0,0 +1,135 @@
+# Daily Operations Specification
+
+## Daily Tasks
+
+### Task 1: [Task Name]
+
+**Frequency**: Daily / Weekly / Monthly
+
+**Time**: When to perform (e.g., 9:00 AM UTC)
+
+**Duration**: Expected time to complete
+
+**Procedure**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Verification**:
+- [ ] Check 1
+- [ ] Check 2
+
+**Automation status**: Manual / Semi-automated / Fully automated
+
+### Task 2: [Task Name]
+
+**Frequency**: Daily / Weekly / Monthly
+
+**Time**: When to perform (e.g., 9:00 AM UTC)
+
+**Duration**: Expected time to complete
+
+**Procedure**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Verification**:
+- [ ] Check 1
+- [ ] Check 2
+
+**Automation status**: Manual / Semi-automated / Fully automated
+
+## Maintenance Procedures
+
+### Procedure 1: [Procedure Name]
+
+**Purpose**: What this maintenance accomplishes
+
+**Frequency**: How often to perform
+
+**Downtime required**: Yes / No (if yes, how long)
+
+**Prerequisites**:
+- [ ] Prerequisite 1
+- [ ] Prerequisite 2
+
+**Steps**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Verification**:
+- [ ] Verification 1
+- [ ] Verification 2
+
+**Rollback**: How to undo if needed
+
+### Procedure 2: [Procedure Name]
+
+**Purpose**: What this maintenance accomplishes
+
+**Frequency**: How often to perform
+
+**Downtime required**: Yes / No (if yes, how long)
+
+**Prerequisites**:
+- [ ] Prerequisite 1
+- [ ] Prerequisite 2
+
+**Steps**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Verification**:
+- [ ] Verification 1
+- [ ] Verification 2
+
+**Rollback**: How to undo if needed
+
+## Backup Procedures
+
+### Backup 1: [Backup Type]
+
+**What to backup**: Description of data/systems
+
+**Frequency**: How often to backup
+
+**Retention**: How long to keep backups
+
+**Location**: Where backups are stored
+
+**Procedure**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Verification**:
+- [ ] Backup completed successfully
+- [ ] Backup integrity verified
+- [ ] Backup accessible
+
+**Recovery test**: How often to test recovery
+
+### Backup 2: [Backup Type]
+
+**What to backup**: Description of data/systems
+
+**Frequency**: How often to backup
+
+**Retention**: How long to keep backups
+
+**Location**: Where backups are stored
+
+**Procedure**:
+1. Step 1
+2. Step 2
+3. Step 3
+
+**Verification**:
+- [ ] Backup completed successfully
+- [ ] Backup integrity verified
+- [ ] Backup accessible
+
+**Recovery test**: How often to test recovery