deliver

deliver

The delivery organ. Takes an already-selected set of fragments and produces the rendered block Claude reads.

When to run

• Another skill invokes this one programmatically, passing a fragment selection it has already filtered and scored (discovery for bodies, prep at task start, review during diff inspection, plan at milestone boundaries).
• Do not respond to user prose triggers. There is no /deliver command. There is no "when user says X" branch. Delivery is purely a format-and-assembly helper.
• Stateless per call. No memoization, no cache, no hidden state.

Inputs

Structured, from the caller:

{
  fragments: Fragment[],        // already-selected; delivery does not re-filter
  order_override?: Order,       // optional; default = the §2 tier priority
  cap?: number,                 // optional; default 20; hard ceiling regardless of caller
}

Fragment = {
  path: string,                 // repo-relative or ~/-relative; source-of-truth pointer
  frontmatter: {                // parsed YAML
    name: string,
    description?: string,
    type?: string,
    kind?: string,              // "architectural-rule" | "decision" | "lesson" | "preference" | ...
    scope?: string[],
    relevance?: string,
  },
  body: string,                 // verbatim content — delivery does not paraphrase
}

Order = "default" | "caller" | explicit-tier-list

Procedure

1. Validate inputs

• fragments present and non-empty. Empty → return empty string and a single-line note ([delivery: empty selection]). Never synthesise content.
• Each fragment has path, frontmatter.name, body. Missing path or name → render with the available fields, emit a [delivery: fragment missing <field>] marker inline so the caller notices.
• cap bounded to [1, 20]. Caller-specified values outside this range are clamped; flag the clamp in the report line.

2. Sort

Default priority (highest tier first):

1. Warnings — frontmatter.kind == "warning". Landmines that earned their place by citing a real prior incident; surface ahead of everything because the cost of forgetting one is concrete.
2. Architectural rules — frontmatter.kind == "architectural-rule".
3. Project-specific facts — frontmatter.type == "project" OR frontmatter.scope contains any project-* tag.
4. Session recaps — frontmatter.type == "session-recap". Episodic recall sits below project facts but above codemap, because "what I was investigating" gives more signal than raw file summaries when resuming work.
5. Codemap entries — fragments where frontmatter.kind == "codemap" or frontmatter.type == "codemap". (Discovery surfaces these when .claude/codemap.md contributes.)
6. Everything else — lessons, decisions, preferences, references, general feedback.