kr-integrity

Audit KR engine specifications for technical defects and implementation readiness.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/rayanino/kr --skill kr-integrity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kr-integrity
Source: https://github.com/rayanino/kr/tree/main/skills/kr-integrity
Command: npx skills add https://github.com/rayanino/kr --skill kr-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill audits KR engine specifications for technical defects that domain experts might miss, ensuring the specification is ready for implementation and preventing costly errors or ambiguities during development.

Core Features & Use Cases

  • Technical Defect Auditing: Identifies ambiguities, knowledge corruption paths, silent failures, and incomplete error handling within KR engine specifications.
  • Implementation Readiness Check: Acts as a quality gate before development begins, ensuring the specification is clear enough for an engineer to build from without clarification.
  • Use Case: After a KR engine's owner has resolved all domain-specific comments, this Skill is used to perform a final technical review, catching issues like vague rules or unhandled error conditions before coding starts.

Quick Start

Use the kr-integrity skill to audit the KR engine SPEC for technical defects.

Frequently Asked Questions about kr-integrity

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

FAQPage Schema
How do I audit KR engine specifications for technical defects?

Audit KR engine specifications for technical defects by applying seven distinct analytical lenses to review rules, identify knowledge corruption, and verify contract consistency. This ensures the spec is implementation-ready before coding begins.

What technical defects should I look for in a specification readiness check?

A specification readiness check targets knowledge corruption, silent failures, ambiguous rules, and incomplete error handling. It verifies error path completeness and contract consistency to ensure engineers can build without further clarification.

When do I need to run a technical review on KR engine specs?

Run a technical review on KR engine specs after the owner has resolved all domain-specific comments. Use it as a final quality gate before development begins to catch vague rules or unhandled error conditions.

How do I check implementation readiness for ambiguous rules and silent failures?

Check implementation readiness by auditing for ambiguous rules and silent failures through seven analytical lenses. This verifies error path completeness and contract consistency, ensuring the specification is clear enough for development.

Does this specification audit catch unhandled error conditions before coding starts?

Yes, this specification audit catches unhandled error conditions before coding starts. It identifies incomplete error handling and silent failures, acting as a quality gate to ensure technical contract consistency.