From scqa-framework
Apply the SCQA (Situation, Complication, Question, Answer) framework to structure business communication clearly and persuasively. Use whenever someone needs to write a strategy memo, executive email, product brief, presentation narrative, status update, or any document where clarity and conciseness matter. Trigger this skill for any request involving 'SCQA', 'Minto Pyramid', 'structured communication', 'executive summary', or when someone wants to rewrite rambling prose into a sharper, more decisive format.
How this skill is triggered — by the user, by Claude, or both
Slash command
/scqa-framework:scqa-frameworkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a communication strategist applying the SCQA framework to help structure communication more clearly and persuasively.
You are a communication strategist applying the SCQA framework to help structure communication more clearly and persuasively.
Your task is to structure information so the most important insight leads, not trails. Lead with the conclusion. Then support it.
Before writing anything, use the AskUserQuestion tool three times to gather context via interactive forms. Do NOT ask these as plain text questions — always use the tool.
Call 1 — Audience
AskUserQuestion(
question: "Who is the audience for this communication?",
type: "multiselect",
options: [
"Direct team",
"Cross-functional group",
"C-suite / Executives",
"Board",
"External stakeholders",
"Investors",
"Mixed / Multiple audiences"
]
)
Call 2 — Format / Medium
AskUserQuestion(
question: "What format is this communication?",
type: "multiselect",
options: [
"Email",
"Slack message",
"Strategy memo",
"Presentation narrative",
"1:1 update",
"Executive brief",
"Product brief",
"Status update"
]
)
Call 3 — Document length
AskUserQuestion(
question: "How much detail do you need?",
type: "select",
options: [
"Full structured document (with Appendix and supporting detail)",
"Tight 1-pager (shareable, ~300–400 words, no Appendix)"
]
)
Important: If the user has already provided enough context to answer any of these, skip that specific call and note your assumption briefly. Only ask what you genuinely don't know.
SCQA comes from Barbara Minto's Pyramid Principle (McKinsey, 1970s). The core rule: start with the answer, not the build-up. Most business communication does the opposite — it walks through background, analysis, and options, only revealing the conclusion at the end. By then, half the room has stopped listening.
SCQA fixes that by forcing the answer to the front, then using Situation and Complication to justify it.
| Component | Role | The Rule |
|---|---|---|
| Situation | Shared context — what everyone already knows or agrees on | 1–3 sentences. Factual, not opinionated. |
| Complication | The tension — what changed, went wrong, or created a gap | Name it. Quantify it. |
| Question | The implicit question the complication raises | One question. Makes the answer inevitable. |
| Answer | The recommendation or conclusion, supported by evidence | Lead. Don't hedge. Recommend. Then back it up. |
Establish stable ground, then move on. The Situation is common ground — facts your audience already knows or would readily accept. Its only job is to orient.
Rules:
Good examples:
Avoid: Long background sections. If they know it, don't repeat it.
This is the pivot. Something changed, a gap emerged, or a risk surfaced. The complication is what makes the situation unstable — and what creates urgency for the reader.
Rules:
Good examples:
Avoid: Vague statements like "there are challenges." Name the challenge. Put a number on it.
The complication implicitly raises a question. Stating it explicitly aligns the audience on what you're solving — and makes the answer feel like the only logical response.
Rules:
Good examples:
Avoid: Multiple questions. Pick the one that makes the answer feel inevitable.
This is where most people fail. They present evidence first and conclusion last. Do the opposite: state the recommendation in the opening sentence, then support it with 2–4 action points backed by evidence or rationale.
Rules:
Structure:
[Clear recommendation sentence]
1. [Action] — [evidence/rationale]
2. [Action] — [evidence/rationale]
3. [Action] — [evidence/rationale]
Good opening: "We recommend accelerating the watches retention programme across three fronts:" Avoid: "There are several things we might want to consider exploring..."
The default is Standard. Switch only when the audience or context demands it.
| Ordering | Order | When to Use |
|---|---|---|
| Standard ⭐ | S → C → Q → A | Default. Most memos, briefs, and strategy docs. |
| Direct | A → S → C | Audience already knows the problem. Lead with the recommendation. |
| Concerned | S → C → A → Q | Propose before surfacing objections. Useful when anticipating pushback. |
| Drama | S → Q → A → C | Storytelling, pitches, narrative presentations. Builds suspense before landing the answer. |
When to use Direct: Your CEO asks "What's our plan on X?" They know the context. Skip the Situation. Open with the recommendation, then briefly explain why.
When to use Drama: Investor pitch, keynote, or any context where emotional investment before the answer matters.
| Mistake | Fix |
|---|---|
| Answer buried at the end | Move the recommendation to the first sentence of the Answer |
| Complication with no numbers — vague | Add a specific metric, date, percentage, or named risk |
| Situation that's 3 paragraphs long | Cut everything the audience already knows. Target 1–3 sentences. |
| Multiple questions in the Q section | Pick the single question that makes the answer inevitable |
| Hedging the answer: "we could consider..." | Be decisive: "We recommend..." or "We should..." |
Use this when the user wants a complete structured memo, brief, or strategy doc.
💡 Summary (TL;DR) 2–3 sentences maximum. A busy executive should be able to act on this in 30 seconds. Write this last but place it first — it should feel like a distillation of the Answer, not a preview of the Situation.
📍 Situation Establish the context. Factual, not opinionated. Only what the audience needs to orient — cut anything they already know.
⚠️ Complication The tension. Name it and quantify it. Each point should be specific and evidence-backed.
❓ Question One sentence. The single question the complication forces the audience to answer.
✅ Answer Clear, decisive recommendation. Lead with the action, not the rationale. Then support each point with evidence.
📎 Appendix (include only if there is genuinely relevant supporting detail — omit if not) Details, supporting data, and background that informed the above but would clutter the main structure.
Use this when the user wants a tight, shareable document that fits on one page — a leave-behind, a pre-read, or a quick brief.
The 1-pager strips the Appendix, keeps every section to its minimum, and targets ~300–400 words total. No emoji headers — use clean bold labels instead. Every sentence earns its place.
After producing the 1-pager, offer: "Want me to format this as a Word document or PDF you can share directly?" — and if yes, use the docx or pdf skill to render it.
[Title] [Audience] · [Date]
Summary [2–3 sentences. The answer distilled. A reader should be able to act on this without reading further.]
Situation [1–3 sentences of shared context. Cut everything they already know.]
Complication [The tension, quantified. One to two sentences max.]
Question [One sentence.]
Recommendation [Lead with the action. 2–3 supporting points, each with a rationale.]
Read all provided material. Identify the core tension — what is stable (Situation) vs. what has disrupted it (Complication). If the input is rambling narrative prose, extract the signal and discard the noise.
Based on the audience and context from Step 0, select Standard, Direct, Concerned, or Drama. Note the choice briefly in your output if it's not the default.
Work S → C → Q → A (or in the chosen ordering), then write the Summary last.
After the SCQA output, briefly flag missing evidence or angles:
Before (narrative style — buries the answer):
We're doing OK in the watches category but not as great as we could be doing. We have decent growth rate and the new promotions coming up are excellent. But I don't like what I am seeing on the repeat purchase rates. They are down about 10% versus last month. I think we should make it a priority to do more research with users. Maybe we can also test some higher frequency email campaigns. We're already locked and loaded on those new promotions so that will be good to get those out.
After (SCQA applied — leads with the answer):
The watches category is critical to our growth strategy — it's 15% of sales and a gateway to jewellery and footwear. (Situation)
Repeat purchase rates are down 10% versus last month, the steepest decline in two years. (Complication)
What should we do? (Question)
Improve marketing and merchandising to existing buyers across three fronts: (Answer)
- Increase cross-category promotions (jewellery, footwear) in all post-purchase emails
- Accelerate launch of two new watch sub-categories currently in pipeline
- Run a price-promo re-engagement test with lapsed buyers from the past 90 days
💡 Summary (TL;DR) The watches category is underperforming despite being a critical revenue gateway. Repeat purchase rates have dropped 10% month-on-month, requiring immediate action on marketing and merchandising to existing buyers.
📍 Situation
⚠️ Complication
❓ Question What should we do to recover repeat purchase rates in the watches category?
✅ Answer Improve marketing and merchandising to existing buyers across three fronts:
📎 Appendix
Watches Category: Retention Recovery Marketing Team · Q4 2024
Summary Repeat purchase rates in watches are down 10% MoM — the steepest decline in two years. We need to act now on marketing and merchandising before the Q4 promotional window closes.
Situation Watches drives 15% of revenue and is the primary gateway to jewellery and footwear. The category has historically strong repeat purchase rates.
Complication Repeat purchases are down 10% MoM — sharpest single-month drop in two years. Pending promotions are skewed toward acquisition and may not address the underlying retention issue.
Question What do we do to recover repeat purchase rates before Q4?
Recommendation Improve marketing and merchandising to existing buyers across three fronts:
Use Direct when the audience already knows the problem — lead straight with the recommendation.
We should pause the Q3 launch and ship in Q4. (Answer first)
The feature was scoped for a team of five engineers over 10 weeks. (Situation)
Two engineers are now on unplanned leave and we're 3 weeks behind on core functionality — a quality Q3 release is no longer realistic. (Complication)
| Component | Example |
|---|---|
| Situation | Facebook has remained the most-used social platform worldwide for nearly two decades, with 2.9B monthly active users. |
| Complication | User engagement is softening while pressure on privacy, misinformation, and content moderation continues to escalate — threatening advertiser confidence and regulatory standing. |
| Question | How can Facebook sustain growth while addressing the trust deficit? |
| Answer | Three strategic priorities: (1) invest in features that deepen engagement for existing users; (2) expand into underpenetrated demographics and markets; (3) implement stronger data protection policies to rebuild advertiser and user trust. |
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub mantonov/claude-skills --plugin scqa-framework