time-claims-discipline

Validate time-based statements in operational reports against wall-clock durations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It verifies the accuracy of time-related assertions in operational status reports by preventing misstatements of elapsed durations and expected time estimates.

Core Features & Use Cases

  • Time Claim Verification: Checks claims like "minutes elapsed" or "expected hours" against real-time data to avoid errors caused by memory or assumptions.
  • Application Scope: Suitable for use in plan authoring, status updates, and audit reports involving any temporal statement.
  • Functionality: Enforces translation of human-developer-time estimates into AI wall-clock equivalents and verifies elapsed times using system timestamps.

Quick Start

Run this skill whenever you need to verify the correctness of time-related claims before stating or recording them in reports or plans.

Frequently Asked Questions about time-claims-discipline

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

FAQPage Schema
How do I verify elapsed time claims in operational status reports?

Verifying elapsed time claims in status reports involves checking stated durations against real-time system timestamps to prevent errors caused by memory or assumptions. This ensures all temporal statements reflect accurate wall-clock durations.

What is the best way to translate human time estimates into AI wall-clock equivalents?

Translating human time estimates into AI wall-clock equivalents involves enforcing a conversion protocol that maps developer-time expectations to actual operational durations. This translation prevents misinformation in plans and status updates by aligning human assumptions with machine execution speeds.

Can I audit expected hours and minutes elapsed in plan authoring without manual calculation?

Auditing expected hours and minutes elapsed in plan authoring can be automated by validating time-based statements against system timestamps. This eliminates manual calculation errors and enforces accurate temporal data recording before plans are finalized.

Does time claim verification work for audit reports involving any temporal statement?

Time claim verification works for audit reports involving any temporal statement by functioning across plan authoring, status updates, and audit documentation. It validates all time-based assertions to ensure they reflect accurate wall-clock durations before being officially recorded.

Why do time estimates in status updates often reflect inaccurate elapsed durations?

Time estimates in status updates often reflect inaccurate elapsed durations because they rely on human memory and assumptions rather than objective system timestamps. Verifying these claims against real-time data prevents such misinformation from propagating in operational reports.