hunter-log

Files (4)

• README.md
• SKILL.md
• pipeline-envelope-schema.json · references/
• templates.md · references/

SKILL.md (first lines)

# Hunter Log

Persistence layer for the hunter product discovery pipeline. Receives structured JSON output wrapped in a PipelineEnvelope, renders it as Obsidian-compatible markdown, and writes it to the vault with frontmatter, wikilinks, session tracking, and kanban board updates.

## Step 0: Load Conventions

Before doing ANYTHING, read the shared conventions file:

```
Read ${SKILLS_DIR}/_conventions.md
```

This file defines: canonical vault path, folder-to-type mapping, frontmatter contract, valid statuses, tag hierarchy, cross-reference syntax, and the PipelineEnvelope schema. All output from this skill MUST conform to those conventions. If there is a conflict between this SKILL.md and `_conventions.md`, the conventions file wins.

## When to Use

- After any pipeline skill produces output and it needs to be saved
- When manually saving a PipelineEnvelope payload to the Obsidian vault
- When updating the session log or kanban board for an existing pipeline run
- When appending new results to an existing document in the vault

## Trigger Phrases

- "Save this to the vault"
- "Log this pipeline output"
- "Persist the scan results"
- "/hunter-log {envelope}"
- "Write this decision to Obsidian"

---

## Prerequisites

Before starting, you need exactly one thing:

1. **PipelineEnvelope** -- A JSON object wrapping the output of a pipeline skill. Must conform to the schema in [references/pipeline-envelope-schema.json](references/pipeline-envelope-schema.json).

If the caller provides raw skill output without an envelope, ask for the envelope fields (skill, session_id, timestamp, input_refs) or construct one from context.

---

## Pipeline Context

```
signal-scan --> decision-log --> persona-extract --> offer-scope
                     |                |                  |
               hunter-log       hunter-log         hunter-log
            (persistence)     (persistence)      (persistence)
```

hunter-log sits below every pipeline skill. It does NOT do analysis. It only formats and saves.

---

## Vault Layout

All files are written under the Obsidian vault base path (iCloud-synced):

```
${VAULT}/Admin/Product-Discovery/
```

```
Admin/Product-Discovery/
  Pipeline.kanban.md            # Master kanban board
  _index.md                     # Index with dataview queries
  Signal-Scans/                 # from signal-scan
  Decisions/                    # from decision-log
  Personas/                     # from persona-extract
  Offers/                       # from offer-scope
  Sessions/                     # session logs (one per session_id)
```

---

## Workflow

```
PipelineEnvelope (JSON)
    |
Phase 1: Envelope Parsing -- validate, extract skill type + output
    |
Phase 2: File Path Resolution -- map to directory, generate slug, check collisions
    |
Phase 3: Frontmatter Generation -- schema-driven per document type
    |
Phase 4: Body Rendering -- markdown from JSON using templates
    |
Phase 5: Write to Vault -- create or append
    |
Phase 6: Session Log Update -- create or append session file
    |
Phase 7: Kanban Board Update -- move/create card in Pipeline.kanban.md
    |
Output: confirmation with file path + wikilink
```

---

## Phase 1: Envelope Parsing

Read the PipelineEnvelope and extract:

- `skill` -- determines document type and target directory
- `session_id` -- links to session log
- `timestamp` -- used in frontmatter and append headings
- `input_refs` -- used for "Based On" cross-links
- `output` -- the skill's JSON payload to render

**Validation rules:**
- `skill` must be one of: `signal-scan`, `decision-log`, `persona-extract`, `offer-scope`
- `version` must be `"1.0"`
- `session_id` must match format `session-YYYY-MM-DD-NNN`
- `output` must be present and non-null

If validation fails, report the specific field and stop. Do not write partial files.

---

From Peleke/brunnr, MIT.

More from Peleke/brunnr