product-integrity-engineer

Diagnose divergences between PLAN.md and runtime outputs, then orchestrate repairs via Conductor and Archivist.

Updated Apr 24, 2026

Search Tags:#auditing #orchestration #governance #integrity #root-cause #nlu

Ready to run

npx skills add https://github.com/Aurora-AI/Elysiancorpfront --skill product-integrity-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-integrity-engineer
Source: https://github.com/Aurora-AI/Elysiancorpfront/tree/main/.aurora/skills/product-integrity-engineer
Command: npx skills add https://github.com/Aurora-AI/Elysiancorpfront --skill product-integrity-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Senior Product Integrity Engineer monitors the project, PLAN.md, and all agents/skills to automatically detect and repair divergences between the expected behaviour and the delivered product. When issues arise, it activates repair workflows autonomously without waiting for explicit permission.

Core Features & Use Cases

Auto-diagnose divergences between PLAN.md and runtime outputs across agents and pipelines.
Root-cause analysis and orchestration of cross-skill repairs via Conductor and Archivist.
Full governance of integrity checks, escalation to Commandante when architectural decisions are violated.

Quick Start

Initiate an integrity check by issuing /verify-integrity or by triggering an error or divergence signal to begin automatic diagnosis and repair.

Frequently Asked Questions about product-integrity-engineer

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

FAQPage Schema

How do I automatically detect and repair divergences between planned and actual product behavior?▼

Automatically detect and repair divergences by running an integrity check that compares PLAN.md against runtime outputs across agents and pipelines, orchestrating cross-skill repairs to restore alignment and safety.

Why does my pipeline output exceed the planned scope during execution?▼

Pipeline output exceeding scope triggers an integrity breach diagnosis that root-causes the divergence between PLAN.md and actual behavior, then activates repair workflows via the conductor and archivist.

When do I need to run an integrity check on my agents and pipelines?▼

Run an integrity check during execution errors, integrity breaches, cognitive regressions, or when PLAN.md diverges from runtime outputs, by issuing /verify-integrity to begin automatic diagnosis and repair.

Does the product integrity repair process work without explicit permission or manual triggers?▼

Product integrity repair works autonomously by activating repair workflows without waiting for explicit permission, escalating to Commandante only when architectural decisions are violated.

What prerequisites are needed to diagnose integrity breaches across agents?▼

Diagnosing integrity breaches requires ensuring availability of PLAN.md, an active agents and skills registry, and triggers for repair workflows via the conductor and archivist before diagnosis begins.

What is the best way to govern integrity checks and escalate architectural violations?▼

Govern integrity checks by orchestrating cross-skill repairs through the conductor and archivist, escalating to Commandante when architectural decisions are violated to restore product alignment and safety.