rampstackco/claude-skills / skills/long-form-content-frameworks
long-form-content-frameworks
VerifiedPatterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 369 B |
| SKILL.md | skill md | 29.4 KB |
| references/attention-sustaining-techniques.md | markdown | 9.7 KB |
| references/breakouts-and-visualization.md | markdown | 10.4 KB |
| references/citation-and-source-authority.md | markdown | 10.4 KB |
| references/closing-patterns.md | markdown | 12.0 KB |
| references/common-long-form-failures.md | markdown | 11.6 KB |
| references/format-decision-framework.md | markdown | 10.6 KB |
| references/lede-patterns-for-long-form.md | markdown | 9.9 KB |
| references/section-weight-calibration.md | markdown | 9.4 KB |
| references/structural-archetype-patterns.md | markdown | 10.4 KB |
references/common-long-form-failures.md
View on GitHub# Common long-form failures
Eleven-plus failure patterns with diagnoses and cures. The patterns appear repeatedly across long-form drafts, regardless of topic, format, or writer experience. Diagnosing them early saves the rewrite work that catches them late.
The pattern across most failures: writers reaching for length without doing the structural work that justifies it, and writers under-investing in the structural decisions that make long-form land.
---
## Failure 1: Bloggy-long
**Symptom.** A 5,000-word piece reads as a 1,500-word piece stretched. Padding paragraphs. Recap sections. "Before we get into it" preludes. Bullet expansions of single ideas. The reader notices within 600 words and skims.
**Diagnosis.** The writer chose length first and structural depth second. The piece needed to be longer than 1,500 words for SEO or marketing reasons but did not have 5,000 words of substantive content.
**Cure.** Two options. Cut to actual substantive length (often 1,800-2,500 words). Or expand the structural depth: add original analysis, primary research, case study specificity, or comparative dimensions that justify the length.
**Prevention.** Choose length based on substantive content, not based on competitor length or SEO targets. SEO algorithms are getting better at detecting padded length; the strategy of "outranking by being longer" is increasingly counterproductive.
---
## Failure 2: Academic-bloat
**Symptom.** A 7,000-word whitepaper that is exhaustive but loses the thread. Every adjacent topic surveyed. Every definition restated. Every caveat documented. Reader respects the effort and skims for the parts they need.
**Diagnosis.** The writer aimed for comprehensiveness rather than for argumentative load. The piece treats inclusion as the metric instead of treating each section's contribution as the metric.
**Cure.** Apply the section-weight audit: which sections are actually load-bearing, which are surveying. Cut surveying sections that do not support specific claims in the load-bearing sections. Often takes 7,000 words to 4,500 with the argument intact.
**Prevention.** Outline the argument before drafting. Each section should answer: what does this section contribute to the argument? If a section's answer is "comprehensive coverage" rather than a specific contribution, question whether the section earns its place.
---
## Failure 3: Throat-clearing lede
**Symptom.** The lede took 800 words to get to the thesis. Multiple paragraphs of "content marketing has changed dramatically" before the piece's actual claim appears.
**Diagnosis.** The writer was warming up. Drafts often have throat-clearing ledes; finished pieces should not.
**Cure.** Cut the first 400-700 words of the lede. The piece's actual first sentence is usually the third or fourth paragraph of the throat-clearing draft.
**Prevention.** After drafting, ask: where does the piece's specific argument actually start? Whatever appears before that point is throat-clearing and can usually be cut.
---
## Failure 4: Even-section padding
**Symptom.** All H2s come within 10% of each other in word count. Each section running 800-1,000 words regardless of its argumentative load.
**Diagnosis.** The writer treated section length as a quota. Long sections were padded; short sections were either padded or not deepened.
**Cure.** Identify which sections are actually load-bearing. Let them grow. Cut filler from non-load-bearing sections.
**Prevention.** Plan section weights in the outline based on argumentative load, not on parallel structure. Allow 2x or 3x weight differences between sections doing different amounts of work.
---
## Failure 5: Mid-piece sag
**Symptom.** The piece sags around the 60% mark. Reader-attention analytics show drop-off at this point.
**Diagnosis.** Standard mid-piece attention dip, untreated. No micro-thesis, no rhythm variation; the reader is exhausted from sustained density.
**Cure.** Add a mid-piece micro-thesis at the section boundary nearest the midpoint. Insert a breathing section (anecdote, illustration, or reflective moment) into a stretch of argument-tight prose. Vary visual rhythm in the mid-piece section.
**Prevention.** During outlining, mark the midpoint and plan the micro-thesis explicitly. During drafting, audit the middle third for rhythm variation.
---
## Failure 6: Recap closing
**Symptom.** The closing repeated the introduction. "In this piece we covered X, Y, Z. As we have seen, content is important..."
**Diagnosis.** The writer ran out of energy. The closing was drafted last, in fatigue, and it shows.
**Cure.** Rewrite the closing using one of the five working patterns: specific call, reframed thesis, open question, personal reflection, or provocation.
**Prevention.** Write the closing first, or revise the closing last with fresh attention. Closings deserve disproportionate effort because they are disproportionately consequential.
---
## Failure 7: Citation laundering
**Symptom.** Citations are mostly other content marketing pieces rather than primary or authoritative-secondary sources.
**Diagnosis.** The writer searched for support for claims and found other content marketing pieces making the same claims. Citing them feels like sourcing; it is not.
**Cure.** Follow each citation chain back to the original. If the chain ends at a primary source, cite the primary source. If the chain ends at unsourced or weakly sourced content marketing, either find a primary source for the claim or cut the claim.
**Prevention.** Default to Tier 1-3 sources (primary research, authoritative secondary, industry-credible). Only cite Tier 4 sources for color and context, never for argumentative load.
---
## Failure 8: Visual-count overrun
**Symptom.** The piece commissioned 12 charts. The team is exhausted from production. Six months later, charts are stale because nobody updated them. Traffic is the same as it would have been with 4 charts.
**Diagnosis.** Visual count exceeded production capacity and earned-position discipline.
**Cure.** Cut to the visuals that bear argumentative load the prose alone cannot. Update them on a maintainable cadence. Future pieces budget visuals against capacity rather than against ideal-world maximalism.
**Prevention.** Apply the MVP-visuals approach: which visuals are load-bearing, which would be nice to have, which would be decoration. Ship the load-bearing ones first; add others only if capacity permits.
---
## Failure 9: Generic case study
**Symptom.** The case study has no specifics. "A leading enterprise SaaS company" rather than the company name. "Significant revenue growth" rather than the actual percentage. "Several months" rather than the timeline.
**Diagnosis.** The case study format failed at its primary tax: specificity. Either the case was too confidential to share specifics, or the specifics were never gathered.
**Cure.** Get specifics. Negotiate with the customer for what can be shared. If specifics genuinely cannot be shared, abandon the case study format and write a different format (general thought-leadership piece on the lessons learned, with the specific case relegated to background).
**Prevention.** Do not commit to the case study format until specifics are confirmed shareable. Generic case studies fail the format and are less valuable than honest pieces about the lessons without claiming case-study authority.
---
## Failure 10: Diplomatic manifesto
**Symptom.** The manifesto reads as diplomatic. "Both sides have valid points." "The answer probably lies somewhere in the middle." Hedge stacking on positions that should be specific.
**Diagnosis.** The writer chose the manifesto format but could not commit to the conviction the format requires. Often reflects organizational risk-aversion: the manifesto's bold framing was approved but its actual conviction was edited out.
**Cure.** Either rewrite to commit a position (the format demands it), or change the format. A diplomatic position paper that is not pretending to be a manifesto is fine; a manifesto that hedges is broken.
**Prevention.** Before committing to the manifesto format, confirm the writer (and the organization) actually has a contested position to argue. If hedging is required, write a different format.
---
## Failure 11: Definitive guide with gaps
**Symptom.** The "definitive" guide has obvious sub-topic gaps that the audience would notice. The piece claims comprehensiveness but does not deliver it.
**Diagnosis.** The format implies coverage that the piece does not have. Either the gaps reflect topics the writer did not cover deliberately (and should have flagged), or the writer did not realize the gaps existed.
**Cure.** Either fill the gaps or rename the piece. "The definitive guide to X" with gaps is broken; "A practitioner's guide to X" with the same content but without the comprehensiveness claim is fine.
**Prevention.** Before claiming definitive-ness, audit against the audience's likely sub-topic expectations. Confirm coverage or change the framing.
---
## Failure 12: Wrong archetype
**Symptom.** The piece is fighting itself. The writer is trying to argue layered evidence inside a narrative arc, or to survey a taxonomy inside a problem-solution shape. The reader senses the structural friction even when they cannot articulate it.
**Diagnosis.** Archetype-format mismatch or archetype-topic mismatch. The writer chose an archetype that does not fit the work.
**Cure.** Identify the natural archetype for the topic and the format. Restructure. This is often a substantial revision because the archetype is the spine; changing it changes how sections fit together.
**Prevention.** Choose archetype before drafting. Confirm the archetype fits the format and the topic. Do not commit to draft until the archetype-format-topic combination is coherent.
---
## Failure 13: Format-tax unpaid
**Symptom.** The piece is published in a long-form format but does not pay the format's specific tax. A whitepaper without original synthesis. A research report without primary research. A long-form tutorial with broken steps.
**Diagnosis.** The writer reached for the format's authority without paying the cost the format demands.
**Cure.** Either pay the tax (do the original work the format requires) or change the format. A piece published in the wrong format reads as a category error to readers familiar with the format.
**Prevention.** Confirm the format-tax is payable before committing to the format. Format choice is a downstream decision from "what work is the team prepared to do."
---
## The cross-cutting pattern
Most long-form failures share a single root: the writer chose length, format, or visual ambition first, and chose the structural and substantive depth second. The pieces that read as publication-quality are the ones where the inverse choice is made: substantive depth first, then length, format, and visual ambition follow from the depth.
The fix for almost any long-form failure starts with the same audit: what is the piece actually doing, what is each section actually contributing, what does the format require, what does the topic need? When those questions get clear answers, the piece either earns its length or shrinks to a length that fits its substance.
---
## Methodology-level choices that stay in the public skill
The thirteen-plus failure patterns with diagnoses and cures, the cross-cutting pattern that connects most of them, the prevention discipline.
## Implementation choices that stay internal
Specific draft-review checklists the team uses. Specific failure-pattern detection in the team's editing tools. Specific reviewer training on the patterns. Specific case-study negotiation templates for getting customer specifics. The team's own conventions for archetype-format fit confirmation. These vary by team, format mix, and tooling.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |