lore

Onboard a target repository into the workflow conventions — docs/prd/, docs/adr/, and the AGENTS.md shim. Idempotent, a thin pointer at `lore attach --scaffold-workflow`. Use when setting up a repo to adopt the workflow skills.

Systematic root-cause debugging with a hard circuit breaker. Use when a bug resists fixing, a test keeps failing, a teammate is stuck after repeated fix attempts, or you catch yourself guessing at fixes instead of finding the cause.

After an epic merges, update a repo's Diátaxis documentation (tutorials, how-to, reference, explanation) to reflect the implemented state, then open a docs PR that auto-merges on green. NEVER touches docs/prd or docs/adr. Use after an epic lands and its user-facing docs need to catch up. Standalone and cross-repo aware.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

A relentless interview to sharpen a plan or design.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Fast path for one well-understood GitHub issue — read the issue and the code map, clarify only if needed, then TDD it on one branch to one PR with the ADR and docs gates applied. Use when the user points at a single clear issue and wants it implemented directly, not run through the whole epic chain.

Supervise parallel TDD implementation of an epic tracker issue across one or more repos — plans, dispatches teammates, crosschecks every PR, and lands the epic autonomously. Use when the user points at an epic/tracker issue and wants orchestrated, batched, autonomous implementation.

The first step of a piece of work — the session does its own homework, then reflects its understanding back for confirmation before any planning or grilling. Use at the start of a task, when the user says "orient", "get oriented", "what's your understanding", or wants the session to reflect back before planning.

At the end of a long session — often after /lore-workflow:orchestrate-epic surfaced follow-up work — capture this session's context into an epic seed, a GitHub tracker issue a fresh session can pick up cold and run /lore-workflow:orient on. Use when follow-up issues surfaced, the session is too long to continue cleanly, and you want to hand the discussion to a new session.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Turn the current conversation or a plan/PRD into a PRD file under docs/prd/ plus an epic tracker issue with one sub-issue per feature, structured so /lore-workflow:orchestrate-epic can implement it autonomously. Use when the user wants an epic/tracker issue, or to turn a plan/PRD into an orchestratable epic.

Propagate `supersedes:` and `implements:` relations, backfill missing dates from git, and hint when a wiki has outgrown solo mode. Frontmatter-only judgement calls — never edits note bodies. Use for routine vault hygiene; pair with `lore lint` when indexes are also stale. Run with "/lore:curator <wiki>".

List pending freshness verdicts and let the user resolve each one. The primary verdict path is the in-passing nudge emitted during a session; this slash command is the explicit fallback that makes the SessionStart pending-verdict chip actionable. Run with "/lore:verify" — wiki-scoped to match the chip count.

Show the full timeline of context Lore injected this session. Pure cache read — no live I/O, no re-gather. Run with "/lore:context".

Process files from wiki inboxes and the root inbox. Calls MCP `lore_inbox_classify` for the deterministic walk; LLM reads each file and composes notes; `lore inbox archive` moves originals to `.processed/`. Run with "/lore:inbox".

Load working context from the vault on demand. Single MCP call dispatches across no-arg (recent across all wikis), wiki-scoped, keyword search, or scope-prefix aggregation. Run with "/lore:resume" optionally followed by keywords, a wiki name, or a scope prefix.