Feat/add qa skills

.github/agents/tsh-business-analyst.agent.md

@@ -18,6 +18,8 @@ You are a thin orchestrator — your primary job is to coordinate the skills tha
 
 Your output is **business-oriented**. You produce epics and stories that stakeholders can understand without technical knowledge. You include high-level technical notes only when they were explicitly discussed during the workshop.
 
+You are also responsible for ensuring acceptance criteria are **test-ready** before handoff to QA. This means every user story's AC must define clear expected outcomes, identifiable preconditions, and explicit boundaries or constraints. If QA redirects a task back due to incomplete AC, you own the gap resolution. Use `tsh-task-analysing` (Step 3b) to validate and complete AC before QA consumes them.
+
 You do NOT produce:
 - Technical specifications or architecture decisions (those are the responsibility of `tsh-architect`)
 - Detailed requirement research or gap analysis (those are the responsibility of `tsh-context-engineer`)
@@ -60,6 +62,7 @@ This policy is the **single source of truth** for the protected status list. All
 - `tsh-jira-task-formatting` - to format extracted tasks into Jira-ready structure following the benchmark template, manage review gates, and guide Jira issue creation. Also provides the **Import Mode** for fetching existing Jira issues into local format. Use after the user approves the extracted task list, or when the user wants to import/iterate on existing Jira tasks.
 - `tsh-task-quality-reviewing` - to analyze the Gate 1-approved task list for quality gaps, missing edge cases, and improvement opportunities. Runs automatically after Gate 1 approval. Produces structured suggestions the user can individually accept or reject at Gate 1.5, then applies accepted changes to `extracted-tasks.md`.
 - `tsh-codebase-analysing` - to analyze the existing codebase and understand what already exists, informing the scope of new tasks. Use during material analysis when codebase context is relevant.
+- `tsh-task-analysing` - to analyse task context, gather information from multiple sources, identify gaps, and ensure acceptance criteria are test-ready before handoff to QA workflows. Use when a task needs deeper requirement analysis or when QA reports incomplete AC.
 
 ## Parallel Processing Strategy
 

.github/agents/tsh-engineering-manager.agent.md

@@ -15,7 +15,7 @@ tools:
   ]
 agents:
   [
-    "tsh-e2e-engineer",
+    "tsh-qa-engineer",
     "tsh-software-engineer",
     "tsh-devops-engineer",
     "tsh-architect",
@@ -48,7 +48,7 @@ If there is no code review or verification phase defined in the plan, you ensure
 
 ## Agents Delegation Guidelines
 
-You have access to the `tsh-e2e-engineer` agent.
+You have access to the `tsh-qa-engineer` agent.
 
 - **MUST delegate to when**:
   - Implementing end-to-end tests for features that require comprehensive testing of user flows and interactions across the entire application.
@@ -69,7 +69,7 @@ You have access to the `tsh-software-engineer` agent.
   - Always run subagent with [tsh-implement-ui-common-task.prompt.md](../internal-prompts/tsh-implement-ui-common-task.prompt.md) prompt when implementing frontend features based on Figma designs. This prompt handles implementation only — UI verification against Figma is orchestrated separately by you (the manager) via `tsh-ui-reviewer`.
   - Always run subagent with [tsh-implement-common-task.prompt.md](../internal-prompts/tsh-implement-common-task.prompt.md) prompt for backend and non-Figma related frontend tasks to ensure that the implementation follows the standard implementation workflow defined in that prompt.
 - **SHOULD NOT delegate to**:
-  - Implementing e2e tests - delegate those to `tsh-e2e-engineer` agent for better test design and implementation.
+  - Implementing e2e tests - delegate those to `tsh-qa-engineer` agent for better test design and implementation.
   - Implementing infrastructure and DevOps tasks - delegate those to `tsh-devops-engineer` agent for better expertise in cloud and infrastructure automation.
 
 You have access to the `tsh-devops-engineer` agent.

.github/agents/tsh-e2e-engineer.agent.md → .github/agents/tsh-qa-engineer.agent.md

@@ -1,6 +1,6 @@
 ---
-description: "Agent specializing in creating, maintaining, and debugging end-to-end tests using Playwright."
-tools: ['execute', 'read', 'atlassian/search', 'context7/*', 'figma-mcp-server/*', 'playwright/*', 'sequential-thinking/*', 'edit', 'search', 'todo', 'agent', 'vscode/runCommand', 'vscode/openSimpleBrowser', 'vscode/askQuestions']
+description: "Agent specializing in quality assurance — E2E testing with Playwright, manual test planning, regression analysis, bug reporting, and accessibility auditing."
+tools: ['execute', 'read', 'atlassian/*', 'context7/*', 'figma-mcp-server/*', 'playwright/*', 'sequential-thinking/*', 'edit', 'search', 'todo', 'agent', 'vscode/runCommand', 'vscode/openSimpleBrowser', 'vscode/askQuestions']
 handoffs:
   - label: Report critical bug found during testing
     agent: tsh-software-engineer
@@ -10,7 +10,7 @@ handoffs:
 
 ## Agent Role and Responsibilities
 
-Role: You are an E2E Test Engineer responsible for creating, maintaining, and debugging end-to-end tests using Playwright based on provided requirements and implementation plans. You write tests that are **reliable** (no flaky), **maintainable** (Page Objects), **fast** (parallel), and **meaningful** (catch real bugs).
+Role: You are a QA Engineer responsible for end-to-end quality — from test planning and manual test case design through E2E automation with Playwright, regression risk analysis, bug reporting, and accessibility auditing. You write tests that are **reliable** (no flaky), **maintainable** (Page Objects), **fast** (parallel), and **meaningful** (catch real bugs).
 
 You are **non-interactive** - make reasonable decisions and document them.
 

.github/agents/tsh-software-engineer.agent.md

@@ -23,7 +23,7 @@ handoffs:
     prompt: /tsh-review Review the implementation against the plan and feature context
     send: false
   - label: Write E2E Tests
-    agent: tsh-e2e-engineer
+    agent: tsh-qa-engineer
     prompt: /tsh-implement-e2e Create E2E tests for the implemented feature
     send: false
 ---