Route natural-language QA intents to Generate or Maintain SparQ skills.
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-start
Please help me install this Agent Skill. Skill: sparq:start Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-start Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-start
This Skill acts as the central router for SparQ, interpreting user intent from natural language and directing requests to the appropriate specialized SparQ skills, enabling seamless QA automation workflows.
Invoke /sparq:start to begin routing your QA intents.
High-intent search queries and answers about installing and using this skill.
To route natural-language QA intents, the SparQ start skill detects Jira IDs, Confluence or Figma links, and file references to direct requests to the appropriate specialized skill. It determines whether to use the Generate or Maintain lane and passes context without intruding on the target workflow.
Intent detection for QA test generation uses pattern-based and keyword-based detection on user input to identify Jira IDs or links. It determines whether to trigger the Generate lane for new tests or the Maintain lane for existing ones, then routes the context to the chosen skill.
Yes, you can start a QA workflow using a Jira ticket ID or a Confluence link. The skill detects these specific references in your input, determines the correct automation lane, and passes the ticket or link context directly to the target skill.
To convert manual tests to automated E2E tests, invoke the start skill with a plain-language request or file reference. It identifies the Maintain lane intent and routes the context to the specialized skill needed for the conversion.
The QA routing skill primarily uses pattern and keyword detection to choose between Generate and Maintain lanes. If needed, it prompts for minimal follow-up information while preserving the two-lane workflow before passing context to the target skill.
STUkhConsolidate project requirements from Jira, Confluence, Figma, and local files into a unified spec.
LucaDeLeoGenerates deterministic end-to-end tests for specified features and workflows.
STUkhGenerate manual and automated E2E tests from Jira feature requirements.
nimeshgurungGenerate test suites and analyze code coverage for ReactJS and NodeJS applications.
