
Interview Bookends
- 33 installs
- 75 repo stars
- Updated January 30, 2026
- nealcaren/social-data-analysis
Helps with ai & agent building tasks.
About
interview-bookends is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- interview-bookends
- AI & Agent Building
- AI-coding skill
Interview Bookends by the numbers
- 33 all-time installs (skills.sh)
- +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #8,975 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nealcaren/social-data-analysis --skill interview-bookendsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 33 |
|---|---|
| repo stars | ★ 75 |
| Last updated | January 30, 2026 |
| Repository | nealcaren/social-data-analysis ↗ |
What it does
Helps with ai & agent building tasks.
Files
Interview Bookends
You help sociologists write introductions and conclusions for interview-based research articles. Given the Theory section and Findings section, you guide users through drafting the framing prose that opens and closes the article.
When to Use This Skill
Use this skill when users have:
- A drafted Theory/Literature Review section
- A drafted Findings section
- Need help writing the Introduction and/or Conclusion
This skill assumes the intellectual work is done—the contribution is clear, the findings are established. The task is crafting the framing prose that positions the contribution and delivers on promises.
Connection to Other Skills
| Skill | Purpose | Key Output |
|---|---|---|
| interview-analyst | Analyzes interview data | Codes, patterns, quote database |
| interview-writeup | Drafts methods and findings | Methods & Findings sections |
| interview-bookends | Drafts introduction and conclusion | Complete framing prose |
This skill completes the article writing workflow.
Core Principles (from Genre Analysis)
Based on systematic analysis of 80 sociology interview articles from Social Problems and Social Forces:
1. Introductions Are Efficient; Conclusions Do Heavy Work
- Median introduction: 761 words, 6 paragraphs
- Median conclusion: 1,173 words, 8 paragraphs
- Ratio: Conclusions are 67% longer than introductions
- Introductions subtract (narrow to the gap); conclusions expand (project to significance)
2. Phenomenon-Led Openings Dominate (74%)
- Most introductions open with empirical phenomena, not questions
- Question-led openings are rare (1%)—they feel performative
- Theory-led openings cluster in theory-extension articles (30%)
- Show the puzzle; don't just assert it exists
3. Parallel Coherence Is Normative (66%)
- Introductions make promises; conclusions must keep them
- Escalation (20%) is acceptable—exceeding promises reads as discovery
- Deflation (6%) is penalized—overpromising damages credibility
- Callbacks to introduction are universal (100%)
4. Match Framing to Contribution Type
Five cluster styles require different approaches:
| Cluster | Intro Signature | Conclusion Signature |
|---|---|---|
| Gap-Filler | Short, phenomenon-led, data early | Long (2x), summary + implications |
| Theory-Extension | Theory-led (30%), framework early | Framework affirmation |
| Concept-Building | Long, motivate conceptual need | Balanced length, concept consolidation |
| Synthesis | Multiple traditions named | Integration claims, no deflation |
| Problem-Driven | Stakes-led (25%), policy focus | Escalation to implications |
Workflow Phases
Phase 0: Intake & Assessment
Goal: Review inputs, identify cluster, confirm scope.
- Read the Theory section to understand positioning and contribution type
- Read the Findings section to understand what was discovered
- Identify which cluster the article inhabits
- Confirm whether user needs introduction, conclusion, or both
Guide: phases/phase0-intake.md
Pause: Confirm cluster identification and scope before drafting.
---
Phase 1: Introduction Drafting
Goal: Write an introduction that opens the circuit effectively.
- Choose opening move type (phenomenon, stakes, case, theory, question)
- Establish stakes and context
- Identify the gap/puzzle
- Preview data and argument
- Include roadmap (optional but recommended for complex articles)
Guides:
phases/phase1-introduction.md(main workflow)techniques/opening-moves.md(opening strategies)clusters/(cluster-specific guidance)
Pause: Review introduction draft for coherence with theory section.
---
Phase 2: Conclusion Drafting
Goal: Write a conclusion that closes the circuit and projects significance.
- Open with restatement or summary (not the same words as intro)
- Recap key findings efficiently
- State contribution claims
- Integrate with prior literature
- Acknowledge limitations
- Project implications and future directions
- Craft callback to introduction
- End with resonant closing
Guides:
phases/phase2-conclusion.md(main workflow)techniques/conclusion-moves.md(structural elements)techniques/callbacks.md(closing the circuit)
Pause: Review conclusion for coherence with introduction.
---
Phase 3: Coherence Check
Goal: Ensure introduction and conclusion work together.
- Verify vocabulary echoes (key terms appear in both)
- Check promise-delivery alignment
- Assess coherence type (Parallel, Escalators, Bookends)
- Confirm callback is present and effective
- Calibrate ambition across sections
Guide: phases/phase3-coherence.md
---
Cluster Profiles
Reference these guides for cluster-specific writing:
| Guide | Cluster |
|---|---|
clusters/gap-filler.md | Gap-Filler Minimalist (38.8%) |
clusters/theory-extension.md | Theory-Extension Framework Applier (22.5%) |
clusters/concept-building.md | Concept-Building Architect (15.0%) |
clusters/synthesis.md | Synthesis Integrator (17.5%) |
clusters/problem-driven.md | Problem-Driven Pragmatist (15.0%) |
Technique Guides
| Guide | Purpose |
|---|---|
techniques/opening-moves.md | Five opening move types with examples |
techniques/conclusion-moves.md | Structural elements of conclusions |
techniques/callbacks.md | Closing the circuit effectively |
techniques/coherence-types.md | Parallel, Escalators, Bookends, Deflators |
techniques/signature-phrases.md | Common phrases for intros and conclusions |
Key Statistics (Benchmarks)
Introduction Benchmarks
| Feature | Typical Value |
|---|---|
| Word count | 600-950 words |
| Paragraphs | 4-8 |
| Opening move | Phenomenon-led (74%) |
| Data mention | Middle of section |
| Roadmap | Present in 40% |
Conclusion Benchmarks
| Feature | Typical Value |
|---|---|
| Word count | 900-1,450 words |
| Paragraphs | 6-10 |
| Opening move | Restatement (71%) |
| Limitations | Present in 69% |
| Future directions | Present in 76% |
| Callback | Required (100%) |
Coherence Benchmarks
| Type | Frequency | Meaning |
|---|---|---|
| Parallel | 66% | Deliver what you promised |
| Escalators | 20% | Exceed your promises |
| Bookends | 8% | Strong mirror structure |
| Deflators | 6% | Fall short (avoid) |
Prohibited Moves
In Introductions
- Opening with a direct question (unless theory-extension)
- Claiming the literature "has overlooked" without justification
- Promising more than the findings deliver
- Lengthy method description (save for Methods section)
- Excessive roadmapping (structure should feel natural)
In Conclusions
- Introducing new findings not in Findings section
- Forgetting to callback to introduction
- Over-hedging empirical claims
- Skipping limitations entirely (looks defensive)
- Ending with limitations (save strong closing for last)
- Repeating introduction verbatim (callback ≠ copy)
Output Expectations
Provide the user with:
- A drafted Introduction matching their cluster style
- A drafted Conclusion with all standard elements
- A coherence memo assessing promise-delivery alignment
- Revision suggestions if coherence issues detected
Invoking Phase Agents
Use the Task tool for each phase:
Task: Phase 1 Introduction Drafting
subagent_type: general-purpose
model: opus
prompt: Read phases/phase1-introduction.md and the relevant cluster guide, then draft the introduction for the user's article. The theory section and findings are provided. Match the opening move and length to cluster conventions.Model recommendations:
- Phase 0 (intake): Sonnet
- Phase 1 (introduction): Opus (requires narrative craft)
- Phase 2 (conclusion): Opus (requires integration)
- Phase 3 (coherence): Opus (requires evaluative judgment)
Cluster 3: Concept-Building Architect
Prevalence: 15.0% of corpus
Contribution logic: "Existing concepts fail; this article introduces a better one."
---
Identifying Concept-Building Articles
Your article is Concept-Building if:
- The Theory section develops new conceptual tools or typologies
- You introduce a new term with definitional precision
- Structure is building-blocks (concept → concept → synthesis)
- Subsections are moderate to heavy (3-5+)
- Literature balance is theory-heavy
- You may include a table or figure presenting the new framework
---
Introduction Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 800-1,000 words (longest cluster) |
| Paragraphs | 6-8 |
| Opening move | Phenomenon-led (78%) |
| Data mention | Late (33% in final third) |
| Roadmap | Higher rate (56%) |
Opening Move
Use phenomenon-led opening (78%)—but with a conceptual motivation.
"The unprecedented growth in rates of U.S. incarceration since the early 1970s has prompted scholars to rethink basic understandings of punishment, inequality, and the state."
The opening establishes the phenomenon, then pivots to the conceptual gap.
Structure
1. Opening (1-2 sentences): State phenomenon/stakes 2. Conceptual problem (1-2 paragraphs): Show why existing concepts fail 3. New concept introduction (1 paragraph): Name and briefly define the new term 4. Preview of concept development (1 paragraph): How the concept will be developed 5. Data preview (2-3 sentences): Can come late 6. Roadmap (1 paragraph): Recommended for complex conceptual work
Motivating Conceptual Need
The introduction must show why existing concepts are inadequate:
"Existing concepts—burnout, disengagement, defection—fail to capture [specific inadequacy]. The catch-all of 'exit' obscures [what it obscures]."
This sets up the contribution: a new concept that does what existing ones don't.
Introducing the New Concept
Name the concept clearly and define it precisely:
"We introduce the concept of 'carceral creep' to describe [definition]. Unlike [existing term], this concept captures [distinctive feature]."
Longer Introduction Justified
Concept-Building introductions are the longest because you must: 1. Establish the phenomenon 2. Show conceptual inadequacy 3. Introduce the new concept 4. Preview how it will be developed
---
Conclusion Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 800-900 words |
| Paragraphs | 4-6 |
| Intro:Conclusion ratio | ~1.03x (nearly balanced) |
| Limitations | Lower (44%) |
| Future directions | Lower (56%) |
Why Conclusions Are Shorter
The conceptual work is front-loaded. The introduction motivates the concept; the Theory section develops it; the Findings demonstrate it. By the conclusion, the concept is proven. The conclusion consolidates rather than expands.
Structure
1. Opening (1 paragraph): Concept affirmation or summary 2. Concept deployment (1-2 paragraphs): Recap how concept illuminated findings 3. Contribution claim (1 paragraph): What concept adds to field 4. Scope and applications (1 paragraph): Where else concept applies 5. Coda (2-3 sentences): Resonant closing
Opening Move
Summary opening is more common in Concept-Building (44% vs. 20% corpus average):
"In identifying the systematic aspects of identity work, we have developed the concept of [X] to capture [Y]."
Consolidating the Concept
The conclusion should affirm that the concept did analytic work:
"The concept of [X] proved useful for understanding [phenomenon]. Unlike [existing concepts], it captured [specific insight]."
Lower Limitations Rate
Concept-Building articles have lower limitations rates (44%). The focus is on affirming conceptual utility, not bounding claims.
---
Coherence Pattern
Dominant Type
Mixed: Parallel (44%), Bookends (22%), Deflators (22%)
Deflation Risk
Highest (22%): Ambitious conceptual promises are hardest to match.
Warning signs:
- Introduction promises a "new way of understanding" but findings show modest insight
- Concept is introduced grandly but only explains one pattern
- Existing concepts actually work fine for the data
Avoiding Deflation
1. Calibrate ambition: Don't claim more than the concept delivers 2. Show conceptual work: Demonstrate what the concept captures that others don't 3. Distinguish clearly: Make the difference from existing concepts concrete
Bookends Pattern
When it works, Concept-Building achieves Bookends (22%):
- Introduction poses conceptual problem
- Conclusion resolves it with new concept affirmed
---
Exemplar
10.1093_socpro_spz013 (Carceral Creep)
- Introduction: 861 words, stakes-led, introduces "carceral creep"
- Theory section: Building-blocks arc, table defining six stages
- Conclusion: 875 words, summary opening, concept deployed
- Ratio: 1.02 (balanced)
- Coherence: Bookends—opens with conceptual need, closes with concept affirmed
---
Writing Checklist
Introduction
- [ ] Longer introduction justified (800-1,000 words)
- [ ] Establish phenomenon/stakes
- [ ] Show why existing concepts fail
- [ ] Introduce new concept with precision
- [ ] Preview how concept will be developed
- [ ] Include roadmap (recommended)
- [ ] Data mention can be late
Conclusion
- [ ] Plan for balanced length (~800-900 words)
- [ ] Open with summary or concept affirmation
- [ ] Consolidate concept's utility
- [ ] Distinguish from existing concepts
- [ ] Define scope of applicability
- [ ] May have lower limitations emphasis
- [ ] End with resonant affirmation of concept
Coherence
- [ ] Calibrate introduction ambition carefully
- [ ] Concept must do real analytic work in findings
- [ ] Conclusion affirms what introduction promised
- [ ] Watch for deflation risk
- [ ] Key conceptual vocabulary must appear in both
Cluster 1: Gap-Filler Minimalist
Prevalence: 38.8% of corpus (most common)
Contribution logic: "We don't know about X; this study tells us."
---
Identifying Gap-Filler Articles
Your article is Gap-Filler if:
- The Theory section identifies an empirical gap the study fills
- Structure is funnel-shaped (broad context → specific gap)
- Theory is balanced or substantive-heavy (not theory-heavy)
- Subsections are minimal (0-2)
- The contribution is primarily empirical (documenting, describing)
---
Introduction Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 600-750 words (shortest cluster) |
| Paragraphs | 4-5 |
| Opening move | Phenomenon-led (77%) |
| Data mention | Early (40% in first third) |
| Roadmap | Optional (40%) |
Opening Move
Use phenomenon-led opening (77% of Gap-Fillers do this).
"Tasked with protecting children from abuse and neglect, U.S. child welfare authorities investigate the parents of over three million children each year."
Avoid theory-led; the contribution isn't theoretical.
Structure
1. Opening (1-2 sentences): State the phenomenon 2. Context (1 paragraph): Situate empirically, briefly note existing research 3. Gap (1 paragraph): "Yet we know less about..." / "Prior research focused on X, leaving Y unexplored" 4. Data preview (2-3 sentences): Mention data early 5. Argument preview (3-4 sentences): State findings concisely
Data Mention
Mention data early—within the first 3 paragraphs. Gap-Filler articles are empirically grounded; readers want to know your evidence base.
"Drawing on interviews with 83 poor mothers in [location], this study examines..."
Tone
- Efficient, not elaborate
- Modest but clear claims
- Don't oversell; the findings speak for themselves
---
Conclusion Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 1,200-1,400 words (longest relative to intro) |
| Paragraphs | 7-9 |
| Intro:Conclusion ratio | ~2.05x |
| Limitations | Present (74%) |
| Future directions | Present (77%) |
Why Conclusions Are Long
Gap-Filler articles have modest introduction promises. The conclusion must accumulate significance—transforming empirical findings into broader import. This takes space.
Structure
1. Restatement opening (1 paragraph): Return to puzzle 2. Findings summary (1-2 paragraphs): Recap key patterns 3. Literature integration (1-2 paragraphs): Connect to prior research 4. Contribution claim (1 paragraph): State what study adds 5. Limitations (1 paragraph): Bound the claims 6. Implications (1-2 paragraphs): Policy and/or theoretical 7. Future directions (1 paragraph): Next steps 8. Coda (2-3 sentences): Resonant closing
Accumulating Significance
Since the introduction was modest, the conclusion must build significance:
"These findings extend our understanding of [topic] in three ways. First, [contribution 1]. Second, [contribution 2]. Third, [contribution 3]. Together, they suggest that [broader implication]."
Limitations
Include explicit limitations (74% do). Be honest but not self-undermining:
"This study is limited to [population] in [context]. Whether these patterns hold for [other populations] remains an empirical question."
---
Coherence Pattern
Dominant Type
Parallel (69%): Deliver what you promise. Gap-Filler promises are modest, so they're easy to keep.
Deflation Risk
Low (3%): Modest promises are hard to underdeliver on.
Escalation
Some (23%): Findings may exceed expectations. Frame as discovery:
"Beyond documenting [stated goal], our data revealed [broader pattern], suggesting that..."
---
Exemplar
10.1093_sf_soad098 (Migrant Care Work)
- Introduction: 629 words, phenomenon-led, roadmap present
- Conclusion: 1,068 words, restatement opening, limitations present
- Ratio: 1.70
- Coherence: Parallel—consistent empirical focus throughout
---
Writing Checklist
Introduction
- [ ] Open with phenomenon (not theory, not question)
- [ ] Mention data within first 3 paragraphs
- [ ] Keep under 750 words
- [ ] State the gap clearly but briefly
- [ ] Preview findings concisely
Conclusion
- [ ] Plan for length (~1,200+ words)
- [ ] Open with restatement of puzzle
- [ ] Summarize findings without repeating Findings section
- [ ] Connect to prior literature
- [ ] Include limitations paragraph
- [ ] Include future directions
- [ ] Build significance through accumulation
- [ ] End with resonant coda, not limitations
Coherence
- [ ] Introduction promises are modest
- [ ] Conclusion delivers on all promises
- [ ] Callback to introduction present
- [ ] Key vocabulary echoes across sections
Cluster 5: Problem-Driven Pragmatist
Prevalence: 15.0% of corpus
Contribution logic: "Here's an important problem; here's what my research reveals about it."
---
Identifying Problem-Driven Articles
Your article is Problem-Driven if:
- The Theory section is organized around empirical puzzles or policy debates
- Theory enters in service of the problem (not leading)
- Structure may be problem-response or dialogue
- Literature balance is balanced or substantive-heavy
- The contribution is primarily empirical documentation or debate resolution
Two Sub-Types
5a: Debate-Resolvers
- Frame existing literature as characterized by competing positions
- Position study as resolving the tension
- "Scholars disagree about X; our data adjudicates"
5b: Empirical Documenters
- Heavy on descriptive context with light theoretical framing
- Often policy-relevant research
- "Here's what's happening with [understudied phenomenon]"
---
Introduction Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 750-950 words |
| Paragraphs | 5-7 |
| Opening move | Phenomenon (50%), Stakes (25%), Case (17%) |
| Data mention | Early to middle |
| Roadmap | Lower (33%) |
Opening Move
Stakes-led openings are common (25% vs. 11% corpus average):
"As global unaccompanied minor migration persists and expands, understanding how these youth navigate incorporation has never been more urgent."
Case-led openings work well (17%):
"In Cleveland, Ohio, the federal Department of Justice declared that the city's police department engaged in a 'pattern or practice' of using excessive force."
Structure
1. Opening (1-2 sentences): Stakes or case 2. Problem context (1-2 paragraphs): Policy background, empirical stakes 3. Theoretical positioning (1 paragraph): Light framing, debate if applicable 4. Research questions (2-3 sentences): What this study examines 5. Data preview (2-3 sentences): Can be early 6. Argument preview (3-4 sentences): Main findings
Stakes Emphasis
Problem-Driven articles emphasize why this matters in the real world:
"The stakes are high: [statistic]. Understanding [phenomenon] has implications for [policy/practice]."
Debate Framing (5a)
If debate-resolving, frame the competing positions:
"Scholars disagree about whether [position A] or [position B] better explains [phenomenon]. Some argue [A], while others contend [B]. This study provides evidence to adjudicate this debate."
Lower Roadmap Rate
Problem-Driven articles have lower roadmap rates (33%). The structure is often simpler—problem → evidence → implications.
---
Conclusion Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 1,100-1,400 words |
| Paragraphs | 6-9 |
| Intro:Conclusion ratio | ~1.38x |
| Opening move | Integration (25%)—higher than average |
| Limitations | Present (58%)—lower |
| Future directions | Present (67%) |
Why Integration Opening
Problem-Driven conclusions often open with literature integration (25%):
"Scholarship on [topic] has not fully captured [phenomenon]. Our analysis reveals..."
Structure
1. Opening (1 paragraph): Contribution claim or integration 2. Findings summary (1-2 paragraphs): Key empirical patterns 3. Policy implications (1-2 paragraphs): What this means for practice 4. Theoretical implications (1 paragraph): If applicable 5. Limitations (1 paragraph): Often brief 6. Future directions (1 paragraph) 7. Coda (2-3 sentences): Return to stakes
Policy Implications
Problem-Driven conclusions often develop policy implications more extensively:
"For practitioners, these findings suggest [recommendation]. Current policies that [X] may inadvertently [Y]. More broadly, [implication for policy domain]."
Escalation Common
Problem-Driven articles frequently escalate (33%)—extending from specific problem to broader implications:
"While our study focused on [specific context], these dynamics likely operate wherever [conditions]. The concept of [X] may prove useful for understanding [broader phenomenon]."
---
Coherence Pattern
Dominant Type
Parallel (50%) and Escalators (33%)
Escalation Rate
Highest (33%): Problem-driven research naturally extends to implications.
This is acceptable and expected. Real-world problems invite broader claims:
"Understanding [phenomenon] becomes increasingly urgent as [trend] reshapes [domain]."
Deflation Risk
Moderate (17%): Can occur when policy complexity prevents full resolution.
No Bookends
Zero (0%): Problem-Driven articles don't have strong mirror structure. They move from problem to implications rather than circling back.
---
Exemplar
10.1093_sf_soz110 (Residential Search Logics)
- Introduction: 355 words (brief!), stakes-led
- Conclusion: 1,325 words, broad stratification claims
- Ratio: 3.73 (highest escalation example)
- Coherence: Escalators—extends from housing search to inequality
---
Writing Checklist
Introduction
- [ ] Consider stakes-led or case-led opening
- [ ] Emphasize policy context and real-world urgency
- [ ] If debate-resolving, frame competing positions
- [ ] Data can be mentioned early
- [ ] Roadmap optional (structure often simpler)
- [ ] Connect to current events/policy debates if relevant
Conclusion
- [ ] Plan for moderate length (~1,100-1,400 words)
- [ ] Consider integration opening
- [ ] Develop policy implications substantively
- [ ] Connect to broader significance
- [ ] Escalation is acceptable and expected
- [ ] Return to stakes in coda
- [ ] Limitations can be brief
Coherence
- [ ] Stakes emphasis consistent across sections
- [ ] Policy implications developed (not just mentioned)
- [ ] Escalation is grounded in evidence
- [ ] Callback to opening stakes/case
- [ ] Problem is addressed, not just described
Cluster 4: Synthesis Integrator
Prevalence: 17.5% of corpus
Contribution logic: "These literatures have developed separately; I connect them."
---
Identifying Synthesis Articles
Your article is Synthesis if:
- The Theory section connects previously separate literatures
- You explicitly name multiple theoretical traditions
- Structure is building-blocks or dialogue
- Language includes "drawing together," "connecting," "integrating"
- The contribution is integration rather than new concept or gap-filling
---
Introduction Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 800-950 words |
| Paragraphs | 6-8 |
| Opening move | Phenomenon-led (71%) |
| Data mention | Variable |
| Roadmap | 43% |
Opening Move
Phenomenon-led is typical (71%), but the phenomenon sets up the integration:
"How do people make sense of their reliance on unjust institutions?"
The opening question or phenomenon must require multiple literatures to answer.
Structure
1. Opening (1-2 sentences): Phenomenon or question 2. First tradition (1 paragraph): Name and briefly describe tradition A 3. Second tradition (1 paragraph): Name and briefly describe tradition B 4. Integration preview (1 paragraph): How bringing them together illuminates 5. Data preview (2-3 sentences) 6. Argument preview (3-4 sentences): What the integration reveals
Naming Multiple Traditions
The introduction must name multiple traditions explicitly:
"To develop this analysis, we explicitly connect several theoretical traditions: recognition theory (Honneth, Lamont), legal cynicism (Kirk, Matsuda), and legal consciousness (Ewick, Silbey)."
This is not optional. Synthesis articles announce their integration upfront.
Previewing the Integration
Show what the integration accomplishes:
"By connecting [A] and [B], we reveal [insight]. What appeared as [separate phenomena] are better understood as [unified process]."
---
Conclusion Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 1,200-1,500 words |
| Paragraphs | 7-9 |
| Intro:Conclusion ratio | ~1.69x |
| Opening move | Integration (21%)—higher than average |
| Limitations | Present (71%) |
| Future directions | Present (79%) |
Why Integration Opening
Synthesis conclusions often open with literature positioning (21% vs. 9% corpus average):
"Recent research in cultural and political sociology has emphasized the role of recognition in shaping institutional trust..."
This signals: we promised integration, and here's how we delivered.
Structure
1. Integration opening (1 paragraph): Position in literature 2. Findings summary (1-2 paragraphs): Recap through integrative lens 3. Tradition-by-tradition (1-2 paragraphs): Return to each named tradition 4. Contribution claim (1 paragraph): What integration adds 5. Limitations (1 paragraph) 6. Implications (1 paragraph) 7. Future directions (1 paragraph) 8. Coda (2-3 sentences)
Returning to Each Tradition
The conclusion must return to each tradition named in the introduction:
"For scholars of [tradition A], our findings suggest... For researchers in [tradition B], the analysis reveals..."
If you named three traditions in the introduction, all three must appear in the conclusion.
---
Coherence Pattern
Dominant Type
Parallel (57%) and Escalators (29%)
Deflation Risk
Zero (0%): Synthesis articles never deflate.
Why? Integration promises are visible and verifiable. Either the literatures are connected or they're not. There's no graceful retreat from "I will integrate A and B" if you only deliver A.
Escalation Opportunity
Synthesis articles often escalate (29%)—synthesis reveals additional connections beyond what was promised:
"Beyond connecting [A] and [B], our analysis suggests a deeper affinity with [C]..."
---
Exemplar
10.1093_socpro_spaa017 (Recognition and Legal Cynicism)
- Introduction: 1,010 words, question-led, three traditions named
- Theory section: Building-blocks arc, theory-heavy
- Conclusion: 2,606 words (!), integrates all traditions
- Ratio: 2.58
- Coherence: Bookends—question posed, answer delivered through integration
---
Critical Requirements
The Three-Tradition Rule
If you name three traditions in the introduction, your conclusion must: 1. Reference all three 2. Show how findings relate to each 3. Demonstrate the integration
No Dropping Traditions
You cannot promise A + B + C and deliver only A + B. This is deflation.
Integration, Not Summary
The conclusion integrates—it doesn't just summarize:
Not this:
"We examined [A] and [B]."
This:
"By connecting [A] and [B], we revealed [insight]. Scholars of [A] have emphasized [X]; our analysis shows that [B] complicates this by [Y]."
---
Writing Checklist
Introduction
- [ ] Name multiple traditions explicitly
- [ ] Use "connecting," "drawing together," "integrating" language
- [ ] Preview what integration accomplishes
- [ ] Establish why traditions need connecting (they've developed separately)
- [ ] Make promises you can keep
Conclusion
- [ ] Plan for substantial length (~1,200-1,500 words)
- [ ] Consider integration opening move
- [ ] Return to EACH tradition named in introduction
- [ ] Show how findings speak to each tradition
- [ ] Demonstrate integration, not just summary
- [ ] State contribution clearly
Coherence
- [ ] Every tradition named in intro appears in conclusion
- [ ] Integration is visible and verifiable
- [ ] No deflation—cannot drop traditions
- [ ] Vocabulary echoes: tradition names must recur
- [ ] Consider escalation if synthesis reveals more than promised
Cluster 2: Theory-Extension Framework Applier
Prevalence: 22.5% of corpus
Contribution logic: "Framework X exists; I show it applies to Y."
---
Identifying Theory-Extension Articles
Your article is Theory-Extension if:
- The Theory section applies an established framework to a new domain
- You name a specific framework (often by author: "Bourdieu's...", "Goffman's...")
- The contribution is demonstrating the framework's utility in a new context
- Subsections are light to moderate (1-4)
- Literature balance is theory-heavy
---
Introduction Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 750-900 words |
| Paragraphs | 5-7 |
| Opening move | Theory-led (30%) or Phenomenon-led (50%) |
| Data mention | Late (after framework established) |
| Roadmap | 40% |
Opening Move
Theory-led openings are distinctive to this cluster (30% vs. 6% corpus average):
"The concept of the 'glass cliff' refers to the tendency for women and racial/ethnic minorities to be appointed to leadership positions during times of crisis."
But phenomenon-led is still common (50%):
"As discrimination in labor markets persists, scholars have sought to understand how disadvantaged groups navigate occupational barriers."
When to Use Theory-Led
Use theory-led opening when:
- The framework is well-known in the field
- The framework IS the backbone of the article
- Readers will recognize the framework immediately
Use phenomenon-led when:
- The phenomenon needs establishing before the framework
- You want to show the puzzle first, then introduce the framework as a tool
Structure
1. Opening (1-2 sentences): Framework or phenomenon 2. Framework exposition (1-2 paragraphs): Explain the framework 3. Extension gap (1 paragraph): Why it hasn't been applied to this domain 4. Why extension matters (1 paragraph): What we expect to learn 5. Data preview (2-3 sentences): Can be late 6. Argument preview (3-4 sentences): Framework + domain = insight
The Extension Move
The key rhetorical move is showing why extension is non-trivial:
"While [framework] has illuminated [domain A], scholars have not applied it to [domain B]. This is surprising because [reasons it might operate differently]. We extend [framework] to [domain B] to reveal [insight]."
---
Conclusion Signature
Key Statistics
| Feature | Typical Value |
|---|---|
| Word count | 1,000-1,200 words |
| Paragraphs | 6-8 |
| Intro:Conclusion ratio | ~1.41x |
| Limitations | Present (60%) |
| Future directions | Present (70%) |
Core Function
The conclusion must affirm framework utility:
"These findings demonstrate the utility of [framework] for understanding [new domain]. The framework illuminated [specific insight] that prior approaches missed."
Structure
1. Restatement opening (1 paragraph): Return to framework + domain 2. Framework affirmation (1-2 paragraphs): Show the framework worked 3. What extension revealed (1-2 paragraphs): Insights unique to this domain 4. Contribution claim (1 paragraph): What we now know about framework AND domain 5. Limitations (1 paragraph) 6. Future extensions (1 paragraph): Other domains where framework might apply 7. Coda (2-3 sentences)
Affirming the Framework
The conclusion must show the framework did analytic work:
Not this:
"We applied [framework] to [domain]."
This:
"[Framework] revealed [insight] that other approaches could not capture. Specifically, the concept of [X] illuminated [Y], demonstrating the framework's utility beyond its original domain."
Suggesting Further Extensions
Theory-Extension conclusions often point to other potential applications:
"These findings suggest [framework] may prove useful for understanding [other domain]. Future research might examine whether [mechanism] operates similarly in [other context]."
---
Coherence Pattern
Dominant Type
Parallel (60%) and Escalators (20%)
Deflation Risk
Moderate (10%): Frameworks don't always work as expected in new domains.
Warning signs:
- Findings don't clearly connect to framework concepts
- Framework feels "tacked on" rather than central
- Extension reveals the framework doesn't quite fit
Avoiding Deflation
1. Choose the right framework: If the framework doesn't fit, reconsider 2. Show conceptual connection: Link findings to framework vocabulary 3. Acknowledge if framework needed modification: This can BE the contribution
Escalation
Framework may prove more useful than expected (20%):
"Beyond confirming [framework]'s utility, our findings suggest [additional insight], extending [framework] in [new direction]."
---
Exemplar
10.1093_socpro_spab036 (Yellow Vests/Populism)
- Introduction: 1,281 words, case-led with populism framework
- Theory section: Populism framework exposition
- Conclusion: 1,454 words, restatement, framework affirmed
- Ratio: 1.14
- Coherence: Parallel—consistent populism analysis throughout
---
Writing Checklist
Introduction
- [ ] Consider theory-led opening if framework is well-known
- [ ] Name the framework explicitly
- [ ] Explain framework enough for readers to follow
- [ ] Show why extension to this domain is non-trivial
- [ ] Establish what we expect to learn
- [ ] Data can come late (after framework)
Conclusion
- [ ] Plan for moderate length (~1,000-1,200 words)
- [ ] Open with restatement of framework + domain
- [ ] Affirm framework utility explicitly
- [ ] Show what extension revealed
- [ ] Connect findings to framework vocabulary
- [ ] Point to other potential applications
- [ ] Include limitations
Coherence
- [ ] Framework appears in both intro and conclusion
- [ ] Framework concepts appear in findings
- [ ] Extension is demonstrated, not just claimed
- [ ] No deflation—framework must do work
- [ ] Vocabulary from framework recurs throughout
Phase 0: Intake & Assessment
You are assessing the user's materials and identifying the appropriate cluster style for their introduction and conclusion.
Why This Phase Matters
The introduction and conclusion must match the contribution type. A gap-filler article needs different framing than a concept-building article. Before drafting, you must understand what kind of contribution the user is making and align the framing accordingly.
Your Tasks
1. Gather Required Materials
Request these materials if not provided:
- Theory/Literature Review section (required)
- Findings section (required)
- Abstract (helpful but optional)
- Target journal (helpful for calibrating length/style)
2. Read and Analyze the Theory Section
Identify the positioning move:
| Positioning | Indicators |
|---|---|
| Gap-filling | "Little research has examined...", "We know less about...", identifies empirical gap |
| Theory-extension | Names specific framework, "X theory suggests...", applies existing framework to new domain |
| Concept-building | Introduces new term, critiques existing concepts, presents typology |
| Synthesis | Connects multiple literatures, "Drawing together...", integrates traditions |
| Debate-resolution | "Scholars disagree...", adjudicates between positions |
Identify the arc structure:
- Funnel (broad → specific)
- Building-blocks (concept → concept → concept)
- Dialogue (position 1 → position 2 → synthesis)
3. Read and Analyze the Findings Section
Identify:
- Main argument (the central claim)
- Key mechanisms/findings (the pillars)
- Empirical scope (who was studied, where, when)
- Level of theoretical ambition (description vs. explanation vs. new concept)
4. Assign Cluster Membership
Based on your analysis, assign the article to one of five clusters:
| Cluster | Key Indicators | Prevalence |
|---|---|---|
| Gap-Filler Minimalist | Empirical gap, funnel structure, substantive focus | 38.8% |
| Theory-Extension | Named framework, application to new domain | 22.5% |
| Concept-Building | New term introduced, conceptual critique | 15.0% |
| Synthesis Integrator | Multiple traditions connected, integration claims | 17.5% |
| Problem-Driven Pragmatist | Policy stakes, debate framing, empirical focus | 15.0% |
5. Confirm Scope
Ask the user:
- Do you need an introduction only, conclusion only, or both?
- What is your target word count for each section?
- Are there specific elements you want emphasized (e.g., policy implications)?
Cluster-Specific Implications
If Gap-Filler Minimalist:
- Introduction: Keep short (~600-700 words), phenomenon-led opening, data mention early
- Conclusion: Plan for length (~1,200-1,400 words), emphasis on implications
- Ratio: Conclusion should be ~2x introduction length
If Theory-Extension:
- Introduction: Consider theory-led opening, name framework early
- Conclusion: Framework affirmation, moderate length
- Ratio: Closer to 1.4x
If Concept-Building:
- Introduction: Longer to motivate conceptual need, include roadmap
- Conclusion: Can be proportionally brief if concept proven in findings
- Ratio: Nearly balanced (~1.0x)
- Risk: Higher deflation risk—calibrate ambition carefully
If Synthesis Integrator:
- Introduction: Name multiple traditions, preview integration
- Conclusion: Must return to each tradition, integration claims
- Risk: Zero deflation tolerance—if you promise synthesis, deliver it
If Problem-Driven Pragmatist:
- Introduction: Stakes-led or case-led opening, policy context
- Conclusion: Policy implications, may escalate to broader claims
- Opportunity: Escalation is common and acceptable
Output
Provide a summary with:
1. Cluster assignment and rationale (which cluster, why) 2. Contribution type (gap-filling, extension, building, synthesis, debate) 3. Main argument (one sentence) 4. Key findings (3-4 bullets) 5. Recommended approach:
- Introduction opening move
- Introduction target length
- Conclusion target length
- Key elements to include
6. Coherence considerations (what promises must the intro make for the conclusion to deliver?)
When You're Done
Return your assessment to the orchestrator and pause for user confirmation before proceeding to drafting.
Phase 1: Introduction Drafting
You are drafting the introduction for a sociology interview article. Your goal is to open the circuit—establish stakes, identify the puzzle, and preview the contribution.
Why This Phase Matters
The introduction is where authors position their contribution. It establishes the genre contract: "I will examine X using Y to illuminate Z." Everything that follows must honor this contract. A strong introduction makes the reader want to keep reading; a weak one loses them before the findings begin.
Required Reading
Before drafting, review:
techniques/opening-moves.md— The five opening move typesclusters/[relevant-cluster].md— Cluster-specific guidance- Phase 0 assessment — Cluster assignment and recommended approach
The Introduction Formula
Most sociology interview article introductions contain these moves in roughly this order:
| Move | Function | Typical Length |
|---|---|---|
| HOOK | Grab attention, establish stakes | 1-2 sentences |
| CONTEXT | Situate empirically | 1-2 paragraphs |
| GAP/PUZZLE | Identify what needs explaining | 1 paragraph |
| DATA PREVIEW | Introduce empirical approach | 2-4 sentences |
| ARGUMENT PREVIEW | State what paper will show | 2-4 sentences |
| ROADMAP | Outline paper structure | 0-1 paragraph (optional) |
Not every introduction includes every move, but the order is fairly consistent.
Step 1: Choose Your Opening Move
Based on cluster assignment:
Phenomenon-Led (74% of corpus)
Opens with an empirical statement about the world.
"Neighborhood is an important theme in research on prisoner reentry and desistance from offending, but scholars and practitioners typically use this to refer to a single location."
Best for: Gap-Filler, Concept-Building, Synthesis
Stakes-Led (11%)
Opens with an importance claim.
"The unprecedented growth in rates of U.S. incarceration since the early 1970s has prompted scholars to rethink basic understandings of punishment, inequality, and the state."
Best for: Problem-Driven, Gap-Filler
Case-Led (8%)
Opens with a concrete case or scene.
"In Cleveland, Ohio, the federal Department of Justice declared that the city's police department engaged in a 'pattern or practice' of using excessive force."
Best for: Problem-Driven, Synthesis
Theory-Led (6%)
Opens with a theoretical framework.
"The concept of the 'glass cliff' refers to the tendency for women and racial/ethnic minorities to be appointed to leadership positions during times of crisis."
Best for: Theory-Extension (30% use this)
Question-Led (1%)
Opens with a direct question.
"How do people make sense of their reliance on unjust institutions?"
Use sparingly: Rare and can feel performative. Only use when the question is genuinely compelling.
Step 2: Establish Context
After the opening move, situate the reader:
Empirical context: What is the phenomenon? Who is affected? What is the scope?
- Statistics, policy background, population characteristics
- Ground the abstract in concrete reality
Scholarly context: Where does this fit in the literature?
- Brief signaling of relevant traditions (save details for Theory section)
- Just enough to establish you know the field
Length: 1-2 paragraphs, ~150-250 words
Step 3: Identify the Gap/Puzzle
This is the turn—the moment you identify what needs explaining.
Gap-Filling Turn
"Yet we know remarkably little about how [population] experiences [phenomenon]. Prior research has focused on [X], leaving [Y] unexplored."
Extension Turn
"While [framework] has illuminated [domain A], scholars have not applied it to [domain B], where [reasons it might operate differently]."
Concept-Building Turn
"Existing concepts—[X, Y, Z]—fail to capture [specific aspect]. This article introduces the concept of [new term] to address this gap."
Synthesis Turn
"These literatures have developed largely in isolation. By drawing them together, we can see [new insight]."
Debate Turn
"Scholars disagree about whether [X] or [Y] better explains [phenomenon]. This study adjudicates by examining [case]."
Step 4: Preview Data and Argument
Briefly introduce your empirical approach and main claim:
Data preview:
"Drawing on [N] in-depth interviews with [population] in [location], conducted between [dates]..."
Argument preview:
"We argue that [main claim]. Specifically, we find that [finding 1], [finding 2], and [finding 3]."
Or:
"This article makes three contributions: First, ... Second, ... Third, ..."
Length: 1 paragraph, ~100-150 words
Step 5: Roadmap (Optional)
If the article is complex (multiple findings, synthesis of traditions), include a brief roadmap:
"The article proceeds as follows. We first review [literature], developing our theoretical framework. We then describe our methods and setting. The findings section demonstrates [X]. We conclude by discussing implications for [Y]."
When to skip: If the structure is obvious (standard empirical article), the roadmap can feel formulaic. Use your judgment.
Cluster-Specific Adjustments
Gap-Filler
- Keep short: 600-750 words
- Mention data early (within first 3 paragraphs)
- Efficient positioning; don't overexplain
Theory-Extension
- Consider theory-led opening
- Name the framework clearly
- Explain why extension to this domain matters
Concept-Building
- Longer introduction justified: 800-1,000 words
- Motivate why existing concepts fail
- Introduce the new concept with precision
- Include roadmap
Synthesis
- Name multiple traditions explicitly
- Preview the integration
- May be longer to set up connections
Problem-Driven
- Stakes-led or case-led opening works well
- Policy context can dominate
- Connect to real-world urgency
Prohibited Moves
- Opening with "This paper argues..." — Too abrupt; establish context first
- Lengthy literature review in introduction — Save for Theory section
- Overpromising — Don't claim more than findings deliver
- "The literature has overlooked..." — Without justifying why the overlooking matters
- Detailed methods in introduction — Save for Methods section
Calibrating Ambition
Match introduction claims to conclusion capacity:
| If you promise... | Conclusion must deliver... |
|---|---|
| "Extends theory X" | Affirmation that X works in new domain |
| "Introduces concept Y" | Demonstration that Y does analytic work |
| "Connects literatures A and B" | Integration of both in interpretation |
| "Resolves debate" | Evidence favoring one position |
The coherence rule: Whatever the introduction promises, the conclusion must keep.
Output
Provide: 1. Complete introduction draft (target word count based on cluster) 2. Annotation noting:
- Opening move type used
- Where the turn/gap occurs
- Key promises made (for conclusion coherence check)
3. Concerns or alternatives if multiple approaches could work
When You're Done
Return the draft to the orchestrator. Pause for user review before proceeding to conclusion drafting.
Phase 2: Conclusion Drafting
You are drafting the conclusion for a sociology interview article. Your goal is to close the circuit—resolve the puzzle, claim the contribution, and project significance.
Why This Phase Matters
The conclusion is where articles deliver on their promises. It transforms specific findings into broader significance. A strong conclusion makes readers remember the article; a weak one leaves them wondering "so what?"
Critical insight from genre analysis: Conclusions are substantially longer than introductions (median 1,173 vs. 761 words, ratio 1.67). This is because conclusions must accomplish more rhetorical tasks.
The Work Conclusions Must Do
| Task | Purpose | Typical Length |
|---|---|---|
| Restate puzzle | Remind reader of motivating question | 2-3 sentences |
| Summarize findings | Recap key discoveries | 1-2 paragraphs |
| Claim contribution | State what the article adds | 1 paragraph |
| Integrate with literature | Connect to prior work | 1-2 paragraphs |
| Acknowledge limitations | Bound the claims | 1 paragraph |
| Project implications | Draw out broader meaning | 1-2 paragraphs |
| Future directions | Point to next steps | 1 paragraph |
| Coda | Resonant closing | 2-4 sentences |
Step 1: Choose Your Opening Move
Conclusions typically open with one of three moves:
Restatement (71% of corpus)
Returns to the puzzle without explicit "we found" language.
"For poor mothers, the reach of child welfare surveillance extends beyond a single agency. This study has examined how fears of CPS reporting shape interactions with surveilling institutions..."
Summary (20%)
Opens with explicit findings recap.
"This article has demonstrated that exit from high-intensity movements operates through multiple distinct mechanisms..."
Integration (9%)
Opens with literature positioning.
"Recent research in cultural and political sociology has emphasized the role of recognition in shaping institutional trust..."
Recommendation: Restatement is the default. Summary works for complex articles with many findings. Integration works for Synthesis articles.
Step 2: Summarize Key Findings
Recap the main findings efficiently. This is NOT a rewrite of the Findings section—it's a distillation.
Structure options:
Enumerated:
"Three key findings emerge from this analysis. First, [finding 1]. Second, [finding 2]. Third, [finding 3]."
Narrative:
"The analysis reveals that [main claim]. Participants consistently [pattern 1], even as they [pattern 2]. This dynamic was shaped by [mechanism]."
Length: 150-250 words (1-2 paragraphs)
Avoid: Repeating quote-heavy prose from Findings. The conclusion uses author voice.
Step 3: Claim the Contribution
State explicitly what the article adds to knowledge. Match to cluster type:
Gap-Filler
"This study contributes to our understanding of [topic] by documenting [empirical insight]. Prior research focused on [X]; we show that [Y]."
Theory-Extension
"These findings demonstrate the utility of [framework] for understanding [new domain]. The framework illuminates [specific insight] that prior approaches missed."
Concept-Building
"The concept of [new term] provides analytic leverage for understanding [phenomenon]. Unlike [existing concepts], it captures [distinctive feature]."
Synthesis
"By connecting [tradition A] and [tradition B], we reveal [integrated insight]. What appeared as separate phenomena are better understood as [unified process]."
Problem-Driven
"This analysis advances debates over [topic] by showing [resolution]. The evidence suggests that [position] is more accurate, but [nuance]."
Step 4: Integrate with Prior Literature
Connect your findings to existing scholarship. This demonstrates you understand the field and positions your contribution within it.
Approaches:
Confirming prior work:
"These findings align with [Author]'s argument that [claim]. We extend this insight by showing [extension]."
Challenging prior work:
"Contrary to [Author]'s emphasis on [X], we find that [Y] plays a more central role. This suggests [implication]."
Synthesizing:
"Our findings bridge [Scholar A]'s focus on [X] with [Scholar B]'s attention to [Y], revealing how [connection]."
Length: 1-2 paragraphs, including citations
Step 5: Acknowledge Limitations
Limitations are expected (present in 69% of conclusions). Handle them confidently, not apologetically.
What to acknowledge:
- Sample characteristics (size, selection, demographics)
- Geographic/temporal scope
- Methodological constraints
- What you can and cannot claim causally
What NOT to do:
- Endless hedging
- Undermining your own contribution
- Listing every conceivable limitation
- Ending the conclusion with limitations
Example:
"This study has limitations. Our sample of [N] [population] in [location] may not generalize to [other contexts]. We cannot establish causal ordering between [X and Y]. Future research with [different design] could address these constraints."
Length: 1 paragraph, ~100-150 words
Step 6: Project Implications
Draw out what your findings mean beyond the immediate study. Options include:
Theoretical implications:
"These findings suggest that theories of [topic] should attend more carefully to [factor]. The [mechanism] we identify may operate in other contexts where [conditions]."
Policy implications:
"For practitioners, these findings suggest [recommendation]. Current policies that [X] may inadvertently [Y]."
Broader significance:
"More broadly, this study illuminates [larger phenomenon]. As [trend] continues, understanding [mechanism] becomes increasingly important."
Length: 1-2 paragraphs
Step 7: Point to Future Directions
Identify productive next steps. This is NOT a limitations dump—it's a research agenda.
Strong future directions:
- Build on your contribution ("Future research might examine whether [mechanism] operates similarly in [new context]")
- Address what you couldn't ("Longitudinal designs could establish [causal claim]")
- Extend the framework ("The concept of [X] could be applied to [Y]")
Length: 1 paragraph
Step 8: Craft the Callback and Coda
The callback returns to the introduction—same themes, vocabulary, or images. This is REQUIRED (100% of articles have callbacks).
Callback strategies:
- Return to opening case or image
- Echo key vocabulary from introduction
- Answer the question posed in opening (if question-led)
- Complete the circuit explicitly
The coda provides resonant closure. Options:
Clinching quote:
As Maria put it, "It's not that we don't trust them—it's that we can't afford to."
Mic-drop sentence:
"What the literature calls 'exit' may be better understood as dispersal: the movement identity spreading into the broader world, carried by individuals who remain, in some fundamental sense, what the movement made them."
Return to stakes:
"Understanding these dynamics is increasingly urgent as [trend] reshapes [domain]."
Avoid ending with:
- Limitations (too weak)
- Generic "more research is needed"
- Fading repetition of findings
Cluster-Specific Adjustments
Gap-Filler
- Longer conclusion (target 1,200-1,400 words)
- Accumulate significance from modest claims
- Emphasize implications to build contribution
Theory-Extension
- Moderate length (1,000-1,200 words)
- Framework affirmation central
- May extend framework to additional domains
Concept-Building
- Can be shorter if concept proven in Findings (~800-900 words)
- Consolidate concept's utility
- Define scope of concept applicability
Synthesis
- Must return to each tradition named in intro
- No deflation—integration must be delivered
- Often longer due to multi-tradition integration
Problem-Driven
- May escalate to broader policy implications
- Stakes-heavy closing
- Connect back to real-world urgency
Output
Provide: 1. Complete conclusion draft (target word count based on cluster) 2. Annotation noting:
- Opening move used
- Where callback occurs
- Key promises from intro that are addressed
- Coherence type (Parallel, Escalators, Bookends)
3. Coherence check against introduction promises
When You're Done
Return the draft to the orchestrator for coherence review in Phase 3.
Phase 3: Coherence Check
You are reviewing the introduction and conclusion together to ensure they work as a unified rhetorical system.
Why This Phase Matters
The introduction makes promises; the conclusion must keep them. Articles fail when these sections are written in isolation. This phase ensures the circuit is closed—that what opens in the introduction resolves in the conclusion.
The Coherence Principle
From genre analysis of 80 sociology articles:
| Coherence Type | Frequency | Description | Assessment |
|---|---|---|---|
| Parallel | 66% | Conclusion delivers what intro promised | Normative |
| Escalators | 20% | Conclusion exceeds intro scope | Acceptable |
| Bookends | 8% | Strong mirror structure | Effective |
| Deflators | 6% | Conclusion falls short | Problematic |
The goal: Achieve Parallel, Escalators, or Bookends. Avoid Deflators.
Step 1: Extract Promises from Introduction
Read the introduction and identify every promise made:
| Promise Type | Example | Conclusion Must Deliver |
|---|---|---|
| Empirical claim | "We examine how X experience Y" | Evidence about X's experience of Y |
| Framework application | "Using Z framework..." | Findings interpreted through Z |
| New concept | "We introduce the concept of Q" | Q demonstrated analytically |
| Synthesis claim | "Connecting A and B literatures" | Both A and B integrated |
| Debate resolution | "Adjudicating between X and Y" | Evidence favoring one position |
| Scope claim | "Among [population] in [context]" | Findings bounded to that scope |
Create a promise inventory: 1. List each promise 2. Note where in conclusion it's addressed 3. Flag any unaddressed promises
Step 2: Verify Vocabulary Echoes
Key terms from the introduction should reappear in the conclusion. Check for:
Concept vocabulary:
- Does the same terminology appear? (e.g., "recognition," "legal cynicism")
- Are concepts used consistently?
Phenomenon vocabulary:
- Same population descriptors
- Same setting references
Argument vocabulary:
- Same mechanism names
- Same contribution framing
Red flag: If major terms from introduction don't appear in conclusion, the callback may be weak.
Step 3: Assess Callback Quality
The callback is REQUIRED. Evaluate it on:
Presence
- Does the conclusion explicitly return to introduction themes?
- Is there a moment where the reader recognizes "this is what we started with"?
Strength
| Weak Callback | Strong Callback |
|---|---|
| Vague thematic similarity | Explicit vocabulary echo |
| Different framing | Same puzzle, now resolved |
| New angle introduced | Completing the circuit |
Placement
- Callbacks typically appear in the opening paragraph of conclusion (restatement)
- And in the closing paragraph (coda)
- Double callbacks (opening + closing) create Bookends effect
Step 4: Check Promise-Delivery Alignment
For each promise, assess delivery:
| Promise | Delivered? | Assessment |
|---|---|---|
| [Promise 1] | Yes/Partial/No | Notes |
| [Promise 2] | Yes/Partial/No | Notes |
| [Promise 3] | Yes/Partial/No | Notes |
If All Promises Delivered → Parallel (good)
The article does what it says. This is normative and appropriate.
If Conclusion Exceeds Promises → Escalators (acceptable)
The findings turned out bigger than anticipated. Frame as discovery, not overclaiming.
Example escalation language:
"Beyond our initial focus on [X], the data revealed [broader pattern]..."
"These findings have implications beyond [original scope], suggesting..."
If Promises Underdelivered → Deflators (problematic)
Options: 1. Revise introduction to make more modest claims 2. Strengthen conclusion to deliver on promises 3. Acknowledge explicitly if scope narrowed during research
Step 5: Assess Coherence Type
Based on your analysis, classify the draft:
Parallel
- All promises delivered
- Vocabulary echoes present
- Callback present and effective
- Verdict: Ready for polish
Escalators
- Promises delivered plus additional claims
- Conclusion makes broader contributions
- Escalation is justified and grounded
- Verdict: Acceptable if escalation is earned
Bookends
- Strong mirror structure
- Opening image/question returns in closing
- Symmetrical feel
- Verdict: Highly effective when achieved
Deflators
- One or more promises unaddressed
- Conclusion hedges relative to introduction
- Contribution feels smaller than promised
- Verdict: Requires revision
Step 6: Specific Checks
Contribution Match
| Introduction Claims | Conclusion Claims | Match? |
|---|---|---|
| [Contribution type] | [Contribution type] | Yes/No |
Scope Match
| Introduction Scope | Conclusion Scope | Match? |
|---|---|---|
| [Population, context] | [Population, context] | Yes/No |
Theory Match
| Introduction Frameworks | Conclusion Frameworks | Match? |
|---|---|---|
| [Theories named] | [Theories integrated] | Yes/No |
Revision Recommendations
If coherence issues found, provide specific guidance:
For Weak Callbacks
- Add explicit return to introduction vocabulary
- Echo opening image in closing
- Reference the original puzzle directly
For Unfulfilled Promises
- Either deliver in conclusion or revise introduction
- Don't leave promises hanging
- Acknowledge any scope changes explicitly
For Deflation
- Strengthen conclusion claims if evidence supports
- Or moderate introduction claims if necessary
- Match ambition to capacity
For Unearned Escalation
- Ground broader claims in evidence
- Use hedging language if appropriate
- Ensure escalation is warranted
Output
Provide a Coherence Memo with:
1. Promise Inventory: List of all introduction promises 2. Delivery Assessment: Which promises delivered, which not 3. Callback Evaluation: Presence, strength, placement 4. Coherence Classification: Parallel/Escalators/Bookends/Deflators 5. Revision Recommendations: Specific changes needed 6. Final Assessment: Ready for submission or needs revision
Coherence Checklist
Before finalizing, confirm:
- [ ] Every major promise in introduction is addressed in conclusion
- [ ] Key vocabulary from introduction appears in conclusion
- [ ] Callback is present and recognizable
- [ ] Conclusion scope matches introduction scope
- [ ] All frameworks/theories named in intro are integrated in conclusion
- [ ] Contribution type is consistent across sections
- [ ] No deflation (claims don't shrink)
- [ ] Any escalation is earned and grounded
When You're Done
Return the coherence memo to the orchestrator with: 1. Overall assessment (Pass/Revise) 2. Specific revision instructions if needed 3. Confidence level in current draft
If revisions needed, cycle back to Phase 1 or 2 as appropriate.
Opening Move Types
This guide details the five types of opening moves used in sociology interview article introductions, with frequencies from genre analysis.
Overview
| Opening Move | Frequency | Best For |
|---|---|---|
| Phenomenon-led | 74% | Gap-Filler, Concept-Building, Synthesis |
| Stakes-led | 11% | Problem-Driven, Gap-Filler |
| Case-led | 8% | Problem-Driven, Synthesis |
| Theory-led | 6% | Theory-Extension |
| Question-led | 1% | Rare; use sparingly |
---
1. Phenomenon-Led Opening (74%)
Opens with an empirical statement about the world. The most common approach.
What It Does
- Grounds the article in observable reality
- Establishes the phenomenon before the puzzle
- Shows rather than tells
- Signals empirical focus
Structure
1. State the phenomenon 2. Provide context/prevalence 3. Move toward the puzzle
Examples
Simple statement:
"Neighborhood is an important theme in research on prisoner reentry and desistance from offending, but scholars and practitioners typically use this to refer to a single location."
Statistical grounding:
"Between 50 and 67 percent of U.S. households have a pet."
Population focus:
"Tasked with protecting children from abuse and neglect, U.S. child welfare authorities investigate the parents of over three million children each year."
Trend statement:
"The self-contained, self-reliant nuclear family persists as the archetypal family form, despite its declining prevalence."
When to Use
- Default choice for most articles
- When the phenomenon itself is inherently interesting
- When you want to establish empirical grounding before theory
- When readers need to see the puzzle in the world before the literature
When to Avoid
- When the framework IS the contribution (use theory-led)
- When stakes need immediate emphasis (use stakes-led)
---
2. Stakes-Led Opening (11%)
Opens with an importance claim about why the topic matters.
What It Does
- Creates immediate urgency
- Signals policy relevance
- Engages readers who care about real-world impact
- Establishes significance before details
Structure
1. State why this matters 2. Contextualize the stakes 3. Move to specific focus
Examples
Scale emphasis:
"The unprecedented growth in rates of U.S. incarceration since the early 1970s has prompted scholars to rethink basic understandings of punishment, inequality, and the state."
Policy urgency:
"As global unaccompanied minor migration persists and expands, understanding how these youth navigate incorporation has never been more urgent."
Social significance:
"Decades of research have made the case that neighborhoods are important contexts for children's development, shaping their educational achievement, health, and life chances."
When to Use
- Problem-Driven articles with policy implications
- When the "so what?" needs emphasis
- When reader motivation might flag without urgency
- When connecting to current events or policy debates
When to Avoid
- When stakes feel manufactured or overblown
- When the phenomenon should speak for itself
- When you risk seeming self-important
---
3. Case-Led Opening (8%)
Opens with a concrete case, scene, or vignette.
What It Does
- Creates narrative engagement
- Grounds abstractions in specifics
- Signals qualitative, context-rich approach
- Makes the phenomenon vivid
Structure
1. Describe specific case/scene 2. Zoom out to broader pattern 3. Move to puzzle/question
Examples
Policy case:
"In Cleveland, Ohio, the federal Department of Justice declared that the city's police department engaged in a 'pattern or practice' of using excessive force."
Historical moment:
"On Tuesday, November 27, 2018, President Emmanuel Macron stood outside of the Elysee Palace delivering a speech on 'ecological transition.'"
Composite vignette:
"When Maria arrived at the welfare office, she knew the routine: arrive early, bring all documents, expect to wait."
When to Use
- Problem-Driven articles grounded in specific context
- When the case IS the entry point to broader analysis
- When narrative engagement matters
- When the case exemplifies the puzzle
When to Avoid
- When the case might seem idiosyncratic
- When you can't connect it to broader patterns
- When abstractions need emphasis over particulars
---
4. Theory-Led Opening (6%)
Opens with a theoretical framework or concept.
What It Does
- Signals theoretical contribution
- Establishes framework before application
- Appeals to theory-oriented readers
- Centers the framework as the article's backbone
Structure
1. Introduce the framework/concept 2. Explain its utility 3. Set up the extension or application
Examples
Named concept:
"The concept of the 'glass cliff' refers to the tendency for women and racial/ethnic minorities to be appointed to leadership positions during times of crisis."
Theoretical tradition:
"Recognition theory suggests that social identities are shaped through intersubjective processes of acknowledgment and validation."
Framework introduction:
"Bourdieu's concept of cultural capital has proven remarkably productive for understanding educational inequality."
When to Use
- Theory-Extension articles (30% of this cluster uses it)
- When the framework is well-known and central
- When the contribution IS applying the framework
- When readers expect theoretical framing
When to Avoid
- When the framework is obscure (define later)
- When empirical grounding is needed first
- When the phenomenon is more compelling than the theory
---
5. Question-Led Opening (1%)
Opens with a direct question.
What It Does
- Poses the puzzle immediately
- Signals inquiry-driven approach
- Can create engagement if question is compelling
- Mirrors how research actually begins
Structure
1. Ask the question 2. Explain why it matters 3. Preview the answer
Examples
Paradox question:
"How do people make sense of their reliance on unjust institutions?"
Process question:
"What happens when social movement organizations must choose between their ideals and their survival?"
Puzzle question:
"Why do residents of high-crime neighborhoods call the police despite widespread distrust?"
Why It's Rare (1%)
- Can feel rhetorically performative
- Implies the answer is unknown (requires justification)
- "Showing" is usually more persuasive than "asking"
- Questions can feel like a gimmick
When to Use
- When the question is genuinely compelling
- When the paradox is the central puzzle
- When the question format captures something assertions don't
- Synthesis articles where the question bridges literatures
When to Avoid
- As a default (it's overused in student writing)
- When the question isn't actually puzzling
- When showing would be more effective than asking
---
Choosing Your Opening Move
Decision Tree
1. Is the framework central to contribution?
- Yes → Consider Theory-Led
- No → Continue
2. Is there immediate policy/social urgency?
- Yes → Consider Stakes-Led
- No → Continue
3. Is a specific case the entry point?
- Yes → Consider Case-Led
- No → Continue
4. Is the phenomenon inherently interesting?
- Yes → Use Phenomenon-Led (default)
- Uncertain → Use Phenomenon-Led
5. Is there a genuinely compelling paradox?
- Yes → Consider Question-Led (rare)
- No → Don't force it
Cluster Recommendations
| Cluster | Primary | Secondary |
|---|---|---|
| Gap-Filler | Phenomenon | Stakes |
| Theory-Extension | Theory (30%) | Phenomenon (50%) |
| Concept-Building | Phenomenon | Stakes |
| Synthesis | Phenomenon | Case |
| Problem-Driven | Stakes (25%) | Case (17%) |
Signature Phrases for Introductions and Conclusions
Common phrases and formulations from sociology interview articles, organized by function.
---
Introduction Phrases
Opening Moves
Phenomenon-led:
- "[Topic] has become increasingly central to..."
- "[N] percent of [population]..."
- "In recent decades, [trend] has..."
- "[Population] face a distinctive challenge..."
- "The [phenomenon] remains a persistent feature of..."
Stakes-led:
- "Few social problems have generated as much..."
- "Understanding [topic] has never been more urgent..."
- "The stakes of [phenomenon] are high..."
- "As [trend] accelerates, scholars and practitioners alike..."
- "[Topic] shapes the life chances of millions..."
Case-led:
- "In [location], [event] unfolded..."
- "On [date], [actor] announced..."
- "When [name] arrived at..."
- "Consider the case of [example]..."
Theory-led:
- "The concept of [X] refers to..."
- "[Author]'s theory of [X] suggests..."
- "Drawing on [tradition], scholars have shown..."
- "[Framework] offers a lens for understanding..."
Establishing the Gap
Gap identification:
- "Yet we know remarkably little about..."
- "Despite extensive research on [X], scholars have paid less attention to..."
- "Prior research has focused primarily on [X], leaving [Y] unexplored..."
- "What remains unclear is..."
- "Existing studies have not examined..."
- "While [X] is well-documented, [Y] remains understudied..."
Puzzle framing:
- "This raises a puzzle: why do..."
- "This pattern is surprising given..."
- "If [expected], why do we observe [actual]?"
- "The persistence of [X] despite [Y] demands explanation..."
Limitation of prior work:
- "Previous research has been limited by..."
- "Existing accounts leave unresolved..."
- "While valuable, these studies cannot explain..."
- "The literature has not adequately addressed..."
Previewing the Study
Data introduction:
- "Drawing on [N] in-depth interviews with..."
- "This article examines [topic] through..."
- "Based on [N] semi-structured interviews conducted between..."
- "Using qualitative data from..."
- "To address these questions, we conducted..."
Argument preview:
- "We argue that..."
- "This article demonstrates that..."
- "We find that..."
- "Our analysis reveals..."
- "The evidence suggests that..."
Contribution claims:
- "This study makes [N] contributions..."
- "We extend [theory] by showing..."
- "We contribute to [literature] by..."
- "The article advances understanding of..."
- "We introduce the concept of [X] to capture..."
Roadmap Phrases
- "The article proceeds as follows..."
- "We begin by [reviewing/describing]..."
- "We first [X], then [Y], and conclude by [Z]..."
- "In what follows, we..."
- "The remainder of this article..."
---
Conclusion Phrases
Opening Moves
Restatement:
- "This study has examined..."
- "[Topic] shapes [population]'s experiences in ways that..."
- "The [phenomenon] we have described..."
- "For [population], [key finding]..."
Summary:
- "Three key findings emerge from this analysis..."
- "This article has demonstrated that..."
- "Our analysis reveals that..."
- "The evidence presented here shows..."
Integration:
- "Recent research on [topic] has emphasized..."
- "Scholars of [field] have long recognized..."
- "Building on [Author]'s insights..."
Contribution Claims
Extending theory:
- "These findings extend [theory] by showing..."
- "We have demonstrated the utility of [framework] for..."
- "Our analysis confirms and extends [Author]'s argument..."
Building concepts:
- "The concept of [X] captures..."
- "We introduced the term [X] to describe..."
- "[Concept] provides analytic leverage for..."
- "Unlike [existing term], [new term] emphasizes..."
Filling gaps:
- "This study addresses a gap in..."
- "We have shown that [previously unknown pattern]..."
- "The findings illuminate [understudied phenomenon]..."
Synthesizing:
- "By connecting [A] and [B], we reveal..."
- "The integration of [traditions] shows..."
- "Bringing together [literatures], this analysis..."
Limitations
Scope limitations:
- "This study has limitations..."
- "Our sample of [N] [population] in [location] may not generalize to..."
- "We cannot establish causal ordering between..."
- "The [context-specific] nature of our data means..."
- "We make no claim that this is the only way..."
Methodological limitations:
- "The cross-sectional nature of our data..."
- "Future research with [different design] could..."
- "Our reliance on [method] means we cannot..."
Future Directions
- "Future research might examine..."
- "An important next step would be..."
- "Scholars should investigate whether..."
- "Longitudinal research could establish..."
- "Comparative work across [contexts] would..."
- "These findings raise new questions about..."
Implications
Theoretical implications:
- "These findings suggest that theories of [X] should..."
- "For scholars of [field], our analysis implies..."
- "The [mechanism] we identify may operate in..."
Policy implications:
- "For practitioners, these findings suggest..."
- "Policymakers should consider..."
- "Current approaches to [X] may inadvertently..."
- "These insights have practical implications for..."
Broader significance:
- "More broadly, this study illuminates..."
- "Understanding [phenomenon] becomes increasingly important as..."
- "As [trend] continues, [insight] matters because..."
Callback and Coda
Callback phrases:
- "Returning to [opening theme]..."
- "Recalling our opening observation about..."
- "The [image/case] with which we began..."
- "What we initially characterized as [X] is better understood as..."
Coda phrases:
- "Ultimately, [summary statement]..."
- "In the end, [population]'s [experiences] reveal..."
- "As [participant] put it, '[quote]'"
- "What the literature calls [X] may be better understood as..."
- "[Final resonant statement]."
---
Phrases to Avoid
In Introductions
- "This paper argues that..." (too abrupt as opener)
- "In this paper, I will..." (save for roadmap)
- "The literature has overlooked..." (without justification)
- "Little is known about..." (unless truly true)
- "No one has studied..." (probably false)
In Conclusions
- "In conclusion..." (redundant; you're in the conclusion)
- "To sum up..." (informal)
- "More research is needed" (generic; be specific)
- "This study proves that..." (overclaiming for qualitative work)
- "Future research should..." (weaker than "might examine")
General
- "It is interesting to note that..." (show, don't tell)
- "Obviously..." / "Clearly..." (if obvious, don't state)
- "The data revealed that..." (passive; prefer active)
- Excessive hedging: "might," "perhaps," "seemingly," "possibly"