Signal & Feedback Surface Design

What problem does it solve?

Keeps scenarios self-explanatory by making states, transitions, and failures visible through clear signals so humans and agents can trust what happens without adding new observability stacks or guesswork.

Core Features & Use Cases

• Signal inventory & audit: Read the seams documentation and map key states, transitions, and failure modes to the signals that need to exist for each.
• Feedback alignment: Shape logs, status outputs, and UX messages so they speak the domain language, describe what the scenario is doing, and guide next steps.
• Telemetry & stability: Ensure deterministic events are logged, health indicators summarize the latest situation, tests assert critical signals, and the Observability Surface doc reflects the signal inventory.
• Use Case: After defining a workflow, ask this skill to highlight missing signals, noisy outputs, and the documentation updates needed to keep operators and future agents informed.

Quick Start

Ask the skill to analyze the current scenario and describe the required signals for states, transitions, and failures.