quality-standard

Validate engineering deliverables with self-verification, edge-case analysis, and quality gates.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill quality-standard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-standard
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/quality-standard
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill quality-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures every engineering deliverable meets the rigor, completeness, and precision expected from a senior architect by enforcing self-verification, edge-case analysis, decomposition rules, anti-pattern detection, and explicit quality gates before delivery.

Core Features & Use Cases

  • Self-verification checklist: Completeness, precision, consistency, and executability checks to remove ambiguity and hidden assumptions.
  • Edge-case prompting: Systematic consideration of data, concurrency, failure modes, security, and operational edge cases relevant to the context.
  • Decomposition rules & task templates: Enforces atomic tasks, story formats with Given-When-Then acceptance criteria, and spike guidelines to reduce risk and rework.
  • Anti-pattern detection & quality gates: Flags architecture, code, data, process, and security anti-patterns and blocks delivery when critical quality gates fail.
  • Use Case: Apply to PR descriptions, tech specs, user stories, and code reviews to produce architect-grade artifacts that a mid-level engineer can execute without clarifying questions.

Quick Start

Apply the quality-standard protocol to the draft deliverable and produce a self-verified, architect-grade version including edge cases, decomposition, and explicit quality gates.

Frequently Asked Questions about quality-standard

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

FAQPage Schema
How do I enforce senior-architect quality on technical specifications and code reviews?

You can enforce senior-architect quality by applying self-verification checklists, edge-case prompting, and decomposition rules to validate completeness, precision, and executability across technical specifications and code reviews.

What is edge-case prompting and how does it improve engineering deliverables?

Edge-case prompting is the systematic consideration of data, concurrency, failure modes, security, and operational edge cases relevant to a deliverable's context. It improves engineering outputs by removing hidden assumptions and validating completeness before delivery.

How do I write user stories and task breakdowns that a mid-level engineer can execute without clarifying questions?

Write executable user stories and task breakdowns by applying decomposition templates that enforce atomic tasks, Given-When-Then acceptance criteria formats, and spike guidelines to reduce ambiguity and rework.

Can I use quality gates to block pull request delivery when critical architecture anti-patterns are detected?

Yes, you can use quality gates to flag architecture, code, data, process, and security anti-patterns, explicitly blocking pull request delivery when critical quality gate checks fail during self-verification.

What's the best way to validate completeness and executability in PR descriptions?

The best way to validate PR descriptions is applying a self-verification protocol that checks for completeness, precision, consistency, and executability while systematically considering failure modes and operational edge cases.