skills.rest
guardiatechnology
guardiatechnologyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kata-dooc-validate

Validate agent DoOC evidence and generate a go/no-go decision.

Updated Sep 3, 2025
Search Tags:#validation#adr#observability#engineering workflow#agent promotion#go no-go#dooc
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-dooc-validate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-dooc-validate
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-dooc-validate
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-dooc-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that an agent is ready to be promoted from pre-operational to operational-concrete by enforcing the DoOC (Definition of Operational Concrete) evidence requirements before design work proceeds.

Core Features & Use Cases

  • Operational readiness verification: Confirms PoV origin, leading metric proof, lagging metric declaration, scope stability, and observability evidence.
  • Exception-aware gating: Supports controlled bypass paths for direct-entry, legacy-pov, and user-override while keeping mandatory items intact.
  • Deterministic audit snapshot: Produces a structured dooc/{agent}.md report and returns a final go/no-go decision for downstream orchestration.

Quick Start

Use the kata-dooc-validate Skill to validate DoOC readiness for an agent and generate the docs/{context}/dooc/{agent}.md snapshot, returning go or no-go based on the required evidence.

Frequently Asked Questions about kata-dooc-validate

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

FAQPage Schema
How do I validate agent promotion readiness for operational concrete deployment?▼

Agent promotion readiness is validated by verifying DoOC evidence across PoV origin, leading and lagging metrics, scope stability, observability, ownership, capacity, tier, and system-prompt stage to produce a go/no-go decision.

What is a DoOC validation gate and when do I need it?▼

DoOC validation is a gating mechanism needed before promoting an agent from pre-operational to operational-concrete, ensuring all evidence requirements are met before downstream design work proceeds.

How do I bypass mandatory validation criteria using ADR or PDR exceptions?▼

Exception clauses allow controlled bypass paths for direct-entry, legacy-pov, and user-override modes via ADR/PDR references, while keeping mandatory DoOC evidence items intact for operational promotion.

Can I generate an audit snapshot for direct-entry and legacy-pov agent modes?▼

Yes, DoOC validation supports with-pov, direct-entry, and legacy-pov entry modes, generating a structured audit snapshot report and returning a deterministic go or no-go decision.

What happens to the DoOC snapshot when validation returns a no-go decision?▼

The DoOC snapshot is persisted only on a go decision, meaning no-go results prevent the operational promotion and stop the agent from proceeding to downstream orchestration.

Related Skills

Explore More Software Engineering Skills→
guardiatechnologyguardiatechnology

kata-agent-overview-design

Generate overview.md and system-prompt.md for operational agents.

Official
Advanced
outcomeengoutcomeeng
1

reviewing-python

Review Python codebases adversarially and issue APPROVED or REJECTED verdicts.

Official
Advanced
chaimtchaimt

adlc-product-roadmap

Analyze feature specs and tasks.md to compute milestone progress and update PDR records.

Community
Advanced
trypanictrypanic

go-code-quality-check

Run go vet, staticcheck, and semgrep to generate severity-grouped fix plans.

Community
Advanced