Bootstrap an API Test Scenario RTM from EXISTING tests when no RTM file exists yet. Use when a repo already has API tests (Playwright, Jest, NUnit/xUnit, pytest) but there is no requirements/ RTM describing them. The skill discovers the existing tests and the endpoints they cover, generates the canonical scenario set using the api-test-scenario-rtm-generator standard, maps each existing test onto a scenario row (filling E2E Test Name and aligning status/expected result from assertions), and writes a new RTM file with a realistic per-method status. Invoke when the user says things like "we already have tests but no scenarios file", "backfill scenarios from these tests", "reverse-engineer the RTM from the spec files", "generate requirements from existing tests", "create a scenario file for tests/api/...", or "map our existing tests to scenarios". If an RTM file already exists for the resource group, this skill defers to api-test-scenario-rtm-updater.
Generate a new API Test Scenario RTM (Requirements Traceability Matrix) file from a prompt, OpenAPI spec, or controller source. Creates structured test cases with boundary analysis, validation testing, and testing pyramid principles for REST API endpoints and saves them as an RTM file in requirements/.
Review, sync, and update API Test Scenario RTM files. Use when scenarios are outdated after tests changed, boundary values need updating, resolved warnings should be removed, E2E Test Names need syncing after Playwright tests are renamed, or an RTM needs to be brought up to the current coverage standard (OWASP, REST semantics, BVA). Invoke whenever the user mentions reviewing or updating an RTM, scenario corrections, boundary values, test synchronization, coverage gaps, or says things like "update the scenarios for X", "tests changed in Y.spec.ts", "I now know the min/max length", "the bug is fixed", or "are we missing OWASP cases?".
Review software requirements against the 8 Key Characteristics of Good Requirements (Clear, Complete, Consistent, Verifiable, Feasible, Traceable, Atomic, Positive) and produce a structured report with issues, clarifying questions, a per-requirement grading table, aggregate scores, and top recommendations. Use this skill whenever the user asks to "review requirements", "check my requirements", "analyze user stories", "review acceptance criteria", "validate my specs", "grade my requirements", "give feedback on requirements", or pastes/attaches a list of requirements or user stories and asks for feedback — even if they just say "are these good?" or attach a requirements document.
Run a phased git workflow: create branch (optional), commit, push, and open a GitHub pull request. Reports success or failure per phase and surfaces the PR URL when the final phase succeeds. Use when the user wants to ship a feature branch end-to-end or wants a single scripted pipeline with phase status.
Create new Jira Cloud issues via the Atlassian MCP: bugs, tasks, stories, sub-tasks. Loads project defaults from a local config file. Use when the user asks to create a Jira ticket, file a bug, add a task, add a story, or log a new issue.
Search and browse Jira Cloud issues via the Atlassian MCP. Run JQL queries, view backlogs, sprint scope, bug lists, stale issues, and any JQL-driven list. Use when the user asks for Jira backlog items, project issues, sprint issues, open bugs, issues by status, or wants to run a JQL query.
Update existing Jira Cloud issues via the Atlassian MCP: transition statuses, add comments, edit fields (priority, labels, fix version, summary), and link issues. Use when the user asks to move an issue to a different status, add a comment to a ticket, change a field on an existing issue, or link two issues together.