Technical Quality Perspective: Include architecture, reliability, and maintainability in quality decisions
Technical quality is more than tidy code. Availability, maintainability, recovery, and dependency boundaries decide whether a system can serve reliably over time. Evaluation must connect engineering traits to operational consequences.
The Technical Quality Perspective Skill assesses architecture and operational signals together, avoiding isolated code metrics that hide fragility.
This guide uses collaboration-grounded examples to unpack the judgment process, helping you turn different signals into actions that are communicable and traceable.
Awesome QA Skills organizes Skills by language and testing stage. The series overview covers repository structure and shared installation options; this guide stays with Technical quality perspective.
Read the source Skill first
The main prompt covers Required inputs and gate, Technical assessment, Boundary and output, Inputs and workflow, Responsibilities and boundary. Those headings are navigation; the project artifacts still provide the facts.
This Skill has no separate examples directory. The sample below is derived from its entry point, main prompt, and eval constraints.
A review fragment that keeps disagreement visible
Review a service change for architecture, observability, failure recovery, and rollback cost
Different roles can read the same artifact and find different risks.
| Observation | Evidence | Impact | Recommendation |
|---|---|---|---|
| A critical state has no user feedback | Prototype shows only success | Users may submit twice | Add failure and recovery states |
| The schedule has no regression window | Release plan leaves half a day | High-risk fixes cannot be retested | Reduce scope or move the gate |
Do not force agreement. Record evidence and impact, then leave the decision with the accountable owner.
Merge evidence without flattening disagreement
For Review a service change for architecture, observability, failure recovery, and rollback cost, product may care about completion rate, QA about recovery, and engineering about observability and rollback cost. Keep those observations separate.
| Role | Observation | Evidence needed | Decision ownership |
|---|---|---|---|
| Product | Can users finish the journey | Funnel and acceptance record | Scope trade-off |
| QA | Can errors and recovery be verified | Cases, runs, defects | Test conclusion |
| Engineering | Can failures be diagnosed and rolled back | Logs, metrics, deployment record | Technical risk |
Write shared facts after the role-specific notes. A conflict becomes an open decision with options and an approver. Claims about Required inputs and gate and Technical assessment need source links because paraphrasing can change their meaning.
The final quality note can stay short: what is proven, what remains unknown, and who owns it.
A prompt you can adapt
Replace the bracketed fields with project facts. Specific material leaves less room for guessing.
Use the technical-quality-perspective Skill.
Task: Review a service change for architecture, observability, failure recovery, and rollback cost
Version and environment: [requirement / build / environment]
Inputs: [file paths or links]
Scope: [included and excluded journeys]
Constraints: [accounts, data, time, compliance]
Keep each role observation, evidence, and impact separate. Distinguish shared facts from disagreement and name the approver for open decisions.
Finish with open questions. Do not invent missing facts.Use the first pass to inspect structure and gaps. Supply missing material before asking for the handoff-ready artifact.
Advanced use, from one call to a maintained flow
Add confidence and source_id to observations. Re-evaluate conclusions as evidence changes while retaining prior versions and decision records.
A three-Skill chain
requirements-analysis → technical-quality-perspective → multi-role-quality-synthesis
| Handoff | Payload | Receiver check |
|---|---|---|
| Upstream to technical-quality-perspective | Source versions, scope, risks, open questions | Technical quality perspective staleness and conflicts |
| technical-quality-perspective to downstream | Primary artifact, evidence index, unfinished work | Technical quality perspective executability and owners |
| Feedback to technical-quality-perspective | Runs, defects, new risks | Technical quality perspective baseline and regression update |
Do not paste three complete outputs into one large prompt. Give Technical quality perspective a structured summary and accessible source artifacts. It saves context and makes defects traceable.
Team gates
| Gate | Check | Failure action |
|---|---|---|
| technical-quality-perspective input | Version, environment, owner, accessible sources | Stop Technical quality perspective and list gaps |
| technical-quality-perspective artifact | Material claims carry basis and status | Return Technical quality perspective for evidence |
| technical-quality-perspective execution | Command, exit status, report are reproducible | Classify infrastructure or test failure |
| technical-quality-perspective decision | Residual risks have accepter and date | Do not enter the next stage |
Review Technical quality perspective adoption, human edit rate, unsupported claims, and failure-to-diagnosis time each sprint. Record a baseline for several cycles before setting targets.
A perspective Skill is not role-play
Do not invent what product, QA, or engineering would say. Technical quality perspective can only draw observations from available artifacts. When views conflict, record evidence, impact, and the decision owner.
Install and invoke
Install the individual Skill. The series overview carries the longer installation explanation.
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/technical-quality-perspective -gInvoke it with “Use the technical-quality-perspective Skill,” then attach the real artifacts.
Two practical questions
Can one perspective overrule the others?
No. It adds observations. Keep disagreement and supporting evidence visible.
What if that role is absent?
Label the result as proxy analysis and list questions for the actual role. Do not fabricate approval.
What if roles reach opposite conclusions?
Keep both evidence sets, state the risk each role owns, and route the decision to the accountable person.
Can a perspective be written without data?
It can be an observation or assumption if the missing source and next evidence request stay visible.
Run Technical quality perspective against one real artifact and keep the input, output, and review notes. The fragments here establish structure; project evidence must still come from the project.
References
- Awesome QA Skills project:https://github.com/naodeng/awesome-qa-skills
- Awesome QA Skills series overview:https://inaodeng.com/en/blog/ai-testing/introduction_of_awesome_qa_skills/
- Awesome QA Skills: Technical quality perspective Skill source:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/technical-quality-perspective
- Technical quality perspective Skill details:https://inaodeng.com/en/qaskills/technical-quality-perspective/