Narrative Handoff Contract

Defines and validates the machine-readable contract that passes a narrative architecture between a structural agent and a drafting agent — architecture.json with evidence-backed slots, capped scene tags, gap dispositions, a DEAD column, and an escalation object for sending defects back upward. Ships a validator script so the rules are enforced rather than requested. Use when two agents or two sessions must hand narrative work to each other, when an architecture needs checking before drafting begins, when a draft must report a defect it cannot fix at its own layer, or when the user mentions han

200 stars 25 forksMarketing, Sales & Business 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 narrative-handoff-contract
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/narrative-handoff-contract ~/.claude/skills/narrative-handoff-contract

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

From the SKILL.md

# Narrative Handoff Contract

## Table of Contents

- [Core Principles](#core-principles)
- [Workflow](#workflow)
- [The three fields that carry the weight](#the-three-fields-that-carry-the-weight)
- [The escalation object](#the-escalation-object)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

**Related skills:** Use `narrative-evidence-ledger` to build the claim set this contract points at, `narrative-arc-mapping` to fill the slots, and `narrative-fidelity-audit` to check the prose that comes back.

## Core Principles

1. **A pipeline whose interface is prose has no interface.** Two agents that hand each other paragraphs cannot enforce anything. The handoff is a file.
2. **The evidence array is the validated field, not the value.** A slot with a confident sentence and no claim ID fails here rather than reading well downstream.
3. **ABSENT is a passing state.** An architecture with every slot filled is flagged, because real material always has holes.
4. **Enforce with a cap, not a request.** "Never draft prose" decays as context fills. A length limit on scene lines does not.
5. **The channel runs both ways.** Without an escalation object the drafting layer has no way to report a structural defect, so it papers over it with polish.
6. **Pointers resolve outward.** A citation resolving into the pipeline's own earlier output is circular, invisible to reading, and a hard failure.

## Workflow

Copy this checklist and track your progress:
Read the full skill on GitHub

Details

Skill name
narrative-handoff-contract
Path
skills/narrative-handoff-contract/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Narrative Handoff Contract skill do?

Defines and validates the machine-readable contract that passes a narrative architecture between a structural agent and a drafting agent — architecture.json with evidence-backed slots, capped scene tags, gap dispositions, a DEAD column, and an escalation object for sending defects back upward. Ships a validator script so the rules are enforced rather than requested. Use when two agents or two sessions must hand narrative work to each other, when an architecture needs checking before drafting begins, when a draft must report a defect it cannot fix at its own layer, or when the user mentions han

How do I install the Narrative Handoff Contract 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 Narrative Handoff Contract 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 to Numbers

200

lyndonkl/claude

Builds the business story behind a valuation and connects it to the drivers that carry value — market size, growth, margin, reinvestment efficiency and risk. Tests a narrative as possible, plausible and probable, and keeps the feedback loop open. Use when starting a valuation, writing the story behind a company, setting growth or margin assumptions, sanity-checking a story against its numbers, choosing a target margin or sales-to-capital ratio, or when a valuation needs a defensible reason for its inputs.

Marketing, Sales & Business25

Mlb Trade Evaluator

200

lyndonkl/claude

Computes the full impact of a proposed MLB fantasy trade across all 10 H2H categories (R/HR/RBI/SB/OBP, K/ERA/WHIP/QS/SV), rest-of-season dollar value, positional flexibility, slot-value optionality, adverse-selection prior, and weeks 21-23 playoff impact. Produces a signed verdict (accept / counter / reject) with rationale and a specific counter if applicable. Use when user mentions "trade evaluation", "trade value", "should I accept", "trade delta", "counter offer", or pastes in a trade proposal from Yahoo. Defaults to COUNTER in the middle band — pure REJECT is reserved for clearly predator

Marketing, Sales & Business25

Quarterly Zoomout

200

lyndonkl/claude

Synthesizes 13 weeks of substacker Growth Analyst reports + the most recent Curator review + a meta-scan of the published corpus into a 400-700 word narrative that names the quarter's shape — what happened, what changed, what held steady, what surprised. Used by the Growth Strategist at the opening of every review. Trigger keywords — quarterly, zoomout, quarter narrative, rollup, what happened this quarter.

Marketing, Sales & Business25

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.