lyndonkl/writing-structure-planner
skills/writing-structure-planner/SKILL.md
Guides writing architecture planning using McPhee's structural diagramming method, helping select from 8 structure types (list, chronological, circular, dual/triple profile, pyramid, parallel, custom), create visual diagrams, and place gold-coin moments for engagement. Use when planning or organizing writing structure, outlining before drafting, restructuring disorganized drafts, or when user mentions outlining, organizing ideas, structure planning, article architecture, narrative flow.
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude writing-structure-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:29 AM163.6s3 files scanned
SKILL.md
- name:
- writing-structure-planner
- description:
- Guides writing architecture planning using McPhee's structural diagramming method, helping select from 8 structure types (list, chronological, circular, dual/triple profile, pyramid, parallel, custom), create visual diagrams, and place gold-coin moments for engagement. Use when planning or organizing writing structure, outlining before drafting, restructuring disorganized drafts, or when user mentions outlining, organizing ideas, structure planning, article architecture, narrative flow.
Writing Structure Planner
Table of Contents
- Core Principles
- Workflow
- Structure Types Overview
- Guardrails
- Quick Reference
Related skills: Use writing-revision for revising existing prose, writing-stickiness for memorable messaging, writing-pre-publish-checklist for final quality checks.
Core Principles
- Structure arises from material: Don't impose a structure - let the content suggest its natural organization
- Blueprint before building: Always plan structure before drafting
- Invisible architecture: Good structure is invisible to readers - they just experience flow
- Three options minimum: Always sketch at least 3 structural options before choosing
- Gold-coin distribution: Place reader rewards throughout, especially in the middle
Workflow
Copy this checklist and track your progress:
Structure Planning:
- [ ] Step 1: Analyze material thoroughly
- [ ] Step 2: Explore structure options
- [ ] Step 3: Select and refine structure
Before starting: Review resources/structure-types.md for the 8 structure types, diagramming method, and selection criteria.
For analysis steps, output findings to analysis files in the current directory to ensure thorough coverage of all material. These analysis files remain in the project for your review.
Step 1: Analyze material thoroughly
Step 1.1: Gather and understand all material completely. Read everything the user has provided.
Step 1.2: Create analysis file writer-structure-material-analysis.md and output: all key points, anecdotes, data, quotes, and examples found in the material. Identify themes and patterns. Determine what's most important vs. supporting detail. Identify the natural organizing principle (time, space, importance, comparison). Note reader considerations (busy? engaged? unfamiliar? expert?).
Step 1.3: Present the material analysis to the user and confirm understanding is complete. Ask: "Did I miss any important material or themes?"
See resources/structure-types.md - Gather Your Material for detailed guidance.
Step 2: Explore structure options
Step 2.1: Read the analysis file. Review all 8 Structure Types with examples.
Step 2.2: Create analysis file writer-structure-options.md and sketch 3 different structure options. For each option include: structure type name, diagram sketch, how user's material maps to it, pros and cons.
Step 2.3: Test each option against Structure Selection Criteria. Present all 3 options to the user with your recommendation.
See resources/structure-types.md - Sketch 3 Options for detailed process.
Step 3: Select and refine structure
Step 3.1: Read the options file. Based on user's choice (or your recommendation if they defer), select the structure that best serves the material.
Step 3.2: Create the final annotated structure diagram. Map key moments and transitions. Identify where to place gold-coin moments throughout (especially middle sections). Annotate with pacing and transition notes.
Step 3.3: Verify structure supports the through-line (promise -> delivery -> resonance). Test: Does this feel inevitable or forced? Present final annotated structure diagram for user review before drafting.
See resources/structure-types.md - Select and Refine for detailed guidance.
How to know if structure is working:
If working: Readers won't notice it, they'll just experience flow and feel the piece is "well-organized."
If not working: Readers will feel lost, wonder "where is this going?", or abandon before the end.
Validate using resources/evaluators/rubric_structure.json. Minimum standard: Average score >= 3.5.
Structure Types Overview
The 8 structure types available (see resources/structure-types.md for full details):
| Type | Best For | |------|----------| | List | Multiple independent points, how-to guides | | Chronological | Narratives, historical accounts, processes | | Circular/Cyclical | Hooking readers with drama, then providing context | | Dual Profile | Character profiles, examining topic from multiple angles | | Triple Profile | Complex characters in multiple contexts | | Pyramid (Inverted) | News, executive summaries, busy readers | | Parallel Narratives | Comparing/contrasting, multi-threaded stories | | Custom Diagrams | Unique material that doesn't fit standard types |
Guardrails
Requirements:
- Material-first: Always understand the material before suggesting structure. Never impose a structure without understanding content.
- Three options: Always generate at least 3 structural options. The second or third is often best.
- User collaboration: Present options and let the user choose. Don't dictate structure.
- Gold-coin placement: Every structure must include strategic placement of reader rewards, especially in the middle.
- Test the structure: Ask "does this feel inevitable or forced?" before finalizing.
Common pitfalls:
- Defaulting to chronological when another structure serves better
- Front-loading all strong material in the opening
- Ignoring the "saggy middle" problem
- Imposing structure without understanding material
- Skipping the 3-option comparison step
Quick Reference
Key resources:
- resources/structure-types.md: All 8 structure types, diagramming method, gold-coin strategy, selection criteria
- resources/evaluators/rubric_structure.json: Quality scoring criteria
Inputs required:
- User's material, ideas, or topic description
- Target audience (if known)
- Any constraints (length, format, publication)
Outputs produced:
- Material analysis document
- 3 structure options with pros/cons
- Final annotated structure diagram with gold-coin placement
- Recommended writing order
Related Skills
lyndonkl/skills/zettel-note
development
VerifiedTrustedCommunity
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-transfer-planner
development
VerifiedTrustedCommunity
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-tournament-state
testing
VerifiedTrustedCommunity
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-signal-emitter
development
VerifiedTrustedCommunity
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.
119SKILL.mdUpdated Jun 12, 2026