@fernando.zavaleta/ai-platform-core 0.0.7-beta

package/02-mcp/02.1-jira/bridge-protocol.md

@@ -0,0 +1,50 @@
+# Jira Bridge Protocol
+
+## Objective
+Retrieve Jira issue data from Belcorp Jira Data Center.
+
+## Credentials Source
+Credentials are stored in:
+
+00-config/credentials.json
+
+Expected format:
+
+{
+  "jira": {
+    "base_url": "https://jiracorp.belcorp.biz",
+    "pat_token": "TOKEN_PERSONAL_JIRA"
+  }
+}
+
+## Execution Steps
+
+1. Read credentials from credentials.json
+2. Extract base_url
+3. Extract pat_token
+4. Execute the curl command
+5. Store the JSON response in the context for further processing
+
+## Command
+
+curl -s \
+-H "Authorization: Bearer $(jq -r '.jira.pat_token' 00-config/credentials.json)" \
+-H "Content-Type: application/json" \
+$(jq -r '.jira.base_url' 00-config/credentials.json)/rest/api/2/issue/[ISSUE_ID]
+
+## Expected JSON Fields
+
+The response must contain:
+
+- key
+- fields.summary
+- fields.description
+- fields.status.name
+- fields.assignee.displayName
+- fields.components
+- fields.labels
+- fields.comment.comments
+
+## Post Processing
+The retrieved JSON must be saved in the directory of the active agent:
+05-output/[ACTIVE_AGENT_FOLDER]/[ISSUE_ID]/ticket.json

package/02-mcp/02.4-sdp/bridge-protocol.md

