Mcphee Structure Derivation

Derives a document's structure out of its own corpus instead of picking one off a menu, using John McPhee's coding-and-sorting procedure - cold read, short topic codes one per card, a strict chronology sort run against a strict theme sort, a logged list of every disagreement resolved toward chronology, candidate juxtapositions gated by a state-and-footnote test, a named shape, and an invisibility test. Use when you hold researched material and have no structure yet, when a draft has turned into concept-named sections full of time-scrambled evidence, when deciding whether a flashback is earned,

200 stars 25 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill mcphee-structure-derivation
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/mcphee-structure-derivation ~/.claude/skills/mcphee-structure-derivation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# McPhee Structure Derivation

## Table of Contents
- [Core Principles](#core-principles)
- [Workflow](#workflow)
- [The Dual Sort and Its Resolution](#the-dual-sort-and-its-resolution)
- [Shape Catalog](#shape-catalog)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

**Related skills:** Use `narrative-form-triage` before this skill - it decides the FORM the corpus can support and owns the DO NOT NARRATE refusal, while this one derives the SHAPE once a narrative form has been declared. Use `writing-structure-planner` once components exist - that skill SELECTS among eight known shapes and diagrams the choice; this one DERIVES a shape from raw material and hands the named shape plus the card piles over to it. Use `writing-revision` on the prose after components are drafted, `writing-pre-publish-checklist` for the final gate.

## Core Principles

1. **Derive, do not select**: The shape is an output of sorting cards, not an input chosen before reading. If you named the shape before you coded the corpus, you imposed it.
2. **Chronology wins by default**: McPhee's rule is that tension between chronology and theme is near-universal and chronology usually wins. Theme-sorting is the cheapest operation a language model performs, which is exactly why it must be the one that has to argue for itself.
Read the full skill on GitHub

Details

Skill name
mcphee-structure-derivation
Path
skills/mcphee-structure-derivation/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Mcphee Structure Derivation skill do?

Derives a document's structure out of its own corpus instead of picking one off a menu, using John McPhee's coding-and-sorting procedure - cold read, short topic codes one per card, a strict chronology sort run against a strict theme sort, a logged list of every disagreement resolved toward chronology, candidate juxtapositions gated by a state-and-footnote test, a named shape, and an invisibility test. Use when you hold researched material and have no structure yet, when a draft has turned into concept-named sections full of time-scrambled evidence, when deciding whether a flashback is earned,

How do I install the Mcphee Structure Derivation skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Mcphee Structure Derivation popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Narrative Fallacy Guard

200

lyndonkl/claude

Stops a true set of facts from being assembled into a false story. Runs the retrospective slot audit, the outcome-blind rewrite (flip test, separation test), the inevitability audit with its overshoot check, the survivorship graveyard pass, the counterfactual admissibility gate, and the expensive proportion and omission audits. Every check labels and discloses; none deletes. Use when drafting or reviewing history, post-mortems, biography, market or protocol narratives, research writeups, or any account written after the outcome was known, or when user mentions hindsight bias, narrative fallacy

Testing & QA25

Ladder of Abstraction

200

lyndonkl/claude

Moves prose deliberately between the concrete and the abstract and stops it stranding in the middle rung where bureaucratic prose lives. Tags every paragraph R1 (named particulars) to R4 (meaning), enforces run rules, detects the middle-rung trap, repairs it by climbing down to a real particular rather than simplifying vocabulary, gates the top rung with a counter-sentence test, and closes with an A-frame descent. Use when a draft reads as dense, vague, or jargon-heavy, when a readability score fails, when a conclusion feels grandiose or unearned, when technical material will not land for a ge

Testing & QA25

Narrative Opposition Web

200

lyndonkl/claude

Builds a four-corner opposition web for narrative nonfiction and stops the writer from casting whoever lost as the villain. Runs Truby's four-corner worksheet (shared central moral problem, per-corner value clusters, distinct routes of attack, corner-to-corner conflict), the best-possible-opponent audit (same goal, necessity, relentlessness, value conflict, the double, power parity, justification in the opponent's own voice), the Opponent Warrant evidence test that demotes undocumented antagonists to rivals or constraints, and a drive-section collapse check that catches a web that was decorati

Testing & QA25

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.