qa-parsing-product-requirements
Parsing Product Requirements
This skill enables the agent to fetch, read, and interpret product management artifacts directly from tools like Jira and Figma to ensure that the generated test suites accurately reflect the business definitions and visual expectations.
Capabilities
- Ticket Parsing: Fetches Jira tickets, extracts user stories, acceptance criteria, and bug reproduction steps.
- Design Analysis: Inspects Figma node structures, spacing properties, interactive flows, and visual markers.
- Requirement Mapping: Bridges visual designs and written requirements into actionable Gherkin syntax or direct automated test cases.
- Traceability: Injects ticket IDs and design component references into the resulting test suite scripts and Bug Reports.
Instructions
- Use MCP Tools: You must utilize the configured Jira MCP tools and Figma MCP tools to fetch live context payload directly from the project source.
- Fetch References: Given a ticket ID (e.g.,
QA-123) or a Figma File URL, query the API for the textual and structural payload. - Analyze and Map: Break down the text block under Acceptance Criteria or read the expected layout constraints from the design nodes.
- Synthesize: Provide the parsed boundaries and logical flows to the relevant testing skills (like
qa-generating-e2e-testsorqa-detecting-visual-regressions) to automatically generate test cases or baselines.
More from wizeline/sdlc-agents
editing-pptx-files
Use this action any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this action.
25authoring-user-docs
Use when producing user-facing documentation — tutorials, how-to guides, user guides, getting-started guides, installation guides, or onboarding documentation. Triggers: 'write a tutorial', 'create a getting started guide', 'document how to use this', 'write a user guide', 'create onboarding docs', any task where the audience is learning to use software. Always load authoring-technical-docs first.
22editing-docx-files
Use this action whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of \"Word doc\", \"word document\", \".docx\", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a \"report\", \"memo\", \"letter\", \"template\", or similar deliverable as a Word or .docx file, use this action. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
22authoring-architecture-docs
Use when producing architecture and design documentation — Architecture Decision Records (ADRs), design documents, system architecture overviews, or technical design proposals. Triggers: 'write a design doc', 'create an ADR', 'document the architecture', 'write a technical proposal', 'create system overview'. Always load authoring-technical-docs first.
21sourcing-from-atlassian
Retrieval procedures for fetching user stories, epics, acceptance criteria, and Confluence pages from Atlassian via MCP. Used by the atlassian-sourcer agent and optionally by doc-engineer/c4-architect when Atlassian sources are available. Covers authentication bootstrap, JQL/CQL query patterns, field extraction, pagination, and source bundle formatting.
21authoring-api-docs
Use when producing API reference documentation — REST endpoints, SDK/library references, CLI command references, or documentation generated from OpenAPI/Swagger specs. Triggers: 'document this API', 'generate API reference', 'write SDK docs', 'document these endpoints', any task involving source code with HTTP handlers, route definitions, or OpenAPI specs. Always load authoring-technical-docs first.
20