skills.rest
hero-engine
hero-engineOFFICIAL
Explore all skills by this author →
GitHub

whole-team-quality

Frames quality work as shared product responsibility with clear QA expertise and accountable handoffs.

3|2|Updated Aug 24, 2026
Search Tags:#testing#quality assurance#defect triage#team workflow#QA handoff#shared ownership
One-click install
npx skills add https://github.com/hero-engine/hero --skill whole-team-quality-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: whole-team-quality
Source: https://github.com/hero-engine/hero/tree/main/domains/qa/skills/whole-team-quality
Command: npx skills add https://github.com/hero-engine/hero --skill whole-team-quality-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often treat QA as the sole owner of quality, leading to late-stage ticket throwing, unclear rejections, and blurred ownership when defects appear. This Skill frames quality as a shared product responsibility while preserving QA's distinct expertise. ## Core Features & Use Cases - Shared Ownership Framing: Positions prevention and fast feedback near design and implementation instead of concentrating all quality work in QA. - Clear Rejection Criteria: Distinguishes implementation failure from missing requirements or new scope when rejecting work. - Accountable Seam Requests: Explains the testing need behind a seam request while leaving engineering ownership intact. - Use Case: A QA engineer finds a defect during review and uses this guidance to write a rejection that identifies whether the issue is an implementation bug, a missing requirement, or newly introduced scope. ## Quick Start Ask the AI to apply whole-team quality principles when reviewing a QA rejection or drafting a testing seam request for an engineering team.

Frequently Asked Questions about whole-team-quality

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

FAQPage Schema
How do I write a QA rejection that developers accept?▼

A QA rejection should distinguish implementation failure from missing requirements or new scope. State which category the finding belongs to so the team knows whether to fix code, clarify requirements, or plan new work.

What is whole-team quality in software development?▼

Whole-team quality treats quality as shared product responsibility rather than QA's sole ownership. QA supplies testing craft, risk visibility, and independent challenge, while prevention and fast feedback sit near design and implementation.

How should QA request a testing seam from engineering?▼

A seam request must explain the testing need behind it while leaving engineering ownership intact. Describe what needs to be testable and why, without prescribing how engineers should restructure their code.

When should QA not own a quality issue?▼

QA should not become the only owner of quality. Late-stage ticket throwing signals broken handoffs; prevention and fast feedback belong near design and implementation, with QA providing independent challenge and risk visibility.

Related Skills

Explore More Software Engineering Skills→
lintendolintendo
152

user-story-writing

Create user stories with acceptance criteria from product requirements.

Community
Intermediate
JohannesKoningsJohannesKonings

triage

Automate GitHub issue classification and state management with role-based workflows.

Community
Intermediate
qa-amanqa-aman
19

qa-strategy

Generate a formal QA test strategy document with scope, risks, and coverage matrix.

Community
Advanced
qa-amanqa-aman
19

qa-release

Automate QA release decisions and generate formal sign-off reports.

Community
Advanced