loreAuthor, retrieve, and maintain OKF documentation with the lore CLI, including explicit multi-repository workspaces. Use whenever reading, writing, linking, moving, querying, or checking docs, so Story/Task coupling, managed blocks, provenance, and cross-links stay coherent. Run `lore instructions` f
questDrive this repo's task tracker with the quest CLI instead of editing backlog/tracker state directly. Use whenever creating, listing, viewing, editing, completing, or archiving tasks, drafts, milestones, or decisions in a Quest-initialized workspace. Run `quest instructions --list` for the workflow g
diagram-architectureExplain and diagram a software system's architecture as C4 views - system context, containers, components - drawn from the actual repository, manifests, compose files and lore docs, never from a generic template. Produces a Mermaid diagram plus a plain-English explanation pitched to the reader (begi
diagram-dataExplain and diagram the shape of an application's data - tables, entities, keys and the relationships between them - as a Mermaid ER or class diagram generated or traced from the real schema (SQL migrations and DDL, Prisma, Django, SQLAlchemy, ActiveRecord or TypeScript models), with cardinality rea
diagram-decisionExplain and diagram a technical decision - the question, the options considered, the trade-off of each and the path chosen - for an architecture decision record (ADR), a Quest decision (DEC-N) or a design discussion, plus how decisions relate over time (supersedes, requires). Reads the real ADR and
diagram-planExplain and diagram where the work stands - which tasks block which, what is ready to start, what each milestone contains, and the critical path - generated directly from the Quest tracker (`quest task list --json`, `quest milestone list --json`) so every task and dependency arrow is real, never rem
diagram-processExplain and diagram how something happens - a workflow, request path, pipeline, approval process, incident runbook or object lifecycle - as a Mermaid flowchart (with swimlanes for who does what), sequence diagram (who calls whom, in what order, including the error path) or state diagram (the states
diagram-reviewValidate and critique Mermaid diagrams in Markdown docs, ADRs, READMEs, PR descriptions or a reply. Checks that each diagram parses under the Mermaid version GitHub renders, follows the accessible profile (accTitle/accDescr, quoted labels, legend, colour never the only signal), stays within the read