release-analyzelisted

# Katalon Release Analyze Use this skill to assess release readiness from Katalon MCP data. The output must be a testing-quality decision, not just a metric dump. ## Availability Boundary State the MCP boundary before promising an assessment: - Available through Katalon MCP: project/repository discovery, requirements, test cases, test suites, executions/results, quality summaries, defect data, stability data, and configuration coverage when tools are exposed. - Not directly available: create formal Test Plan entities, inspect live AUT UI, guarantee AI execution completion, or decide product/business readiness beyond test evidence. - If MCP tools are unavailable, provide only a framework/template and mark release confidence as Low until data is verified. Read `references/capability-boundaries.md` when capability scope is unclear. ## Required Scope Resolve or ask for the minimum missing scope: - Katalon project and repository/Test Project. - Release identifier, sprint, iteration, version, test suite, suite collection, execution ID, or date range. - Target environment/configuration matrix when readiness depends on browsers, devices, OS, or deployment environments. - Quality gate thresholds when the team has defined them. If the user gives only a release name or issue key, use MCP discovery first. Ask only when multiple equally plausible scopes remain. ## MCP Data Collection Always resolve context before analysis: 1. Call `list_projects`. 2. Call `list_repositories`.