---
description: Map connections between passages -- parallel accounts, prophetic fulfillments, intertextual echoes, typological links.
argument-hint: "[--passage <ref>] [--type <parallel|fulfillment|echo|typology>]"
---

# Cross-reference

You map the connections between passages that reference, fulfill, echo, or prefigure each other. Essential for commentary, theological study, and any sacred text with layered internal relationships.

## Availability

Sacred work types only. Requires `CONCORDANCE.md` (run `/scr:sacred:concordance --build` first if it doesn't exist).

## What to do

### If no arguments

Build the full cross-reference network across all drafted units. For each significant passage, identify:

1. **Parallel accounts** -- Passages that tell the same event from different perspectives (Synoptic Gospels, Chronicles vs Kings, parallel hadith narrations).
2. **Prophetic fulfillments** -- Earlier prophecies and their later fulfillments. Link forward and backward.
3. **Quotations and allusions** -- Where the text quotes or alludes to other canonical sources (or earlier in itself).
4. **Thematic echoes** -- Non-quotation resonances where one passage deliberately evokes another (creation motifs in a baptism scene, exodus motifs in a deliverance story).
5. **Typological links** -- Figure X prefigures figure Y; event X prefigures event Y. Common in Christian reading of the Old Testament, also in Hindu puranic layering and Buddhist sutra hierarchies.

Save to `.manuscript/CROSS-REFERENCES.md` with entries like:

```markdown
## Genesis 1:1-2 (creation)
**Parallels:** Psalm 33:6, John 1:1-3
**Echoes:** Genesis 8:1 (new creation after flood), Exodus 14:21 (wind over waters at Red Sea)
**Typology:** Points forward to new creation (Isaiah 65:17, Revelation 21:1)

## Exodus 12 (passover)
**Parallels:** Numbers 9:1-14 (second passover)
**Fulfillment:** 1 Corinthians 5:7 (Christ as passover lamb)
**Typology:** The lamb's blood prefigures sacrificial atonement throughout Leviticus
```

### --passage <reference>

Show all cross-references for a specific passage. Useful when drafting: "what does Genesis 22 connect to that I should acknowledge or echo?"

### --map

Generate a visual cross-reference map showing connection density across units. Output as a text-based adjacency matrix or network diagram showing which units connect to which others and how densely. Save to `.manuscript/CROSS-REFERENCE-MAP.md`. Useful for seeing structural patterns -- e.g., a heavily cross-referenced passage is likely a theological crux.

### --add <source> <target> <type>

Manually add a cross-reference. The writer specifies:
- **source** -- Source passage reference (e.g., "Genesis 22:8")
- **target** -- Target passage reference (e.g., "John 1:29")
- **type** -- One of: `parallel`, `fulfillment`, `echo`, `quotation`, `allusion`

Connection types:
- **parallel** -- Similar passages telling the same event from different perspectives
- **fulfillment** -- Prophecy-fulfillment pairs (earlier prophecy, later fulfillment)
- **echo** -- Thematic echo where one passage deliberately evokes another
- **quotation** -- Direct quote of another passage or canonical source
- **allusion** -- Indirect reference to another passage without direct quotation

Append to `.manuscript/CROSS-REFERENCES.md` and confirm.

### --type <parallel|fulfillment|echo|quotation|allusion|typology>

Filter to one connection type. Useful for structural audits ("show me every prophecy and whether it has a fulfillment").

## Integration with the drafter

When drafting a unit, the plan file can include cross-reference anchors: "This passage echoes Genesis 1 -- use creation vocabulary." The drafter loads the cross-referenced passage as context and weaves the echo in.

## Response Contract

Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

Use this format:

```markdown
Next commands:
- `/scr:...`: One short sentence explaining what this path will do.
- `/scr:...`: One short sentence explaining what this alternate path will do.
```

If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.

If the writer seems unsure or no specific next command is obvious, include this default option:

```markdown
Next commands:
- `/scr:next`: Inspect the project state and choose the right next step.
```

If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.

## Tone

Analytical. Cross-references are factual claims about the text's structure. Don't editorialize about whether a connection is "intentional" or "meaningful" -- just record it. The writer decides significance.