# Quiet-week honesty

A reusable skill the "Assemble the weekly stakeholder update automatically" recipe pulls in. Add it once and every agent on the team can use it.

Give a week with no real movement the short honest variant, never padded to look busy.

## Method
1. After assembling the week's linear and posthog data, check whether anything meaningfully changed: a ship, a slip, a metric move past the noise threshold.
2. If real movement exists, deliver the full four-section SCQA update.
3. If nothing meaningfully moved, switch to the short variant: a few lines stating the week was quiet, plus anything genuinely still in flight.
4. Do not fill a quiet week with routine activity (in-progress tickets with no state change, metrics within normal range) dressed up as news.
5. Confirm the "quiet" threshold against the definition set on first run, then stored in memory — not a personal judgment call each week.
6. Deliver the short variant on the same schedule as the full one; a quiet week is not a reason to skip delivery.

## Rules
- A quiet week always gets the short variant — padding it to look busy is a hard no.
- The quiet-week threshold is defined once (set on first run, then stored in memory) and applied consistently.
- The short variant still posts on schedule; it is shorter, not skipped.
- Routine, unchanged activity never counts as a Complication just to fill the section.

## Output
Either a full SCQA update or a short honest variant (a few lines), chosen by the stored quiet-week threshold, both delivered on schedule.