What problem does it solve?
When working on state machines, protocols, or critical data paths in Quickwit, ad-hoc coding can silently weaken safety invariants and user requirements. This Skill enforces a rigorous plan→spec→test→implement sequence so correctness properties are never silently dropped.
Core Features & Use Cases
- Verification-First Sequence: Requires defining the plan and invariants, checking ADRs, reading TLA+ specs, and writing DST tests before any implementation code.
- Spec Protection Protocol: Forbids silently weakening TLA+ invariants, Stateright properties, DST assertions, or English-language user requirements; mandates diagnosis and explicit user approval instead.
- Production-Path Testing: Requires validating features through the actual HTTP/gRPC stack (quickwit server, OTLP ingestion, REST API queries) rather than bypassed unit-level tests.
- Use Case: When implementing a new distributed protocol change in Quickwit, activate this mode to ensure the change is checked against existing TLA+ specs, covered by DST tests, and verified end-to-end through the real network stack.
Quick Start
Activate sesh mode and help me implement a new state machine change in Quickwit following the plan, spec, test, implement sequence.