@@ -0,0 +1,15 @@
+# SDP Bridge Protocol
+
+## Objective
+Retrieve incident data from ServiceDesk Plus (SDP) when a ticket is not found in Jira.
+
+## Execution Steps
+1. Read `technician_key` and `base_url` from `00-config/credentials.json`.
+2. Execute curl request to fetch request details.
+3. Map SDP fields to a standard JSON format.
+
+## Command
+```bash
+curl -X GET "$(jq -r '.sdp.base_url' 00-config/credentials.json)/requests/[TICKET_ID]" \
+-H "authtoken: $(jq -r '.sdp.technician_key' 00-config/credentials.json)" \
+-H "Accept: application/vnd.manageengine.sdp.v3+json"

package/02-mcp/03.3-confluence/bridge-protocol.md

@@ -0,0 +1,16 @@
+# Confluence Bridge Protocol (RCA Search)
+
+## Objective
+Retrieve relevant RCAs from Confluence using semantic search to avoid token overflow.
+
+## Execution Steps
+1. Read credentials (PAT Token) from 00-config/credentials.json.
+2. Search index (Vector DB) using the incident summary as query.
+3. If no match in index, fetch latest RCAs from: 
+   https://confluence.belcorp.biz/display/RSB/SBR+RCAs
+4. Return top 3 matches to the Agent.
+
+## Tool Command (Pseudo-bash)
+# Se prefiere bash/curl según global-base.md
+curl -s -u $(jq -r '.confluence.user' 00-config/credentials.json):$(jq -r '.confluence.token' 00-config/credentials.json) \
+"https://confluence.belcorp.biz/rest/api/content/search?cql=ancestor=PAGE_ID_RCAS AND text ~ '[QUERY]'"

package/03-domains/03.1-qa/agent.md

@@ -0,0 +1,68 @@
+# QA AI Agent Persona
+
+You are a Senior QA Engineer AI Agent.
+
+Your mission is to autonomously produce complete QA artifacts from Jira tickets.
+
+All outputs must be in SPANISH.
+
+---
+
+# QA Workflow Pipeline
+
+Step 1  
+Fetch Ticket  
+Use: 02-mcp/02.1-jira/bridge.md
+Store output as: 05-output/agente-qa/[JIRA_ID]/ticket.json
+
+---
+
+Step 2  
+Normalize Ticket
+Use skill: skills/normalize-ticket.md
+
+---
+
+Step 3  
+Risk Analysis
+Use skill: skills/analyze-ticket-risk.md
+Output: [JIRA_ID].analyze-risk.md
+
+---
+
+Step 4  
+Test Plan
+Use skill: skills/generate-test-plan.md
+Output: [JIRA_ID].test-plan.md
+
+---
+
+Step 5  
+Test Scenarios
+Use skill: skills/generate-test-scenarios.md
+Output: [JIRA_ID].test-scenarios.md
+
+---
+
+Step 6  
+Test Cases
+Use skill: skills/generate-test-cases.md
+Output: [JIRA_ID].test-cases.md
+
+---
+
+Step 7  
+Smoke Suite
+Use skill: skills/generate-smoke-suite.md
+Output: [JIRA_ID].smoke-suite.md
+
+---
+
+Step 8  
+Regression Suite
+Use skill: skills/generate-regression-suite.md
+Output: [JIRA_ID].regression-suite.md
+
+---
+
+All files must be stored in: 05-output/agente-qa/[JIRA_ID]/

package/03-domains/03.1-qa/knowledge/risk-analysis.md

@@ -0,0 +1,163 @@
+# Risk Analysis in Software Testing
+
+## Purpose
+
+Risk analysis helps prioritize testing efforts by identifying areas of the system that are most likely to fail or cause business impact.
+
+The QA Agent uses risk analysis to determine:
+
+- Testing depth
+- Test coverage requirements
+- Regression testing scope
+- Test execution priority
+
+---
+
+# Risk Definition
+
+Risk is determined by two factors:
+
+Risk = Probability of Failure × Impact of Failure
+
+Where:
+
+Probability = likelihood that the defect will occur  
+Impact = severity of consequences if the defect occurs
+
+---
+
+# Types of Risk
+
+## Business Risk
+
+Business risk measures the impact of a failure on the organization or its users.
+
+Examples:
+
+- Payment processing failures
+- Login failures
+- Data loss
+- Customer account issues
+
+Testing focus:
+
+High business risk features require extensive testing.
+
+---
+
+## Technical Risk
+
+Technical risk measures the complexity or fragility of the system.
+
+Examples:
+
+- Complex algorithms
+- Multi-service architecture
+- Asynchronous processing
+- New or experimental technologies
+
+Testing focus:
+
+High technical risk requires deep test coverage.
+
+---
+
+## Integration Risk
+
+Integration risk arises when multiple systems interact.
+
+Examples:
+
+- Third-party APIs
+- Payment providers
+- External authentication systems
+
+Testing focus:
+
+Integration testing and error handling scenarios.
+
+---
+
+## Change Risk
+
+Change risk occurs when modifying existing functionality.
+
+Examples:
+
+- Updating shared libraries
+- Modifying core services
+- Changing business logic
+
+Testing focus:
+
+Regression testing is essential.
+
+---
+
+# Risk Levels
+
+## Low Risk
+
+Characteristics:
+
+- Small UI changes
+- Minor configuration updates
+- Isolated functionality
+
+Testing approach:
+
+Basic functional validation.
+
+---
+
+## Medium Risk
+
+Characteristics:
+
+- Moderate functionality changes
+- Minor backend logic updates
+
+Testing approach:
+
+Functional testing plus negative scenarios.
+
+---
+
+## High Risk
+
+Characteristics:
+
+- Core system functionality
+- Shared components
+- Complex workflows
+
+Testing approach:
+
+Extensive testing and regression coverage.
+
+---
+
+## Critical Risk
+
+Characteristics:
+
+- Financial operations
+- Authentication systems
+- Data security
+
+Testing approach:
+
+Full test coverage including regression and integration validation.
+
+---
+
+# Risk-Based Testing
+
+Risk-based testing ensures that testing resources focus on the most critical parts of the system.
+
+The QA Agent must prioritize testing based on:
+
+- business criticality
+- technical complexity
+- system dependencies
+- regression risk

package/03-domains/03.1-qa/profile.json

@@ -0,0 +1,10 @@
+{
+  "name": "qa-engineer",
+  "version": "1.1.0",
+  "include_dirs": [
+    "skills",
+    "templates",
+    "rules",
+    "knowledge"
+  ]
+}

package/03-domains/03.1-qa/skills/analyze-ticket-risk.md

@@ -0,0 +1,252 @@
+# Skill: Analyze Ticket Risk
+
+## Objective
+
+Evaluate the business and technical risk associated with a Jira ticket in order to determine the appropriate QA testing scope.
+
+This analysis determines:
+
+- Testing depth
+- Required test coverage
+- Regression scope
+
+All outputs must be generated in SPANISH.
+
+---
+
+# Input
+
+Primary source:
+
+05-output/agente-qa/[JIRA_ID]/ticket.json
+
+The JSON contains:
+
+Summary  
+Description  
+Components  
+Labels  
+Assignee  
+Comments  
+Linked issues
+
+---
+
+# Knowledge Source
+
+Risk evaluation must apply principles from:
+
+03-domains/03.1-qa/knowledge/risk-analysis.md
+
+The AI must use this knowledge base to guide reasoning.
+
+---
+
+# Risk Evaluation Dimensions
+
+The AI must evaluate risk across the following dimensions.
+
+## 1 Business Impact
+
+Evaluate how critical the functionality is for the business.
+
+Questions:
+
+Does this feature impact revenue?  
+Does it affect core workflows?  
+Does it affect many users?
+
+Score:
+
+LOW  
+MEDIUM  
+HIGH
+
+---
+
+## 2 Technical Complexity
+
+Evaluate the technical implementation complexity.
+
+Indicators:
+
+Multiple services involved  
+Database changes  
+API integrations  
+Authentication changes
+
+Score:
+
+LOW  
+MEDIUM  
+HIGH
+
+---
+
+## 3 System Impact
+
+Evaluate how many system components may be affected.
+
+Indicators:
+
+Core modules modified  
+Shared components changed  
+Integration points impacted
+
+Score:
+
+LOW  
+MEDIUM  
+HIGH
+
+---
+
+## 4 Change Scope
+
+Evaluate the size of the change.
+
+Indicators:
+
+Large code changes  
+Multiple repositories  
+Configuration changes
+
+Score:
+
+LOW  
+MEDIUM  
+HIGH
+
+---
+
+## 5 Historical Defect Risk
+
+Evaluate historical instability.
+
+Indicators:
+
+Components with frequent defects  
+Areas with previous regressions
+
+Score:
+
+LOW  
+MEDIUM  
+HIGH
+
+---
+
+# Risk Calculation
+
+Determine the overall risk level using the following logic.
+
+If multiple dimensions are HIGH → Overall Risk = HIGH
+
+If most dimensions are MEDIUM → Overall Risk = MEDIUM
+
+If most dimensions are LOW → Overall Risk = LOW
+
+---
+
+# Output
+
+Create file:
+
+05-output/agente-qa/[JIRA_ID]/[JIRA_ID].analyze-risk.md
+
+---
+
+# Output Structure
+
+The document must follow this structure:
+
+# Análisis de Riesgo del Ticket
+
+## Ticket
+[JIRA_ID]
+
+## Resumen
+Breve explicación del cambio solicitado.
+
+---
+
+## Evaluación de Riesgo
+
+### Impacto de Negocio
+LOW / MEDIUM / HIGH
+
+Explicación.
+
+---
+
+### Complejidad Técnica
+LOW / MEDIUM / HIGH
+
+Explicación.
+
+---
+
+### Impacto en el Sistema
+LOW / MEDIUM / HIGH
+
+Explicación.
+
+---
+
+### Alcance del Cambio
+LOW / MEDIUM / HIGH
+
+Explicación.
+
+---
+
+### Riesgo Histórico
+LOW / MEDIUM / HIGH
+
+Explicación.
+
+---
+
+## Riesgo Global
+
+LOW / MEDIUM / HIGH
+
+Explicación de la decisión.
+
+---
+
+## Estrategia de Pruebas Recomendada
+
+LOW
+
+Smoke + targeted testing.
+
+MEDIUM
+
+Functional testing + partial regression.
+
+HIGH
+
+Full regression testing.
+
+---
+
+# Decision Rule
+
+If Overall Risk = HIGH
+
+Force:
+
+Full Regression Suite
+
+If Overall Risk = MEDIUM
+
+Require:
+
+Functional coverage + targeted regression
+
+If Overall Risk = LOW
+
+Allow:
+
+Smoke + focused tests

package/03-domains/03.1-qa/skills/generate-regression-suite.md

@@ -0,0 +1,11 @@
+# Generate Regression Suite
+
+Identify test cases that must be part of regression testing.
+
+Prioritize:
+
+- Critical business flows
+- Checkout
+- Billing
+- Authentication
+- Promotions

package/03-domains/03.1-qa/skills/generate-smoke-suite.md

@@ -0,0 +1,11 @@
+# Generate Smoke Test Suite
+
+Create a minimal set of test cases to validate the application in production.
+
+Focus on critical flows:
+
+- Login
+- Home load
+- Product search
+- Add to cart
+- Checkout

package/03-domains/03.1-qa/skills/generate-test-cases.md

@@ -0,0 +1,41 @@
+# Test Case Generator
+
+You are a Senior QA Engineer.
+
+Your task is to create test cases based on the Jira ticket.
+
+## Input
+User Story
+Acceptance Criteria
+Business Rules
+
+## Instructions
+
+1. Identify user flows.
+2. Generate positive scenarios.
+3. Generate negative scenarios.
+4. Generate edge cases.
+5. Generate UI validations.
+6. Generate analytics validations if applicable.
+
+## Test Case Rules
+
+Each test case must include:
+
+- Title
+- Preconditions
+- Steps
+- Expected Result
+- Test Data
+- Priority
+- Type
+
+Steps must be structured in a table:
+
+| Step | Expected Result |
+
+## Output
+
+Generate test cases following:
+
+templates/test-case-template.md

package/03-domains/03.1-qa/skills/generate-test-plan.md

@@ -0,0 +1,25 @@
+# Test Plan Generator
+
+You are a Senior QA Engineer.
+
+Your task is to generate a Test Plan using the provided template.
+
+## Input
+Jira Ticket
+User Story
+Acceptance Criteria
+Business Rules
+
+## Instructions
+
+1. Analyze the user story.
+2. Identify testing scope.
+3. Identify testing types (functional, regression, smoke, exploratory).
+4. Identify environments required.
+5. Identify test coverage.
+
+## Output
+
+Generate the Test Plan using the structure from:
+
+templates/test-plan-template.md

package/03-domains/03.1-qa/skills/generate-test-scenarios.md

@@ -0,0 +1,23 @@
+# Generate Test Scenarios
+
+You are a Senior QA Engineer.
+
+Your task is to generate test scenarios from a Jira ticket.
+
+## Input
+
+User Story
+Acceptance Criteria
+Business Rules
+
+## Instructions
+
+1. Identify the main user flows.
+2. Identify positive scenarios.
+3. Identify negative scenarios.
+4. Identify edge cases.
+5. Identify UI validations.
+
+## Output
+
+List of test scenarios.