odd-test-altitude-discipline

Verify tests map to outcome-altitude acceptance criteria to prevent silent failures.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/lukeivers/loam --skill odd-test-altitude-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odd-test-altitude-discipline
Source: https://github.com/lukeivers/loam/tree/main/plugins/dev-sdlc/skills/odd-test-altitude-discipline
Command: npx skills add https://github.com/lukeivers/loam --skill odd-test-altitude-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes docs/odd-llm-grounding.lean.md (resource) and feedback_test_outcome_altitude_required.md (resource) and plan-docs-author (resource) and plan-before-code-author (resource) and dispatch-brief-authoring (resource) and feedback_plan_before_code (resource) and feedback_loose_AC_text_fix_AC_not_implementation (resource) components.

What problem does it solve?

This Skill prevents silent failures where implementation-level verification passes but real-world outcomes diverge, ensuring robust traceability across development altitudes.

Core Features & Use Cases

  • Pre-arrangement detection: Identifies tests that do not verify real-world scenarios, ensuring outcome-altitude ACs are properly tested.
  • Risk-band classification: Guides automatic determination of when strict per-cycle testing is required based on risk assessment.
  • Use Case: When reviewing code or tests, this Skill assesses whether the existing tests sufficiently verify production behavior, reducing release risks and ensuring compliance with altitude traceability.

Quick Start

Review your test files and documentation to determine if your tests write state that the production code would produce and verify full end-to-end outcomes using this procedural rule.

Frequently Asked Questions about odd-test-altitude-discipline

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

FAQPage Schema
What is altitude traceability in automated verification and testing?

Altitude traceability in automated verification ensures tests properly map to outcome-altitude acceptance criteria. It prevents silent failures where implementation-level tests pass but real-world outcomes diverge, maintaining validation across development stages.

How do I prevent silent failures when implementation tests pass but outcomes diverge?

To prevent silent failures, verify that tests write state the production code would produce and validate full end-to-end outcomes. This ensures implementation-altitude tests properly map to outcome-altitude acceptance criteria.

How to classify risk bands for determining when strict per-cycle testing is required?

Classify risk bands by assessing whether existing tests sufficiently verify production behavior and reviewing test files against outcome-altitude acceptance criteria. This risk assessment guides automatic determination of strict per-cycle testing requirements.

Does this automated verification Skill require any dependencies to run?

No, this automated verification Skill requires no external dependencies to run. It operates independently to detect pre-arranged tests and ensure traceability across development altitudes for AI safety.

What is the best way to detect pre-arranged tests that do not verify real-world scenarios?

The best way to detect pre-arranged tests is assessing whether tests write state the production code would produce and verifying full end-to-end outcomes. This identifies tests failing to validate real-world scenarios.