A maturity label is easy to write and hard to defend. “Advanced QA” means little if nobody can point to the evidence, the rubric anchor, or the gap that should close next.
Why this Skill is needed
The Quality Maturity Assessment Skill turns plans, test reports, delivery signals, and production feedback into an evidence-bounded view of quality practice. It gives a team a credible baseline without pretending a static document proves runtime capability.
What the Skill does
An assessment is useful when it ties each improvement gap to a rubric anchor and evidence the team can validate.
Use this Skill to review maturity dimensions such as requirement quality, test design, automation, delivery feedback, and operational learning. It separates facts, evidence-backed inferences, candidate improvements, and Human decisions instead of collapsing them into one unsupported score.
A good assessment names the dimension, rubric anchor, source, evidence state, gap, priority, owner role, close condition, and smallest validation method.
Use it to compare quality practices, prepare an improvement plan, or check whether a reported maturity gain is supported by evidence.
What it does not do
The Quality Maturity Assessment Skill can organize material, evidence, and next actions for each quality-practice dimension. It does not replace:
- Confirmation of rules, scope, and risk by the accountable domain owner.
- A real environment, account, dataset, log, or run record; static analysis does not become runtime evidence by itself.
- Authorization for release, compliance, production actions, or residual-risk acceptance.
- A Human decision when supplied sources conflict.
What it checks
Connect each maturity dimension to an observable practice, its rubric anchor, and the evidence needed to assess it. Start with a small matrix based on the source Skill’s output contract:
| Focus | Question before analysis | Handoff output |
|---|---|---|
| Maturity dimension | Which quality practice is in scope? | Dimension and exclusions |
| Rubric anchor | What observable practice distinguishes the levels? | Framework, version, and anchor |
| Evidence sufficiency | Do artifacts show the practice and its continuity? | Source, version, time, and evidence state |
| Improvement gap | What is the smallest change that can move the practice forward? | Owner, priority, close condition |
| Decision boundary | What still needs Human confirmation? | Explicitly not scored |
If a row has only a conventional expectation and no source or validation method, keep it open instead of turning it into a pass.
Audit inputs before you start
Before assessing a quality-practice dimension, classify the input into six evidence states. A gap is not automatically a failure, but it must not disappear inside the conclusion.
| State | Meaning | How this Skill should handle it |
|---|---|---|
| known | Directly supported by the supplied material | Keep the source, version, and time with the judgment |
| missing | Needed for this pass but not supplied | Name the smallest evidence action and limit the conclusion |
| conflicting | Sources disagree | Show both sources and route the conflict to an owner |
| stale | Present but outside the relevant version or time window | Mark freshness; old evidence is not current proof |
| out_of_scope | Related but excluded from this pass | Keep the boundary explicit |
| assumptions | Temporarily adopted to continue analysis | State how and when the assumption will be checked |
Keep the input version, scope, environment, evidence locations, and accountable owner together. Without a run record, deliver analysis, design, or a validation plan—not an execution pass.
From problem to structured Finding
Connect the source, scope, evidence state, analysis, owner, action, close condition, and validation before writing the conclusion. The case below keeps this Skill’s identifier and domain context.
Keep the decision layers separate
For each maturity finding, separate facts, evidence-backed inferences, recommendations, and Human decisions:
| Layer | How to write it | Application here |
|---|---|---|
| Fact | What the supplied material directly shows | Cite the source, version, input, or run record for the focus |
| Evidence-backed Inference | What several facts support together | Show the inference chain and retain uncertainty |
| Recommendation | The smallest next action | Name the evidence, review, execution, or regression path |
| Human Decision | What an accountable person must decide | Leave scope, risk acceptance, resources, and release meaning to the owner |
A complete case
This case follows Input, Analysis, Finding, Decision, and Validation. When material is incomplete, keep missing, conflicting, or assumptions visible instead of turning them into a pass.
Input
Put the material on the table before asking for a judgment. Gaps can remain, but their status must stay visible.
| Material | What to provide | What to do when it is missing |
|---|---|---|
| Goal and scope | Compare checkout quality practice across two releases and four maturity dimensions | Keep excluded dimensions explicit |
| Version and time window | Release IDs, environments, review period, and rubric version | Mark the comparison bounded or stale |
| Evidence | Requirement reviews, CI results, escaped defects, runbooks, and production feedback | Separate facts from assumptions |
| Decision boundary | Improvement owner, risk accepter, and decisions this review must not make | Leave release approval to a Human |
Use a request like this:
Use the quality-maturity-assessment Skill.
Task: Compare the checkout team's quality practice for releases R24.8 and R24.9 across requirement review, test design, CI feedback, and production learning.
Inputs: [rubric, source links, CI reports, defect records, runbook paths]
Scope: [teams, releases, dimensions]
Constraints: [time window, missing data, privacy limits]
Retain source, evidence state, rubric anchor, priority, owner, close condition, and validation method. Do not produce a release approval or unsupported maturity score.
Analysis
Use the input, matrix, and evidence state to form the judgment before writing the Finding; keep missing material as a gap.
Finding
Focused example: Compare releases without overstating maturity
Illustrative example: assume the material shows that a checkout team added contract tests for R24.9 and reported fewer escaped defects, but provides no comparable incident-review window. The Skill can record that artifacts show contract tests were added for the specified API set; this does not prove they run consistently or cover the behavior adequately. Production learning remains unassessed. A missing review record does not mean no incident occurred, and the evidence does not establish that the new tests caused a maturity gain. Ask for comparable release review and learning records, and keep the conclusion pending until they are available.
The assessment describes what the supplied evidence supports and where it falls short. It does not prove every team follows the practice, that the next release is safe, or that a maturity label is the business decision.
Example finding: turn one problem into a handoff
The field example below shows the recording pattern; it is not an execution result.
If the supplied material does not support a conclusion for one maturity dimension, use this finding format. Keep the missing rule visible; do not treat missing evidence as a failure.
| Field | Example wording |
|---|---|
| Source and scope | Record the requirement, version, environment, and the practice being assessed |
| Finding | The maturity judgment is not yet traceable to evidence |
| Evidence state | missing / assumptions; use conflicting when sources disagree |
| Impact and priority | Name the affected user, journey, or delivery decision without inflating severity |
| Owner and Human decision | Ask the product, engineering, security, or test owner to confirm the rule and trade-off |
| Action and close condition | Add the smallest missing evidence; close only when source, judgment, and owner can be reviewed |
| Validation | Name one repeatable check, query, or run and retain the raw artifact |
This record lets the next reviewer trace the judgment to its source and see which evidence or decision remains open.
Decision
The accountable owner confirms the decision question and risk trade-off; the Skill does not make that choice.
Validation
Before closing the finding, run the stated validation and retain the raw artifact. Without an execution record, the status remains unverified.
How a Finding enters the next stage
Handoff output
| Output field | Why it exists | Example status |
|---|---|---|
| Dimension finding | What the evidence supports about one practice | Assessed / Unassessed / Pending |
| Evidence map | Which source supports the finding and how fresh it is | Source, version, date, or missing |
| Improvement gap | The smallest change that can move the practice forward | Owner, priority, close condition |
| Decision boundary | What still needs Human confirmation | Explicitly not scored |
Every conclusion should point to a source, evidence state, and next action. If evidence is missing, use pending, blocked, unassessed, or NOT_SCORED instead of filling the gap with confidence.
Next-stage route
At minimum, hand off the source, evidence state, owner, close condition, and validation action; the next-stage conclusion remains bounded by the evidence state.
Put the assessment inside the quality loop
Maturity depends on whether a practice repeats and learns from results, not on whether an artifact exists once:
- Define the requirement or risk, the quality-practice dimension, and the supplied rubric anchor.
- Design test cases. Treat AI-generated cases as candidates until a reviewer checks their trace to the requirement and their expected results.
- Run the reviewed cases against a named build and environment; retain the version, time, evidence, and result.
- Triage failures and gaps, assign an owner, make the product or test change, and link the retest to the original result.
- Reassess with the same rubric and a comparable time window. Templates show that artifacts exist; repeated runs with failure handling show operating practice.
How to prepare better input
Provide the rubric, fixed time window, release or team identifiers, evidence inventory, and intended use. If the rubric is missing, ask for it; do not invent a scale.
A useful handoff includes input versions, scope, time window, evidence index, assumptions, Human decision boundary, and the smallest validation action.
Best practices
- Start with practices most likely to affect business loss, quality regression, or a blocked decision.
- Use the smallest verifiable evidence request or experiment, and record its conditions, version, source, and result.
- Compare equivalent dimensions and time windows; one improved metric does not establish a cause or a maturity gain.
Working with other Skills
- Quality Metrics Design: https://inaodeng.com/en/qaskills/quality-metrics-design/ — defines metric contracts that can support a maturity dimension.
- Quality Gate Design: https://inaodeng.com/en/qaskills/quality-gate-design/ — turns high-risk gaps into explicit delivery gates.
- Quality Debt Analysis: https://inaodeng.com/en/qaskills/quality-debt-analysis/ — helps prioritize unresolved quality-practice debt.
Common traps
- Treating a tool or dashboard as proof that a practice is consistently used.
- Turning one improved metric into a causal maturity claim without a comparable window.
- Ranking every gap as urgent while leaving no owner, close condition, or validation method.
Install and invoke
Install the English Skill from its language directory:
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en --skill quality-maturity-assessment
Then invoke it by name with the project material:
Use the quality-maturity-assessment Skill.
Include objective, scope, versions, evidence paths, constraints, and decision boundary.
Audit inputs first, preserve evidence states, and finish with owner, close condition, and validation method.
FAQ
Can an incomplete evidence set still be reviewed?
Yes. Return a bounded first pass, label missing or stale evidence, and name the smallest evidence action. Do not fill the gap with a conventional maturity level.
Does the Skill choose improvement priority?
No. It orders findings by evidence and impact; the accountable Human decides risk acceptance, funding, and release implications.
The Skill is most useful when attached to one real project artifact and kept with its source evidence. Start narrow, validate the uncertain part, and expand only when evidence supports it.
References
Source Skill and execution contract
The complete execution contract lives in the Quality Maturity Assessment prompt: https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/quality-maturity-assessment/prompts/quality-maturity-assessment.md. The source directory: https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/quality-maturity-assessment may also contain evaluation cases and supporting material.
Static plans, file presence, and dry runs keep their evidence state. They do not become runtime proof, an all-passed claim, or release approval.
Further reading
- Quality Maturity Assessment details: https://inaodeng.com/en/qaskills/quality-maturity-assessment/
- Awesome QA Skills on GitHub: https://github.com/naodeng/awesome-qa-skills
More Resources
- Personal website: https://inaodeng.com/en/
- AI-generated test detection project: https://github.com/AI-Native-QA-Lab/ai-test-auditor
- DeepSeek QA Workbench: https://github.com/naodeng/dsh-qa
- More AI testing skills: https://inaodeng.com/en/qaskills/
- More testing wiki: https://inaodeng.com/en/wiki/
- More AI Wiki: https://inaodeng.com/en/AIWiki/