Guide
Using Mindframe.
Mindframe is installed and /mindframe:setup has run. Here is how you use the deployment, day to day.
How do I use this product? Paste this to your coding agent — it fetches the guide and walks you through it.
how do I use mindframe? https://mindframe.softwaresoftware.dev/usage/llm.txt
After setup
What you have.
Setup leaves you with a working deployment — four pieces that do the rest.
| Piece | What it is |
|---|---|
| Knowledge base | A vault of markdown notes — your services, people, decisions, incidents, processes. A git repo, owned by you. |
| Event router | The dispatcher, wired to your source systems. Turns incoming events into agent runs. |
| Dashboard | A generative-UI surface — describe what you want to see, an agent builds it. |
| Deliverable skills | The work mindframe does — incident triage today, more as the library grows. |
How it runs
Push and pull.
Push — it reacts. When an incident fires — a Sentry alert, a PagerDuty page — the dispatcher spawns a short-lived agent that investigates it against your vault and posts a recommendation to the channel you configured. This is automatic; you don't do anything.
Pull — it observes. The dashboard probes your services, daemons, and agents and renders live status — the things no event announced. The two paths never touch each other.
Day to day
What you can do.
Trigger a triage yourself
You don't have to wait for an event. Run a deliverable skill directly — the agent reads the issue or the cluster, greps the vault for the matching runbook and ownership, cross-references recent commits, and posts a structured summary with a recommended action.
/mindframe:sentry-triage <sentry issue URL or id>
/mindframe:k8s-triage incident.id=<id> pod=<pod>
Use the dashboard
Open the dashboard and type an instruction in plain language — "show me payments-api", "health of the cluster". The Mindframe agent composes a complete view or tool for it. Each instruction refines or replaces the last.
Ask the knowledge base
Ask about service ownership, past incidents, decisions, on-call. The librarian answers from the vault — the source of truth — and never guesses.
Add a data source
Re-run /mindframe:setup any time to bring a new system in scope or re-bootstrap the knowledge base.
Check the bundle's health
Run /mindframe:doctor when something misbehaves, or as a routine check. It walks every component — agent runtime, knowledge base, event router, dashboard, perception MCPs — for missing capabilities, dead daemons, broken config, and schema drift. Safe fixes are applied automatically; the rest comes back as a report with the exact remedy.
Good to know
Two ground rules.
Keep the knowledge base current
The vault is the ground truth every agent reads — triage is only as good as the vault is accurate. If an answer is wrong or stale, the fix is in the vault: tell the librarian what changed and it updates the notes and commits.
Agents recommend; you act
Mindframe drafts a fix, names a suspect commit, recommends a rollback. It does not execute the rollback, merge the PR, or page a team on its own. The action stays with a person.