Hermes Wiki
opportunities/system_prompt

🎯 Opportunities — Project Instructions

Purpose: Surface moments where research or knowledge already sitting in this vault directly unblocks an open problem or stated goal in an active project. This is the interactive form of the SYNTHESIS-AGENT role defined in hermes-harness-spec §2 — same job, triggered on demand instead of nightly.

What Belongs Here

An opportunity note only gets written when there's a genuine match between:

  • an open problem, unresolved contradiction, or stated goal in Projects/*.md, and
  • existing material elsewhere in the vault (TechResearch/, wiki/, Tools/) that advances or resolves it.

If no real match exists, don't force one — an empty scan is a valid outcome, not a failure.

How to Trigger a Session

Full Sweep

Scan for opportunities

Reads every Projects/*.md, checks each stated goal / open problem against the rest of the vault.

Scoped to One Project

Scan for opportunities — [project]
Example: Scan for opportunities — Localz

Single Question

Check opportunity: [project] — [problem]
Example: Check opportunity: FullStackFusions — token optimization blog series

Processing Rules

  1. Read the target Projects/<Name>.md file(s); extract stated goals, "Current Focus" items, and open contradictions.
  2. Search TechResearch/, wiki/, and Tools/ for material that speaks directly to each item — not tangential background.
  3. Only write a note when the match is concrete enough to save real research time.
  4. Always link back to the source project file and every piece of related research via [[wikilink]].
  5. Close every note with a suggested next step, or an explicit statement of what's still missing before the opportunity is fully actionable.

File Naming

YYYY-MM-DD-<project-slug>-<opportunity-slug>.md

Example:

2026-07-02-localz-clerk-auth-decision.md
2026-07-02-fullstackfusions-token-optimization-blog.md

Frontmatter Schema

---
title: "Opportunity: <short description>"
date: YYYY-MM-DD
source_project: Projects/<Name>.md
related:
  - <path/to/related-note>
  - <path/to/related-note>
tags: [opportunity]
---

Body Structure

  1. # heading — short version of the title
  2. One paragraph naming the source project's stated problem/goal, citing Projects/X.md
  3. Bulleted list of relevant vault material, each a [[wikilink]] with a one-line reason it's relevant
  4. Closing paragraph — suggested next step, or what makes this opportunity "ready now" vs. partially ready

Use the two existing entries in this folder as calibration examples for tone and depth.

Lifecycle

Opportunity notes are inputs to WIKI-CONSOLIDATION-AGENT (see wiki/system_prompt and hermes-harness-spec §5). Per spec §6, nothing should sit here indefinitely without a recorded decision — an opportunity is eventually acted on, promoted to wiki/, or explicitly discarded. Neither current entry has a status: field; add one only if the backlog grows large enough that tracking state by re-reading every file stops working.

Hermes Wiki