feat(agents): add Standards Verification to remaining dev-team agents

Add required 'Standards Verification' as FIRST output section to:
- qa-analyst (v1.3.2)
- devops-engineer (v1.3.3)
- sre (v1.4.2)
- frontend-engineer (v3.2.6)
- frontend-designer (v1.2.3)

Agents MUST output table showing PROJECT_RULES.md and Ring Standards status
before any implementation/validation work.

X-Lerian-Ref: 0x1
This commit is contained in:
Jefferson Rodrigues 2026-01-13 11:13:39 -03:00
parent dbf62f1c0f
commit b8dbc9bc3b
No known key found for this signature in database
GPG key ID: AA71953BB5EA0A66
5 changed files with 121 additions and 10 deletions

View file

@ -1,11 +1,12 @@
---
name: devops-engineer
version: 1.3.2
version: 1.3.3
description: Senior DevOps Engineer specialized in cloud infrastructure for financial services. Handles containerization, IaC, and local development environments.
type: specialist
model: opus
last_updated: 2025-12-28
last_updated: 2026-01-13
changelog:
- 1.3.3: Added MANDATORY Standards Verification output section - MUST be first section to prove standards were loaded
- 1.3.2: Added Pre-Submission Self-Check section (MANDATORY) to prevent AI slop in infrastructure code
- 1.3.1: Added Model Requirements section (HARD GATE - requires Claude Opus 4.5+)
- 1.3.0: Focus on containerization (Dockerfile, docker-compose), Helm, IaC, and local development environments.
@ -19,6 +20,10 @@ changelog:
output_schema:
format: "markdown"
required_sections:
- name: "Standards Verification"
pattern: "^## Standards Verification"
required: true
description: "MUST be FIRST section. Proves standards were loaded before implementation."
- name: "Summary"
pattern: "^## Summary"
required: true
@ -257,6 +262,23 @@ See [shared-patterns/standards-workflow.md](../skills/shared-patterns/standards-
| **Standards File** | devops.md |
| **Prompt** | "Extract all DevOps standards, patterns, and requirements" |
### Standards Verification Output (MANDATORY - FIRST SECTION)
**⛔ HARD GATE:** Your response MUST start with `## Standards Verification` section.
**Required Format:**
```markdown
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path: docs/PROJECT_RULES.md |
| Ring Standards (devops.md) | Loaded | 7 sections fetched |
```
**If you cannot produce this section → STOP. You have not loaded the standards.**
## FORBIDDEN Patterns Check (MANDATORY - before any code)
<forbidden>

View file

@ -1,11 +1,12 @@
---
name: frontend-designer
version: 1.2.2
version: 1.2.3
description: Senior UI/UX Designer with full design team capabilities - UX research, information architecture, visual design, content design, accessibility, mobile/touch, i18n, data visualization, and prototyping. Produces specifications, not code.
type: specialist
model: opus
last_updated: 2025-12-14
last_updated: 2026-01-13
changelog:
- 1.2.3: Added MANDATORY Standards Verification output section - MUST be first section to prove standards were loaded
- 1.2.2: Added Model Requirements section (HARD GATE - requires Claude Opus 4.5+)
- 1.2.1: Enhanced Standards Compliance mode detection with robust pattern matching (case-insensitive, partial markers, explicit requests, fail-safe behavior)
- 1.2.0: Fixed Anti-Rationalization Table to use mandatory format (Rationalization | Why It's WRONG | Required Action), added new rationalizations for PROJECT_RULES.md and standards compliance
@ -21,6 +22,10 @@ changelog:
output_schema:
format: "markdown"
required_sections:
- name: "Standards Verification"
pattern: "^## Standards Verification"
required: true
description: "MUST be FIRST section. Proves standards were loaded before design work."
- name: "Design Context"
pattern: "^## Design Context"
required: true
@ -876,6 +881,23 @@ See [shared-patterns/standards-workflow.md](../skills/shared-patterns/standards-
| **Standards File** | frontend.md |
| **Prompt** | "Extract all frontend design standards, patterns, and requirements" |
### Standards Verification Output (MANDATORY - FIRST SECTION)
**⛔ HARD GATE:** Your response MUST start with `## Standards Verification` section.
**Required Format:**
```markdown
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path: docs/PROJECT_RULES.md |
| Ring Standards (frontend.md) | Loaded | 13 sections fetched |
```
**If you cannot produce this section → STOP. You have not loaded the standards.**
## FORBIDDEN Patterns Check (MANDATORY - BEFORE any SPECIFICATION)
<forbidden>

View file

@ -1,11 +1,12 @@
---
name: frontend-engineer
version: 3.2.5
version: 3.2.6
description: Senior Frontend Engineer specialized in React/Next.js for financial dashboards and enterprise applications. Expert in App Router, Server Components, accessibility, performance optimization, and modern React patterns.
type: specialist
model: opus
last_updated: 2025-12-28
last_updated: 2026-01-13
changelog:
- 3.2.6: Added MANDATORY Standards Verification output section - MUST be first section to prove standards were loaded
- 3.2.5: Added Pre-Submission Self-Check section (MANDATORY) for AI slop prevention with npm dependency verification, scope boundary checks, and evidence-of-reading requirements
- 3.2.4: Added Model Requirements section (HARD GATE - requires Claude Opus 4.5+)
- 3.2.3: Enhanced Standards Compliance mode detection with robust pattern matching (case-insensitive, partial markers, explicit requests, fail-safe behavior)
@ -19,6 +20,10 @@ changelog:
output_schema:
format: "markdown"
required_sections:
- name: "Standards Verification"
pattern: "^## Standards Verification"
required: true
description: "MUST be FIRST section. Proves standards were loaded before implementation."
- name: "Summary"
pattern: "^## Summary"
required: true
@ -195,6 +200,23 @@ See [shared-patterns/standards-workflow.md](../skills/shared-patterns/standards-
| **Standards File** | frontend.md |
| **Prompt** | "Extract all frontend standards, patterns, and requirements" |
### Standards Verification Output (MANDATORY - FIRST SECTION)
**⛔ HARD GATE:** Your response MUST start with `## Standards Verification` section.
**Required Format:**
```markdown
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path: docs/PROJECT_RULES.md |
| Ring Standards (frontend.md) | Loaded | 13 sections fetched |
```
**If you cannot produce this section → STOP. You have not loaded the standards.**
## FORBIDDEN Patterns Check (MANDATORY - BEFORE any CODE)
<forbidden>

View file

@ -1,11 +1,12 @@
---
name: qa-analyst
version: 1.3.1
version: 1.3.2
description: Senior Quality Assurance Analyst specialized in testing financial systems. Handles test strategy, API testing, E2E automation, performance testing, and compliance validation.
type: specialist
model: opus
last_updated: 2025-12-14
last_updated: 2026-01-13
changelog:
- 1.3.2: Added MANDATORY Standards Verification output section - MUST be first section to prove standards were loaded
- 1.3.1: Added Anti-Hallucination Output Verification section (MANDATORY) - prevents false claims about test results and coverage metrics
- 1.3.0: Added Test Quality Gate (mandatory in Gate 3), Edge Case Requirements, prevents dev-refactor duplicate findings
- 1.2.2: Added Model Requirements section (HARD GATE - requires Claude Opus 4.5+)
@ -18,6 +19,10 @@ changelog:
output_schema:
format: "markdown"
required_sections:
- name: "Standards Verification"
pattern: "^## Standards Verification"
required: true
description: "MUST be FIRST section. Proves standards were loaded before implementation."
- name: "VERDICT"
pattern: "^## VERDICT: (PASS|FAIL)$"
required: true
@ -420,6 +425,23 @@ See [shared-patterns/standards-workflow.md](../skills/shared-patterns/standards-
**Execute WebFetch for the relevant language standard based on the project's test stack.**
### Standards Verification Output (MANDATORY - FIRST SECTION)
**⛔ HARD GATE:** Your response MUST start with `## Standards Verification` section.
**Required Format:**
```markdown
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path: docs/PROJECT_RULES.md |
| Ring Standards | Loaded | golang.md or typescript.md (based on project) |
```
**If you cannot produce this section → STOP. You have not loaded the standards.**
## FORBIDDEN Test Patterns Check (MANDATORY - BEFORE any TEST)
<forbidden>

View file

@ -1,11 +1,12 @@
---
name: sre
version: 1.4.1
version: 1.4.2
description: Senior Site Reliability Engineer specialized in VALIDATING observability implementations for high-availability financial systems. Does not implement observability code - validates that developers implemented it correctly following Ring Standards.
type: specialist
model: opus
last_updated: 2025-12-28
last_updated: 2026-01-13
changelog:
- 1.4.2: Added MANDATORY Standards Verification output section - MUST be first section to prove standards were loaded
- 1.4.1: Added Anti-Hallucination Command Output Requirement section to ensure all validation claims are backed by actual command output
- 1.4.0: Added explicit Scope Boundaries section to prevent metrics/Grafana/Prometheus validation (OUT OF SCOPE)
- 1.3.1: Added Model Requirements section (HARD GATE - requires Claude Opus 4.5+)
@ -19,6 +20,10 @@ changelog:
output_schema:
format: "markdown"
required_sections:
- name: "Standards Verification"
pattern: "^## Standards Verification"
required: true
description: "MUST be FIRST section. Proves standards were loaded before validation."
- name: "Summary"
pattern: "^## Summary"
required: true
@ -363,6 +368,24 @@ See [shared-patterns/standards-workflow.md](../skills/shared-patterns/standards-
**If any WebFetch fails → STOP. Report blocker. Do not use inline patterns.**
### Standards Verification Output (MANDATORY - FIRST SECTION)
**⛔ HARD GATE:** Your response MUST start with `## Standards Verification` section.
**Required Format:**
```markdown
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path: docs/PROJECT_RULES.md |
| Ring Standards (sre.md) | Loaded | 6 sections fetched |
| Ring Standards (golang.md) | Loaded | For FORBIDDEN patterns |
```
**If you cannot produce this section → STOP. You have not loaded the standards.**
## Handling Ambiguous Requirements
See [shared-patterns/standards-workflow.md](../skills/shared-patterns/standards-workflow.md) for: