loremaster-ai/loremaster / skills/loremaster-setup
loremaster-setup
VerifiedGuided, interactive onboarding that takes a Hermes Agent user from "tap added" to "first project live" — run it on first install of the Loremaster pack, when adding a new project (new channel + new lore vault), or when reconfiguring an existing setup (scripts, Jira, timezone, Obsidian).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.0 KB |
| references/channel-prompt-template.md | markdown | 1.8 KB |
| references/sample-prd.md | markdown | 710 B |
| references/vault-skeleton.md | markdown | 2.2 KB |
references/vault-skeleton.md
View on GitHub# Lore vault skeleton
Structure to create for a new vault (Step 4). The directory basename is the project
name — the Jira mapping (`~/.hermes/keys/jira-projects.tsv`) keys on it.
```
<project-name>/
raw/ # TRUTH — humans write here; the agent reads
PRD.md # product requirements (main spec)
decisions/ # per-backlog decision logs (backlog ID in the filename)
gtm/ # go-to-market docs (optional)
planning/ # meeting notes, plans (optional)
wiki/ # DERIVED — machine-written; humans read, never edit
index.md # concept catalog: one line + link per page
concepts/ # one page per concept, frontmatter with sources
conflicts/ # open conflict / underspecified-decision reports
README.md
.gitignore
```
`graphify-out/` (graph build products) appears after the first refine-wiki run — do not
create it by hand.
## File contents
`.gitignore`:
```gitignore
# per-person editor state (Obsidian)
.obsidian/
# graphify incremental cache + scratch working files (build products graph.json
# and GRAPH_REPORT.md ARE committed)
graphify-out/cache/
graphify-out/.graphify_*
```
`README.md`:
```markdown
# <project-name> — lore vault
Single source of truth for this project's planning lore, kept by Loremaster
(github.com/loremaster-ai/loremaster).
- `raw/` — truth. Humans edit here (PRD, decisions, gtm, planning).
- `wiki/` — derived. The agent refines raw into concept pages; never hand-edit.
`related` [[wikilinks]] are derived from the knowledge graph, one-way.
- `conflicts/` — open conflicts and underspecified decisions awaiting human verdict.
- `graphify-out/` — graph build products (`graph.json`, `GRAPH_REPORT.md`).
Browse it in Obsidian (open this folder as a vault); edit `raw/` only.
```
`raw/PRD.md`: the team's real PRD if one exists, else the smoke-test sample
(`references/sample-prd.md`) as a placeholder.
`wiki/index.md`:
```markdown
# Wiki index
(Empty — populated by the first refine-wiki run.)
```
Keep `raw/decisions/`, `raw/gtm/`, `raw/planning/`, `wiki/concepts/`, and `conflicts/`
present in git with a `.gitkeep` file each while empty.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |