tla-trace-workflow

Estrellas209

Forks24

Actualizado20 de mayo de 2026 a las 04:22

TLA+ Trace Validation workflow. Use when: (1) validating if a trace matches a TLA+ spec, (2) debugging trace validation failures (TLC reports 'Temporal properties were violated' or validation stops unexpectedly), (3) fixing spec/trace inconsistencies after root cause is identified.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

specula-org

specula-org/Specula

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

5 archivos

SKILL.md

readonly

name	tla-trace-workflow
description	TLA+ Trace Validation workflow. Use when: (1) validating if a trace matches a TLA+ spec, (2) debugging trace validation failures (TLC reports 'Temporal properties were violated' or validation stops unexpectedly), (3) fixing spec/trace inconsistencies after root cause is identified.

Read guide.md for the full workflow methodology.

Más de este repositorio

mismo repositorio

bug-confirmation

specula-org/Specula

Bug confirmation and reproduction. Use when: (1) a bug has been found by model checking and needs code-level validation, (2) reproducing a bug in the real system to confirm it is not a false positive, (3) assessing whether a TLA+ counterexample maps to a real triggerable scenario.

2026-07-16209

tla-checking-workflow

specula-org/Specula

TLA+ Model Checking workflow. Use when: (1) running TLC model checking or simulation on a TLA+ spec, (2) analyzing counterexamples from invariant violations, (3) determining whether a violation is an invariant mismatch, a spec issue, or a real bug in the system implementation.

2026-07-16209

bug-classification

specula-org/Specula

Severity classification of Phase 4a results. Assign severity to REPRODUCED bugs and ENV_LIMITED/MASKED findings, while recording non-severity dispositions such as FALSE POSITIVE, PENDING REPAIR, DEFERRED, and INCOMPLETE.

2026-07-12209

validation-workflow

specula-org/Specula

TLA+ Verification workflow (orchestration). Use when: running the full verification loop — iterating between trace validation and model checking until both pass, ensuring spec faithfully models the system.

2026-07-12209

harness-generation

specula-org/Specula

Trace harness generation (Phase 2.5). Use when: (1) instrumenting a system's source code to emit NDJSON traces for TLA+ trace validation, (2) writing test scenarios that exercise protocol code paths, (3) producing the first batch of traces from instrumented tests.

2026-06-30209

code-analysis

specula-org/Specula

Code analysis for formal verification. Use when: (1) investigating a system implementation to identify what to model in TLA+, (2) performing bug archaeology on a codebase, (3) producing a modeling brief that guides spec generation.

2026-05-18209

Ejecuta cualquier Skill con un clic