team-qa

Orchestrate QA activities from strategy to sign-off across sprints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill team-qa-naxoruto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill team-qa-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates QA team through a full testing cycle from strategy to sign-off for sprints or features.

Core Features & Use Cases

  • QA strategy & test plan generation: Create strategy and a plan for stories, ensuring clarity and coverage.
  • Test case writing & bug reporting: Delegate to qa-lead and qa-tester tasks, generating comprehensive test cases and bug reports.
  • Smoke check gate: Validate build readiness and surface blockers before deep testing.
  • Manual QA execution & sign-off: Execute manual tests and compile a sign-off report for stakeholders.
  • Phase-driven pipeline: Structured phases with context loading, planning, execution, and review, driven by task delegation.

Quick Start

Invoke the skill with a sprint or feature scope to start a QA cycle.

Frequently Asked Questions about team-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate QA activities across a sprint from strategy to sign-off?

Sprint QA coordination requires orchestrating strategy, test planning, execution, and sign-off. This Skill delegates tasks to subagents to generate a complete QA package, ensuring structured phases from context loading through manual testing to final stakeholder reporting.

What is the best way to generate test plans and bug reports for feature testing?

Generating test plans and bug reports for feature testing is handled by delegating work to specialized subagents. The Skill coordinates strategy creation and test case writing, producing comprehensive documentation and structured bug reports for the testing cycle.

Can I automate smoke checks before deep manual QA execution?

Automating smoke checks before manual QA execution is supported as a gating phase. The Skill validates build readiness to surface blockers early, ensuring the build is stable enough before proceeding to deep manual testing and sign-off compilation.

Does this QA workflow handle both test strategy creation and test case writing?

Test strategy creation and test case writing are both handled within this QA workflow. It orchestrates subagents to define the overarching strategy and generate detailed test cases, ensuring full coverage for sprint stories and feature requirements.

How do I compile a QA sign-off report for stakeholders after a testing cycle?

Compiling a QA sign-off report for stakeholders is the final phase of this testing cycle. After executing manual tests, the Skill aggregates results to produce a formal sign-off report, validating feature readiness and documenting any remaining quality issues.

When should I use a phased QA pipeline instead of ad hoc testing for sprints?

A phased QA pipeline should be used instead of ad hoc testing when coordinating complex sprints requiring structured phases. It enforces context loading, strategy, planning, execution, and review through task delegation, ensuring comprehensive coverage and traceable sign-off.