pkuppens/architecture-quality
skills/architecture/architecture-quality/SKILL.md
Documents quality tree and quality scenarios; maps to requirements (arc42 §10). Use when defining non-functional goals, scenarios, or acceptance of quality attributes.
development
Updated May 25, 2026
$ install --global
skillsauthnpx skillsauth add pkuppens/pkuppens architecture-qualityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 25, 2026, 5:09 AM47.8s1 file scanned
SKILL.md
- name:
- architecture-quality
- description:
- Documents quality tree and quality scenarios; maps to requirements (arc42 §10). Use when defining non-functional goals, scenarios, or acceptance of quality attributes.
Architecture Quality
Documents quality goals as scenarios the architecture must satisfy. Aligns with arc42 §10 (quality requirements).
When to use
- Defining or refining non-functional requirements (performance, security, availability)
- Before major design decisions — test options against quality scenarios
- Pairing with requirements-goals for top-level goals
Outputs
docs/architecture/10-quality.md— quality tree and scenarios- Trace links to requirements and ADRs where decisions affect quality
Instructions
- List quality attributes — e.g. performance, security, maintainability, usability, compliance.
- Build a quality tree — refine each attribute into measurable sub-topics.
- Write scenarios — stimulus / environment / artefact / response / measure (ISO 25010 style).
- Map to requirements — link scenario IDs to requirement or issue IDs.
- Record architecture tactics — caching, redundancy, authZ — without duplicating full ADR text (link to §9).
Quality scenario format
# Quality (arc42 §10)
## Quality tree
- Performance
- API latency under load
- Batch throughput
## Scenarios
| ID | Attribute | Stimulus | Response | Measure |
|----|-----------|----------|----------|---------|
| QS-01 | Performance | 100 RPS sustained | p95 < 200ms | load test |
Integration
- Informs design and quality-gate checks.
- architecture-risks-debt when scenarios reveal unacceptable risk.
- Parent: architecture.
Related Skills
pkuppens/sync-branch
testing
VerifiedTrustedCommunity
Syncs remote default branch locally (checkout, fetch --prune, pull) and returns to the previous branch when it still exists. Reports stashes and worktrees not yet handled. Use when the user asks to sync main, update default branch, fetch/pull origin, or run /sync-branch.
SKILL.mdUpdated Jun 6, 2026
pkuppens/azure-devops-work-items
tools
VerifiedTrustedCommunity
Creates, queries, updates, and links Azure Boards work items via az boards CLI. Use when filing ADO work items, running WIQL queries, or setting area path, iteration, tags, and assignee.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-repos
tools
VerifiedTrustedCommunity
Creates, reviews, and completes Azure Repos pull requests and branch policies via az repos CLI. Use when opening ADO PRs, setting required reviewers, or configuring build validation policies.
SKILL.mdUpdated May 29, 2026
pkuppens/azure-devops-pipelines
development
VerifiedTrustedCommunity
Guides Azure Pipelines YAML structure, build validation on PRs, and staged deployment with environments and approvals. Use when authoring azure-pipelines.yml or configuring CI/CD on Azure DevOps.
SKILL.mdUpdated May 29, 2026