pipeline-reflection-ux skill

Overview

This skill improves router-facing pipeline and reflection narration to reduce noisy status churn and make Step 0 and reflection outcomes explicit. It standardizes when and how completion and reflection messages are emitted, and consolidates late notifications into a single, clear summary. The result is quieter, more actionable router output and easier debugging of pipeline flow.

How this skill works

The skill makes Step 0 visible in the router narration and ensures Step 0 completion is emitted before TaskList() is presented. It emits a one-line reflection outcome that includes the path to the generated report and batches post-pipeline notifications into a single summary message. Guardrail semantics remain unchanged, so blocking behavior is preserved.

When to use it

• When updating the router output contract to include explicit Step 0 and reflection messages.
• When changing reflection reminder wording to reduce repeated status churn.
• When implementing or adjusting post-pipeline notification batching to reduce noise.
• When debugging noisy taskupdate or routing logs that show repeated violations.
• Before releasing UX changes that affect pipeline narration or router-facing messages.

Best practices

• Emit Step 0 completion before emitting the TaskList to keep sequence explicit.
• Keep reflection outcomes to a single concise line with a report path for detail.
• Batch late or follow-up notifications into one summary to avoid repeated churn.
• Add or update tests before changing behavior and retest routing/taskupdate/read-safety suites.
• Verify debug-log counts improve for repeated violations to confirm noise reduction.

Example use cases

• Change router output contract to surface an explicit Step 0 start and completion event.
• Adjust reflection reminder text so it appears once with a clear outcome and report link.
• Combine multiple late pipeline notifications into one end-of-pipeline summary for the user.
• Run regression tests after modifications to ensure task update and routing behavior remain stable.
• Measure debug log frequency before and after changes to confirm reduced status churn.

FAQ