# SCQA structure

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.

Assemble the weekly update in fixed Situation, Complication, Question, Answer order, every time.

## Method
1. Write Situation: the factual state of {{team}}/{{project}} right now, drawn from this week's real linear and posthog data.
2. Write Complication: what changed since last week — a slip, a blocker, a metric move — stated plainly, not softened.
3. Write Question: the one question the complication raises for the reader (e.g. "does this change the launch date?").
4. Write Answer: what the team is doing about it, or the decision already made.
5. Keep each section to a few sentences; this is a status update, not a narrative essay.
6. Re-read the four sections in order and confirm each answers only its own question, with no overlap.

## Rules
- Sections always appear in Situation, Complication, Question, Answer order — never reordered or merged.
- Complication only includes real state changes (linear or posthog); it does not include speculation about what might happen.
- Answer states an actual decision or next step, not a vague "we're looking into it."
- If there is no real complication this week, say so plainly rather than inventing one to fill the section.

## Output
A four-section update (Situation, Complication, Question, Answer), each grounded in this week's real linear and posthog data.